Please open an issue on github here Issues · LibreELEC/LibreELEC.tv · GitHub so this doesn't get lost.
so long,
Hias
Please open an issue on github here Issues · LibreELEC/LibreELEC.tv · GitHub so this doesn't get lost.
so long,
Hias
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.
so long,
Hias
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
2019-04-11 18:28:41.660 T:3011814784 DEBUG: CDRMUtils::FindPreferredMode - found preferred mode: 1280x720 @ 60 Hz
2019-04-11 18:28:41.661 T:3011814784 DEBUG: CDRMAtomic::InitDrm - initialized atomic DRM
2019-04-11 18:28:41.748 T:3011814784 DEBUG: CWinSystemGbm::InitWindowSystem - initialized DRM
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 1280x720 with 1280x720 @ 60.000000 Hz
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 1920x1080 with 1920x1080 @ 60.000000 Hz
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 1920x1080 with 1920x1080 @ 59.940063 Hz
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 1920x1080 with 1920x1080 @ 50.000000 Hz
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 1280x720 with 1280x720 @ 59.940063 Hz
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 1280x720 with 1280x720 @ 50.000000 Hz
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 1024x768 with 1024x768 @ 60.000000 Hz
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 800x600 with 800x600 @ 60.000000 Hz
2019-04-11 18:28:41.748 T:3011814784 NOTICE: Found resolution 720x576 with 720x576 @ 50.000000 Hz
2019-04-11 18:28:41.749 T:3011814784 NOTICE: Found resolution 720x480 with 720x480 @ 59.940063 Hz
2019-04-11 18:28:41.749 T:3011814784 NOTICE: Found resolution 720x480 with 720x480 @ 60.000000 Hz
2019-04-11 18:28:41.749 T:3011814784 NOTICE: Found resolution 640x480 with 640x480 @ 60.000000
...
2019-04-11 18:28:41.891 T:3011814784 DEBUG: CDRMUtils::SetMode - found crtc mode: 1280x720 @ 60 Hz
2019-04-11 18:28:41.891 T:3011814784 DEBUG: CGBMUtils::CreateSurface - created surface with size 1280x720
Display More
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
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
...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
Simultaneous audio output to HDMI and analog is no longer possible (without some severe tinkering and drawbacks).
Use the Audio Profiles addon from the kodi repository to easily switch audio output (eg with a button on your remote). See here for more info Add-on:Audio Profiles - Official Kodi Wiki
so long,
Hias
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
Do you have a 3D-capable TV? tab/sbs are the two modes to output 3D (I don't think it'll work on RPi/kodi ATM though).
So just whitelist the 1920x1080 modes without tab/sbs.
so long,
Hias
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
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
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
max_usb_current=1 has no effect on RPi4, you can drop that.
Overclocking capabilities and settings depend on your specific board/chip, you'll need to find out yourself if it works or not.
4kp60 output has some known issues (see release post), these will be fixed in 10.0.1
so long,
Hias
Your power-supply seems to be underrated. The logs show undervoltage reports which then cause the HDMI signal to drop out - and will likely cause all sorts of other issues.
I'd recommend using the official RPi power supply, this is known to be working fine.
so long,
Hias
Which platform and LE version are you using?
LE9.2 on RPi only supports the official RPi 7" touchscreen, on LE10 DSI support is still rather experimental. You might find some more info on the RPi forums, eg here Interfacing (DSI, CSI, I2C, etc.) - Raspberry Pi Forums
so long,
Hias
No, only the kernel is 64bit (to solve the dreaded OOM-killer issue), userspace is still running 32bit.
so long,
Hias
Thanks for the info!
I could reproduce the pixelated output issue here and pinged the RPi devs - it looks though as 480i/576i output via HDMI always had this issue on RPi4.
so long,
Hias