Posts by HiassofT

  • 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

  • LibreELEC (Matrix) 10.0.0

    Quote from jim_p

    May I ask what this means?

    Drivers for RPi2 and 3 are currently not yet feature complete and stable.

    LE10 uses a completely new and different graphics and video decoding stack. For quite some time RPi0-3 had some severe issues (which are mostly solved now) but so far we could do only a very limited amount of testing on RPi2/3 so there might be more bugs lurking.

    One of the major missing features on RPi2/3 is GPU accelerated HEVC playback - which means HEVC is practically unusable. Not sure if or when this will be added, it's very tricky and other missing features like deinterlacing (which is also important for RPi4) have higher priority.

    We'll look into providing LE10 testbuilds for RPi2/3, if you don't need HEVC these should already be quite usable - and feedback from testers will also help us find bugs.

    so long,

    Hias

  • LE 10.0.0 RPi4B - TV signal is lost

    Most likely you are hitting this issue: HDMI screen turns off when sustained high CPU usage on all cores · Issue #1598 · raspberrypi/firmware · GitHub

    Due to internal clocking changes the RPi4 started clocking down the HDMI block too much when it throttles (eg when it got too hot or in undervoltage conditions) which led to "no signal".

    LE 10.0.1 will contain a fix for that, but you still need to resolve the root cause (too weak power supply).

    LE 9.2 was able to visually notify you about undervoltage conditions (by showing a lightning bolt on the screen) but unfortunately that's no longer that case with the new graphics driver in LE10 so you/we need to check the logs (we added the throttled state to pastekodi logs right at the beginning though so we can easily see if there was a power supply issue - these are still quite common).

    so long,

    Hias

  • LibreELEC (Matrix) 10.0.0

    Always be careful with overclocking, it can cause subtle issues and settings that work stable today can result in an unstable system after the next (firmware) update.

    Of course you are free to overclock your RPis as much as you like, just keep in mind that if you experience some issue the first thing to check is if removing the overclock fixes it.

    so long,

    Hias