Is there something wrong with the hdmi_force_hotplug=1 setting?
LE10/kodi 19 has switched to using arm-side kernel drivers for display, rather than the (closed source) firmware side drivers previously used.
hdmi_force_hotplug (and most display settings) only apply to firmware so will have no effect.
Use getedid (described in previous post) to get the same effect applied to kernel driver.
You need LibreELEC (Matrix) 10.0 BETA version for HD audio passthrough.
Your sample file plays correctly for me on a Pi4.
So, either problem is with your Pi4 hardware, power supply or something wrong on sdcard (incorrect settings/corruption).
Usually an issue with power supply generates an "Under-voltage detected!" message in dmesg, so I'd be surprised if that fixed it.
You could try a clean install to a different sdcard to rule the sdcard contents out.
Ideally, if you could find another Pi4 to test your sdcard/power supply/TV etc with then we could be sure if it's the Pi4 or not.
One last thing. Try adding "gpu_freq=250" and "arm_freq=600" to config.txt. That will make the Pi4 much slower, but I'd be interested if corruption is still present.
Libreeelec 9.2.6 does not support TrueHD passthrough (or DTS-HD) on Pi.
It should be supported on LE 10 beta.
Are you quite sure your soundbar supports TrueHD passthrough? Do you have a link to the specs?
When the video is corrupt, and you bring up OSD, is that clean, or have corruption?
This feels like a hardware issue. Did HW h.264 decode on that board work with LE9/Kodi 18?
"vcgencmd get_config over_voltage" should indicate what value has been read.
Your link is wrong, but if you are saying it fails with standard big_buck_bunny_1080p_h264.mov
then that is a file that is tested regularly and plays fine.
Can you try adding "over_voltage=2" to config.txt on boot partition and test again?
Can you confirm if playing a file locally still has the problem? (e.g. copy to sdcard or attached USB stick)
If it does can you provide a sample file? (e.g. cut a 1 minute chunk that shows the problem and upload to a site like dropbox/google drive)
https://wiki.libreelec.tv/support/log-files
This isn't an issue I'm experiencing (or have heard of from others).
If this issue only started recently, then confirming the oldest build that has the issue and the newest build that didn't have issue would help narrow it down.
What is memory size of Pi4? Have you installed any other apps (e.g. docker/torrent client/PVR backend etc?)
Testing if this occur with a clean install of LE 10.0b2 would be useful (before installing any addons or other changes).
I can confirm this issue still exists on my 90% videos that I have on my hard drive and they have dts, Dolby Digital, dts hd audio , I am using libreelev 9.96.2 10. Are there any known solutions ?
Post a debug log. Can you provide a sample file that has the issue?
(or confirm if one of these has it: ¦› DTS Demo Trailers HD and SD - List of All Downloads)
The HVS can dither. It is enabled for 16 and 18-bit LCD displays.
It hasn't been enabled for HDMI which is typically 24-bit to 24-bit
(but 10-bit HEVC does change that).
I'll see if I can spot a difference with it enabled.
(although 10/12-bit output is starting to work).
> Whatever image I tried (of those that worked with the rockpi4 before) does not work.
Were the old and new Pi's Raspberry Pi or Rock Pi? The two are very different and need different images.
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?
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.
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.
