I'm still missing full HBR audio support for RPi4. DTS HD MA is detected just like DTS and in option of Kodi there is no option to turn on DTS HD MA.
HBR audio isn't implemented yet for the RPi4. It's in the queue but will take a bit (probably months, not weeks).
so long,
Hias
I haven't looked at the temperatures but yesterday I experienced asynchronous video playback on a 1080p Netflix stream. Video was up to two seconds behind the audio but after a scene cut it was in sync again for 1 or 2 minutes. Maybe it has something to do with the cpu temperature.
I'm using the Pi4 without a case but I have a hifiberry on the GPIO
Quite certainly the CPU was maxed out and the RPi couldn't keep up with decoding the video.
While that can be caused by high temperature (and thus throttling, in which case you should see the thermometer icon pop up) I've also seen that with some streams (eg Black Mirror S01E02 at around 59:30-1:00:00) which have very high peak bitrate scenes.
The RPi4 probably needs to be overclocked to keep up with this - or switch to the next lower bitrate stream (IIRC the ~7Mbit/sec 1080p Black Mirror stream peaked to about 11-13Mbit/sec and ran into a/v sync issues, the ~6Mbit/sec 1080p stream played fine). Limiting the max bitrate may also help with that.
so long,
Hias
This is what I assumed, but also read that libreelec ships with upgraded firmware. So, is that true? Does it flash the (Pi Hardware) firmware on (Libreelec) version updates?
LE 9.1.002 ships with updated VideoCore / VPU firmware - the other 2 firmwares (bootloader and USB chip) which are in flash chips aren't touched.
so long,
Hias
Try disabling the pvr client addon, reboot and check if you still have high CPU usage.
Can't recommend anything else ATM without seeing your full debug log.
so long,
Hias
Can you post kodi debug log as well? perf top shows some hefty xml prcessing going on - could be pvr/xmltv addon for example.
so long,
Hias
You can run perf top and check kodi debug log to get some more detailed info. Such high CPU load is definitely not normal - most of the time that's caused by some misbehaving/broken addon.
so long,
Hias
Easiest way is to enable debug logging in kodi and then watch kodi log as you press buttons. eg
tail -f .kodi/temp/kodi.logYou can also use evtest from the system tools addon, but you have to make sure you've stopped kodi and eventlircd as both of them might grab the input device and thus evtest doesn't report any buttons/keys (evtest will warn you about that). BTW: If eventlircd grabbed the remote input button presses will show up as LIRC events instead of keyboard/input events in kodi.
so long,
Hias
This is a known issue. With the updated firmware it's a lot better (but still not 100% perfect). An updated LibreELEC version (with new firmware) should be released real soon now.
BTW: You can also disable the slide animations in Estuary skin setting if the tearing is too annoying for you.
so long,
Hias
The LE kernel has a built-in initramfs, taking care of the early linux init steps of LE, so using it on another distro won't quite work (it'll have exactly the result you posted).
It's probably easiest to just build a kernel yourself, using the LE kernel config linux.arm.conf
so long,
Hias
Both of the mentioned log files don't seem to give any extra info and simply repeat the error I quoted here. Hopefully this will shed some light on the issue.
Please post the contents of the logfiles, sometimes they contain references to other logs (eg failed dependencies) so it's worth to check them, too.
If in doubt capture the full build log and upload it somewhere (it could be huge, though). eg
ARCH=arm PROJECT=RPi DEVICE=RPi4 make image 2>&1 | tee build.logso long,
Hias
How to build an image for the rpi4 from the Github source? I've tried the build instructions and used device=rpi4 but that doesn't seem to work.
"Doesn't seem to work" isn't too specific. I use this to build RPi4 images:
ARCH=arm PROJECT=RPi DEVICE=RPi4 make imageso long,
Hias
That's probably the well known issue with interlaced video. See here for a fix LibreELEC (Leia) 9.2 ALPHA1 with Raspberry Pi 4B Support or wait for the next LE release (which should be available soon).
so long,
Hias
I don't remember a post on the Milhouse build thread either. The fix was included added in kernel 5.0.8 (and 4.19.35). I found this post though from Matt "Mr. Chromebox" Devo where he wrote that the network issue is fixed in LE 9.0.2 ChromeBox Kodi E-Z Setup Script (LibreELEC/Linux+Kodi) [2017/02/21]
I don't have any Chromeboxes myself, just remembered that the network issue came up numerous times in the Milhouse x86 thread.
so long,
Hias
I haven't tested composite out myself yet but others reported on the RPi forums that they had issues with composite, too Extremly Poor performance with tvout enabled - Raspberry Pi Forums
It's currently being looked into, could be that some firmware fix is needed.
so long,
Hias
Update to LE 9.0.2 or 9.1.001. Slow network performance on Chromeboxes is a known (kernel) issue and should be fixed in newer LE versions.
See also Chromebox - Official Kodi Wiki
so long,
Hias
9.1 are the alpha/beta versions, 9.2 will be the final stable version after finishing alpha/beta tests It follows the same scheme that we used eg for 8.2.
See also the wiki page: Releases [LibreELEC.wiki]
so long,
Hias
Where did you read about the crappy IR-receivers?
Sorry, can't remember, could have been on kodi or intel forums.
Unfortunately IR problems with NUCs seem to haunt a lot of (linux) users. An easy workaround is to use an external USB MCE receiver. The HP branded one for example works fine, it's not exactly a small or beautiful thing but it's well supported in Linux (I have one here too) and rather easy to get (package with HP MCE remote plus IR receiver costs about 15-20 USD shipped from China on ebay).
so long,
Hias
Is it possible the the missing shared library (libssl.so.1.0.0) could cause my problem?
Yes, this is quite certainly the problem. Make sure you have the current tvheadend42 addon installed. Kodi log will show that info, just use the logfile uploader in LE settings and post the link here.
BTW: very often (addon) update problems are caused by slow network initialization (kodi log will show that, too). Enable "Wait for network" in LE settings makes sure the network is up before kodi start and fixes these issues.
so long,
Hias
