Are you connecting to the display through hdmi or composite (shared with headphones socket)?
Posts by popcornmix
-
-
Sorry for the long delay, life got in the way. I'm working on this issue, but the command getedid is not found. I'm using 9.2.8 on a RPI4. I tried adding the lines hdmi_group=1 hdmi_mode=16 to the config.txt but the device is still booting into 4k on the known good TV I'm working with. My plan is to get a good EDID from this TCL TV I have and then set it so it works on the picky Samsung unit, not sure if you think this is a good idea or not. I tried searching the edid commands for LE9 but I haven't found anything useful. Thanks for the help.
LE 9 is no longer updated. I'd suggest trying LE10 and seeing if that has the issue (and it will support getedid).
-
Would it be possible to add the option within the GUI to adjust this delay?
You said you fixed it with "vc4.inval_delay=0 vc4.cec_debug=0x100".
Have you fixed it with "vc4.inval_delay=<some number> vc4.cec_debug=0"
If not, there's no point adding a gui option to adjust the delay for you.
-
No definite ideas, but if it were me I'd try:
I would carefully check for any CEC settings in AVR menu and TV menu.
TV seems more likely to be setup correctly as it's working with a direct connection, but may have different configuration per HDMI port.
Try different hdmi ports on AVR and TV.
Unplug TV/AVR/Pi from mains and remove all hdmi connections. Leave unplugged for a minute).
Connect (just) hdmi leads from Pi to AVR and AVR to TV.
Power on TV. Then AVR. Then Pi.
-
added
video=HDMI-A-1:1280x720M@60D to second line of the file.cmdline.txt is a single line. Anything after the first newline is ignored. Make sure you add any options to the first line.
-
When I get video lags, I restart raspberry Pi and it helps... Have no idea why
Did you downgrade widevine as mentioned earlier. Latest widevine is known to cause lags.
-
Azurewrath can you try this test build.
I think the issue was your video was 10-bit but not HDR, which is a little unusual.
That meant the kernel didn't do a full modeset (as HDR colourspace didn't change) but did change the colour depth (which adjusts the pixel clock) which really wants a full modeset.
The test build is a stanard Matrix build with a kernel patch added to force the modeset.
-
I installed your test build and the 'vc4.inval_delay=5000' added to the cmdline.txt appears to have resolved the issue in my setup. That is with an LG C9 and Yamaha TSR-7810 AVR with the Rpi4 plugged into the AVR using CEC over the ARC HDMI connection. Thanks for looking into this issue! Does this test build include the updates from 10.0.2 and is it safe to continue running or do you recommend that I revert back until your fix is rolled into the next release?
Yes, this build matches 10.0.2 and you can continue using it. Please confirm if vc4.inval_delay=2000 also works for you.
Also report if vc4.inval_delay=0 vc4.cec_debug=0x100 works for you.
-
My TV is set to limited colour range. I don't want to change this because it is connected to an AVR with other devices which are all sending limited RGB (e.g. the Bluray player).
Limited/full range is signalled over hdmi (in the AVI infoframe) and generated by the source (e.g. the Pi)
You shouldn't set it on the sink (TV) - it should just display in the colour range that has been signalled.
-
Has the "plain" decoder (w/o PRIME) been fixed too? (i had the same issues when using the plain decoder w/o PRIME too)
No, the fix is in hardware decode specific code.
If it's failing without PRIME, then it suggests a core ffmpeg issue (so will affect kodi on any platform not using hw decode) and will affect many other players that use ffmpeg internally.
Did the original sample provided have the issue?
-
Are you ensuring TV (and AVR if used) is powered on before booting the pi?
-
It was once again my bad as I put vc4.inval_delay=5000 after a line break and not immediately on the same line after "quiet" on cmdline.txt
And I'm happy to say that it is working with this value!!! It does not turn on after being powered off!! I'm so happy now!
Okay good to know. It would be helpful if you could confirm whether a smaller number also works (try with 4000, 3000, 2000).
Also try with "vc4.inval_delay=0 vc4.cec_debug=0x100" which I suspect will also fix it.
It would also be useful if any other affected users could test.
-
Yesterday I did the proposed update to 10.0.2 and since then the 3840x2160 24p video no longer switches to 24p. In 1080p no problem, the tv goes well in 1080p24. Did you have the same problem or do you have a solution please?
It's not something I see (or have seen anyone else reporting).
Probably best to create a new post, including a debug enabled log of you playing a 3840x2160@24 file, where the hdmi mode is not set.
-
Can you explain, why you have a much darker screen with a clean LE10 than a clean LE9 installation?
LE9 has no support for HDR. If you play a HDR video then the colours will be completely wrong (and typically brighter/more washed out) than they should be.
LE10 does support HDR.
-
I couldn't get that file to fail to play.
NeB are you using a whitelist?
I suspect your issue is probably related to hdmi cable, but having a whitelist set up (allowing lower resolution/refresh rates to be chosen) will make it less likely you'll hit issues.
See: https://wiki.libreelec.tv/configuration/4k-hdr
The debug log would be useful to see exactly which hdmi is being chosen.
-
Please note that /sys/module/vc4/parameters/inval_delay value is always 1000 regardless using vc4.inval_delay=5000 or vc4.inval_delay=0 vc4.cec_debug=0x100 at cmdline.txt
That suggests you haven't edited /flash/cmdline.txt correctly.
What does:
Codecat /flash/cmdline.txt cat /proc/cmdlinereport?
-
By the way, how to make sure that the update occured?
CodeLibreELEC5:~ # grep . /sys/module/vc4/parameters/* /sys/module/vc4/parameters/cec_debug:256 /sys/module/vc4/parameters/fkms_max_refresh_rate:85 /sys/module/vc4/parameters/inval_delay:0 /sys/module/vc4/parameters/tv_norm:(null)If you are not running the correct version, then you won't see the cec_debug/inval_delay entries.
And the values shown should match what you added to cmdline.txt
-
See post and test build here
