Posts by popcornmix

Do you have another hdmi cable you can try? That would be my first guess.

Does it occur only when playing video or in gui as well?

You have display configured to 4kp30. Does the issue occur at 1080p60?

Quote from taxmilibre

If it was possible for the sound to be simultaneously in the 3.5 mm and HDMI socket, I would be very pleased.

That is not possible.

I think if you add:

dtparam=audio=on

to /flash/config.txt and reboot the analogue option should appear.

Quote from harun-cuk17

Is this the latest build to test? And this one should be also the best to test. Am I right?

When I download the file and unzip I see different files and maps inside. How could I write that build to sd card? Do you have some steps how it should be?

You need to be running a Matrix beta build.

Copy the tar file linked to /storage/.update and reboot.

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.

This log looks like an out-of-memory issues form transmission:

Apr 03 15:53:02.395376 LibreELEC kernel: transmission-da invoked oom-killer: gfp_mask=0xcc0(GFP_KERNEL), order=0, oom_score_adj=0

Do you still get crashes when transmission is disabled?

Quote from kaktuzzo

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).

Quote from TauNeutrino

here are the logs:

http://ix.io/2Ufe

From log:

 [    0.000000] OF: fdt: Machine model: Xunlong Orange Pi Zero

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?

dott can you try adding

over_voltage=2

to config.txt on fat partition of sdcard?

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.

Quote from Anke

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):

3D - Official Kodi Wiki

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:

Revert "Sets the BCDC priority to constant 0" by JamesH65 · Pull Request #2545 · raspberrypi/linux · GitHub

There is test firmware in this thread which may help this issue.

It is possible the test firmware from this post may help

Quote from Mario77

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 http://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.