OK,where do I look for it, in LE11 or Beebox UEFI?
LE 11. Create an advancedsettings.xml file: Click!
Is there any hope that the problem with the Generic HDMI-DP Linux driver will be fixed?
Nobody here is working on it. Better ask at the Kodi forum, because this affects many players.
There is no bug .. auto-update has not been enabled yet.
The LE 10 version folder was empty after switching to manual update.
My conclusion was: No LE 10 versions available, no auto-update available.
Please edit your post, and translate into English. Thanks!
Sorry, I was thinking about RPi3B+. If you run RPi1B+, there is no LE 10.x version.
dtoverlay=hifiberry-amp is correct, but I guess your RPi is too slow to handle that HiFiBerry HAT.
Update to LE 10.0.4.
Create an advancedsettings.xml file, and add .flac: Click!
HDMI video mode is more than just resolution, it also includes color space.
It's very likely that your hardware uses a DiplayPort-to-HDMI adapter (LSPCon chip) internally. Such hardware is a known source of trouble. So yes, I think we can call the errors on HDMI output a driver issue.
When I connect the TV/AVR to the DisplayPort 1.2, LE11 plays all videos with 3D audio one after the other. There is no need to reboot after each video.
But there is always an offset between video and audio! The audio is not in sync with the video.
Avoiding to use the LSPCon chip is your best chance to make things work. I think there is a setting for an A/V offset somewhere.
Maybe your video material has errors:
2023-01-25 19:51:02.684 T:799 debug <general>: CBlurayCallback - Error opening file! (udf://smb%3a%2f%2f10.220.0.41%2fFilme_LW_11%2fPhantastische%20Tierwesen%20Dumbledores%20Geheimnisse%20(2022)%2fPhantastische%20Tierwesen%20Dumbledores%20Geheimnisse%20(2022)%20%5b2160p%20TrueHD%20Atmos%20%5d.iso/AACS/Unit_Key_RO.inf)
2023-01-25 19:51:02.684 T:799 debug <general>: CBlurayCallback::Logger - aacs.c:83: AACS/Unit_Key_RO.inf not found. No AACS protection.
...
2023-01-25 19:51:02.855 T:799 debug <general>: Open - probing detected format [mpegts]
2023-01-25 19:51:02.856 T:799 debug <general>: Open - avformat_find_stream_info starting
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] PES packet size mismatch
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] Packet corrupt (stream = 14, dts = 1047750).
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] PES packet size mismatch
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] Packet corrupt (stream = 14, dts = 1047750).
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] PES packet size mismatch
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] Packet corrupt (stream = 14, dts = 1047750).
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] PES packet size mismatch
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] Packet corrupt (stream = 14, dts = 1047750).
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] PES packet size mismatch
2023-01-25 19:51:02.867 T:799 debug <general>: ffmpeg[0x52079b0]: [mpegts] Packet corrupt (stream = 14, dts = 1047750).
2023-01-25 19:51:02.941 T:799 error <general>: ffmpeg[0x52079b0]: [mp3float] Header missingUse the kernel parameter method: Click!
Im having this same exact issue with an Intel NUC10i7FNH1, did anyone figure it out, using 10.0.4 and high quality hdmi cables
Thank you so much…it worked. For future updates should I just leave it on Manual then and ignore the Auto option?
I would say yes. Hopefully this bug will be fixed in the next stable release. Developers are informed.
Thanks chewitt! What would happen if I play HDR media on the TV? Wouldn't the TV just ignore the HDR signal and just play the content in UHD without HDR?
If you don't hardcode anything, HDMI will do the usual negotiation, which means SDR delivery to your TV.
I have 10.0.2 running great on pi4 architecture RPI4.arm
I have auto update turned on but I am not getting any prompts to update to 10.0.4
Anything I am missing in the settings?
I had the same issue.
Looks like an initialization problem of the Ethernet adapter:
Jan 20 03:32:22.977996 op3lts kernel: dwmac-sun8i 5020000.ethernet eth0: PHY [stmmac-0:01] driver [YT8531 Gigabit Ethernet] (irq=POLL)
Jan 20 03:32:22.979202 op3lts kernel: dwmac-sun8i 5020000.ethernet eth0: No Safety Features support found
Jan 20 03:32:22.980173 op3lts kernel: dwmac-sun8i 5020000.ethernet eth0: No MAC Management Counters available
Jan 20 03:32:22.981075 op3lts kernel: dwmac-sun8i 5020000.ethernet eth0: PTP not supported by HW
Jan 20 03:32:22.984864 op3lts kernel: dwmac-sun8i 5020000.ethernet eth0: configuring for phy/rgmii-txid link mode
Jan 20 03:32:22.983137 op3lts connman-vpnd[401]: eth0 {update} flags 36931 <UP,RUNNING>
Jan 20 03:32:22.983174 op3lts connman-vpnd[401]: eth0 {newlink} index 3 address 02:07:14:7B:21:B5 mtu 1500
Jan 20 03:32:22.983196 op3lts connman-vpnd[401]: eth0 {newlink} index 3 operstate 0 <UNKNOWN>
Jan 20 03:32:22.983596 op3lts connmand[486]: Adding interface eth0 [ ethernet ]
Jan 20 03:32:22.983818 op3lts connmand[486]: eth0 {update} flags 36931 <UP,RUNNING>
Jan 20 03:32:22.983844 op3lts connmand[486]: eth0 {newlink} index 3 address 02:07:14:7B:21:B5 mtu 1500
Jan 20 03:32:22.983866 op3lts connmand[486]: eth0 {newlink} index 3 operstate 0 <UNKNOWN>
Jan 20 03:32:23.002208 op3lts connman-vpnd[401]: eth0 {update} flags 36867 <UP>
Jan 20 03:32:23.002248 op3lts connman-vpnd[401]: eth0 {newlink} index 3 address 02:07:14:7B:21:B5 mtu 1500
Jan 20 03:32:23.002252 op3lts connmand[486]: eth0 {update} flags 36867 <UP>
Jan 20 03:32:23.002267 op3lts connman-vpnd[401]: eth0 {newlink} index 3 operstate 2 <DOWN>
Jan 20 03:32:23.002280 op3lts connmand[486]: eth0 {newlink} index 3 address 02:07:14:7B:21:B5 mtu 1500
Jan 20 03:32:23.002300 op3lts connmand[486]: eth0 {newlink} index 3 operstate 2 <DOWN>jernej ?
I have tried the most recent version (LibreELEC-Generic.x86_64-11.0-nightly-20230121-f3ef152.img.gz) but HDR does not work and I also get glitches in the picture.
Thanks for testing! If you want to help to fix this, write a bug report here (read the How-To on top first).
Thanks I'll wait for that
No need to wait. Put one of those into your /storage/.update folder, and reboot: Click!
It's clearly a bug on CEC:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xf7d26bec in CEC::CSLCommandHandler::ActivateSource(bool) () from /usr/lib/libcec.so.4Moved to bug reports.