The problem is the codec (VC-1) which isn't hardware decoded and ffmpeg doesn't support multithreading.
(You typically see one core at 100% with 2 fairly idle) Some 1080p files struggle to keep up. Overclocking could help.
I did profile and found about 30% of the decode time is spent in two loop filter functions.
There's optimised assembly on x86, but arm only has C code. It's something we'd like to improve.
Hi,
Every day libreelec 10 crashes a few times when the TV is off
You have a couple of addons that are crashing:
weather.gismeteo and pvr.iptvsimple
I'd try uninstalling those and see if crashing stops.
That's strange. I was getting a different log file earlier.
I think the issue is that the gui mode is 4kp30 and the video is 50Hz.
Currently LE doesn't support 4kp50/4kp60.
I'd suggest you change mode in system/video settings to 1080p60.
Then enable "adjust display refresh to match video" and use the whitelists to enable modes you care about.
Make sure this includes 1080p50 (you can include 4kp24/4kp30 etc for 4k content).
From log:
So I'm not sure why you are asking about pi4. It's a very different device.
> Issue does not reproduced on nightly build dated about 20201120.
HW hevc decode may not have been supported back then, so you may have always had this issue.
I'd predict that disabling DRM Prime HW decode in settings would avoid the artefacts.
It is possible you have a hardware fault. You don't have another Pi4 you could try the sdcard on?
The workaround just gets half-SBS 3D playback working like on the other players you suggested.
i.e. with no 3d menus/subs.
It is on the list of things to fix, but it's not the highest priority.
If it is a "really simple fix", then pull requests are welcome.
Nope.
Simply no... SBS 3D videos play normally on any software player I've tried, they simply consist of two both frames side-by-side ... any mplayer/VLC/SMplayer plays them fine - apparently with no "driver" the projector does the decoding/alternating of the frames.
None of those players bother to have 3D menus or 3D subtitle support. - which is still working for nice video playback.
Here we have a perfectly fine SBS menu, subtitles in 3D , but instead of displaying both frames inside the picture, like those players do .. it seems we somehow crop the output to one single frame.
The workaround is to not tell kodi the files are 3D.
Make sure filenames do not contain the 3d tags (either by changing the filename or the default 3d tags matched):
or use the OSD interface to set the file to 2D.
That should mean the menus/subs won't go into 3D mode, but it also means the video will be played normally,
which for half-SBS/half-TAB is what you want.
I believe it was no longer needed after a wireless firmware update:
There is test firmware in this thread which may help this issue.
It is possible the test firmware from this post may help
Issue is over voltage
Cannot be set higher then
over_voltage=3
I've found an issue with over_voltage=4 (or higher) on Pi2.
Can you test this firmware
Unzip and replace start.elf/fixup.dat on boot partition with start_x.elf/fixup_x.dat from zip file.
Let me know if over_voltage=4 starts to work again.
Your sample does generate a "hevc @ 0x168ca90] Out of pu + coeff intermediate memory: pus=768" warning which doesn't seem to be handled well.
I've forwarded the report to our hevc codec guy.
The bitrate limits are complicated. Generally higher bitrates means more motion vectors which tends increase cache misses and so increase sdram bandwidth. sdram bandwidth is usually the constraint on playing harder samples.
You can get a slight increase in sdram bandwidth with hdmi_enable4kp60=1 (even if you don't use a 4kp60 mode) as it runs the AXI bus at 550MHz rather than 500MHz.
The GUI overlay takes some bandwidth, so subs, OSD, debug info etc will cost some additional bandwidth.
It may also be worth monitoring the hevc clock (vcgencmd measure_clock hevc) when the video is playing. I believe it will be 500MHz when busy and 250MHz when less busy. If it's dropping to 250MHz when your stream is playing that would limit the streams you can play.
hevc can be overclocked, or you can disable the lower frequency (force_turbo=1 in config.txt) which could help.
Can you provide a sample file that freezes the Pi4
While we're unlikely to be able to play very high bitrate clips smoothly, they shouldn't cause a freeze.
As it's showing same symptoms with raspbian, then it might be worth creating an issue here:
Issues · raspberrypi/firmware · GitHub
where the right people should see it.
OffLoad could you try installing raspbian on an sdcard, and use the display configuration tool to switch to 4kp30.
Does that have the same problem? If so can you also try with hdmi connected to other hdmi port
(this doesn't work with kodi, but should with raspbian).
Does 4kp24 work?
I'm suspecting that the cable is borderline (I know it has worked on another device, but it could be just on the edge of being usable at 4kp30).
But to begin with see if we can rule out a kodi/LE issue.
The fix was done long ago, but is stuck in a PR and hasn't made it into an official build:
