Thanks for the report! I haven't seen that issue myself yet and pinged the RPi devs.
Can you test if the video plays fine if you set the display resolution to 1920x1080? I suspect it could be related to the 2560x1440 resolution of your monitor.
so long,
Hias
No need to use lirc, just remap the buttons with kodi's keyboard.xml. See eg here RE: apple ir remote (atvclient) not working after upgrade from 9.0.2. to 9.1.002
so long,
Hias
LE includes the latest default and stable firmwares available when building the image. Settings addon checks against the default release train (same as RPiOS), if you want to track stable instead you can do that manually on the command line.
so long,
Hias
Thanks a lot for reporting back, it's really nice to hear the build is working fine for you!
I hope we'll be able to provide some (semi-)regular LE10 RPi2 builds at some point in time. We already discussed that internally, problem ATM is that there are issues with our CI buildsystem and it can't do it automatically for us.
I'll keep my build online for now so other people can download and test it as well.
so long,
Hias
Thanks for the log!
10bit H264 files are a bit problematic ATM, there are several bits and pieces missing to handle them gracefully. As a workaround it's easiest to disable DRM PRME decoding (as you already found out) to play those files until the issues are resolved.
so long,
Hias
Here's an RPi2 build, built straight from our current libreelec-10.0 branch. It includes all the kernel and video player fixes we have so far:
LibreELEC-RPi2.arm-10.0-devel-20210901141112-c91d4d4.img.gz
so long,
Hias
Thanks for the log!
There's currently a bug playing VP8 videos, better avoid these files for now, they lead to kernel/firmware issues and you need to reboot the RPi to get it back into a proper working state. I've informed the RPi devs and hope we'll get a fix soon.
Concerning the H264 issue: could you please test with this build: LibreELEC-RPi4.arm-10.0-devel-20210901104638-c91d4d4.tar ?
This is our current libreelec-10.0 development version and it includes several fixes for video player crashes. The "V207 TS - AVC 1080p 24fps 8bit - AAC2.0.ts" file played fine with it here (tried starting it a couple of times).
so long,
Hias
If kodi crashed then you should have a kodi_crash.log file.
Can you please upload that (after reproducing the issue)? Either run "pastecrash" via ssh or use the "upload crash log" function in LE settings.
so long,
Hias
Thanks for the reply, Chewitt. I have no idea what you mean. Something wrong with my settings? I tried to play some different HDR movies, and they still have washed out colors. If I play HDR from YouTube, the colors looks right.
Does your TV support HDR?
If no then this is expected - HDR output to HDR capable TVs is supported, tonemapping (converting HDR videos to SDR if your TV does not support HDR) is not supported on RPi4.
so long,
Hias
Thanks a lot for the logs!
If you have to use hdmi_force_hotplug on the RPi then I suspect the hotplug-detect signal might be indeed the culprit and the soundbar doesn't detect the TV because of that.
When directly connected the RPi got a valid edid from the TV, indicating 1920x1080p60 as preferred mode.
The edid from the soundbar looks like it sent a fallback safe-mode one - preferred mode is 1280x720p60 and the 24Hz mode from your TV are missing. But AC3, DTS and multi-channel audio support is listed.
The hotplug detect issue could be caused by the cable (hotplug not wired up or cable broken) or it could also be caused by your TV "misbehaving". Both of that happened to others before, too.
Using a different HDMI cable and/or HDMI port on your TV would be the easiest thing to try. Other than that I'm out of ideas - if the TV and soundbar don't play well together because of the TV's hotplug issue I'm not sure there's anything easy you could do about it.
so long,
Hias
My guess is manual starting worked by coincidence - kodi closes the audio device after 1 minute of inactivity, so if you started squeezelite after that it will succeed (but ofc then kodi will fail when it next tries to use the device).
On LE9.2 hdmi audio output was under firmware control and could mix kodi's audio output and alsa audio output (both ended up in VC4 firmware).
Now hdmi audio output is under Linux control and the audio device doesn't support mixing multiple streams - you have to use pulseaudio do to that.
so long,
Hias
This gives me the error below:
[11:25:28.862998] test_open:281 playback open error: Device or resource busy
[11:25:28.863237] output_init_common:401 unable to open output device: default:CARD=vc4hdmi0
This error is expected - kodi is already using the HDMI audio device.
You have to decide who should get access to HDMI audio output, either kodi or squeezelite, shared access from multiple programs is not supported (you could configure pulseaudio to allow shared access that but that'll be a bit tricky).
so long,
Hias
Please always provide a pastekodi debug log as well - we really need that.
so long,
Hias
Thanks for testing. HDMI modes on both logs are the same, so that part of the pass-through works.
The logs are the same because the HDMI infos are all replaced by the hdmi_safe settings - and therefore the number of audio channels is also only 2 (that comes from the failsafe settings, too).
To get any meaningful logs or info about the TV or soundbar these hdmi settings need to be removed from config.txt before.
so long,
Hias
First try to see if you can get the TV working when directly connected to the RPi without all the hdmi_... options you added to config.txt.
hdmi_group and hdmi_mode should be relatively safe to use, but if you need to add one of the sledge-hammer hdmi_force_hotplug, hdmi_ignore_edid or hdmi_safe options it's a strong indication you are working around some fundamental underlying problem (and it also makes the logs useless).
If the RPi can't detect the TV without those options then chances are high the soundbar can't either. On the soundbar you most likely don't have the option to analyse or work around those detection issues (and the soundbar might just disable HDMI output if it thinks nothing is connected) - but on the RPi you can do both.
Use eg "tvservice -s" to check if the RPi detected the TV and what mode it's using and "tvservice -m CEA" to see the list of available modes on the TV.
so long,
Hias
Please open an issue on github here Issues · LibreELEC/LibreELEC.tv · GitHub so this doesn't get lost.
so long,
Hias
Not much we can do about it with at least a debug log and ideally a sample file to reproduce. Our crystall ball is still on repair.
so long,
Hias
