Posts by HiassofT

  • LE 10.0.0 RPi4 - random crashes while playing (starting) video files

    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

  • LibreELEC (Matrix) 10.0.0

    Quote from Pindarm

    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

  • No picture and sound via Yamaha Surroundbar

    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

  • squeezelite not working anymore as background process with LE 10

    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

  • squeezelite not working anymore as background process with LE 10

    Quote from luigi2000

    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

  • No picture and sound via Yamaha Surroundbar

    Quote from Da Flex

    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

  • No picture and sound via Yamaha Surroundbar

    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

  • No picture and sound via Yamaha Surroundbar

    It's hard to tell, it could be an issues with cables or the soundbar, pretty much anything.

    Might be worth checking all parts one by one, also test if the soundbar works with a different HDMI source (eg a bluray or dvd player).

    Also run the following commands, both when RPi is connected directly to the TV and also when it's connected via the soundbar, and post the URLs - this might give us some additional hints.

    Code
    pastekodi
modetest | pastebinit

    so long,

    Hias

  • No picture and sound via Yamaha Surroundbar

    Quote from dippes

    But can you still help me with the HDMI problem with the Surroundbar?

    The log looks fine, Kodi/LibreELEC is running at 1280x720 60Hz which seems to be the preferred mode

    Might be worth checking and/or replacing the cables, also test without the argon one case (there are several reports here on the forum that the case was responsible for display issues).

    so long,

    Hias

  • LibreELEC (Matrix) 10.0.0

    Quote from edjalmo

    I always thought that HEVC was a hardware thing and wold never see this on rpi3, but now is like there's a light in the end of the tunel.

    They're letting us dream kkkkk

    In general HEVC is a hardware thing (or you need a very powerful CPU).

    In the past RPi devs invested an enormous amount time to get HEVC playback working on RPi3 by offloading several CPU intensive tasks to the GPU - with really good results.

    The problem is that this approach only works with the legacy proprietary graphics driver which has now been phased out.

    With the new graphics drivers all of that old, optimized code can't be used anymore and adapting it to the new driver would both be very tricky and time consuming - and it's not even clear yet if it would be doable at all or achieve the same performance as with the old drivers in LE 9.2.

    So: don't hold your breath, ATM we can't promise RPi3 will get back optimized HEVC decoding in LE 10/11/... any time soon.

    so long,

    Hias

  • RPi4 is unreachable after TV was in standby for a while

    Quote from tobor

    ...but I am not attempting to play 4K content. Is the "no signal" problem with 1920x1080 output also a known issue?

    No. We are not aware of any "no signal" / "RPi unreachable" issues at HD resolution (or 4k up to 30Hz).

    Even in case of the known 4kp50/60 "no signal" issue the RPi was still fully functional and reachable eg via ssh - just the TV didn't show a picture anymore. Changing the resolution to 1920x1080 (or 4kp30) eg via the Chorus web interface also brought back TV output.

    If you have a different issue then we need more info.

    so long,

    Hias

  • LibreELEC RPi4 9.95.2 does not reproduce .ASS subtitles

    I could reproduce the issue, that seems to be a bug in kodi: ASS subtitles not shown on gbm if GUI resolution limit is active · Issue #20085 · xbmc/xbmc · GitHub

    When playing HD (or lower res) videos make sure your whitelist is set up correctly and enable "Adjust refresh rate" in player settings - so kodi outputs in HD (or lower), then ASS subs are shown.

    For 4k video output the only workaround for now is to disable the GUI resolution limit (which will give rather poor GUI performance though) or to limit output to HD.

    so long,

    Hias