No time to test yet, but will try soon, but before I want to know is there HW support decoding H264 with Rpi3 and LE11 and 12?
yes
so long,
Hias
Posts by HiassofT
-
-
It's in the system-tools addon
so long,
Hias
-
If your portable hard drive is formatted with NTFS then hook it up to a windows PC and run chkdsk to fix the filesystem errors (older LE versions were more tolerant about them).
VC1 and MPEG2 hardware decoding are still supported on RPi0-3 if you have the license(s).
so long,
Hias
-
It's a tough choice.
Yes, RPi5 feels definitely snappier and has a lot more grunt but it also needs more power (esp. with H264 media which needs to be software decoded) so it will get hotter. We still have to see how that works out in practice with people putting the RPi5 in a case. I suspect the fan will kick in quite often.
Availability is another issue in the next couple of months, RPi4 is on stock everywhere but I don't expect the RPi5 to be broadly available until spring next year (eg mouser currently says the'll have about one thousand RPi5 4GB models - which is next to nothing - available end of January).
so long,
Hias
-
Even the RPi3 can do this. Please test with a current LE version (LE11 or LE12 nightly) on a separate SD card.
RPi0-3 have a hardware limitation so that 192kHz 7.1ch PCM output and TrueHD/DTS-HD passthrough can't work but 96kHz is supported.
Other than that of course your AVR must support 96kHz audio and there are some limitations on software decoding audio (eg the object based audio formats like Atmos are not supported).
so long,
Hias
-
LE 9.2 on RPi4 was a stop gap, using 32bit kernel and a franken-kodi which cross-breeded the old MMAL codec with the new GBM graphics stack. No one should be using that today
The reason we went for that was simply because the old graphics stack didn't support RPi4 and the new v4l2 decoders weren't ready yet. So we had to find some interim hack (which we knew would be throw-away) to get some release out.
64bit kernel in LE10 and now finally 64bit userspace as well in LE12 were the incremental steps we had to do to keep everything going (64bit userspace was held up because there wasn't a 64bit widevine library - which some people need for DRM stuff - available until recently).
so long,
Hias
-
The DTS HD MA files I had here all were only 48kHz but with the lossless DTS-HD HRA kodi showed it was being output at 96kHz
Code
Display More2023-10-23 15:39:54.141 T:1005 info <general>: ffmpeg[0x2eb57130]: Input #0, matroska,webm, from 'smb://lebuild.lan/samples/thedigitaltheater/dts_sfx_short_lossless_1080p-thedigitaltheater.mkv': 2023-10-23 15:39:54.141 T:1005 info <general>: ffmpeg[0x2eb57130]: Metadata: 2023-10-23 15:39:54.142 T:1005 info <general>: ffmpeg[0x2eb57130]: encoder : libebml v1.3.0 + libmatroska v1.4.1 2023-10-23 15:39:54.142 T:1005 info <general>: ffmpeg[0x2eb57130]: creation_time : 2015-04-06T12:06:20.000000Z 2023-10-23 15:39:54.142 T:1005 info <general>: ffmpeg[0x2eb57130]: Duration: 00:00:16.25, start: 0.000000, bitrate: 12175 kb/s 2023-10-23 15:39:54.142 T:1005 info <general>: ffmpeg[0x2eb57130]: Stream #0:0(eng): Video: h264 (High), yuv420p(progressive), 1920x1080, SAR 1:1 DAR 16:9, 29.97 fps, 29.97 tbr, 1k tbn (default) 2023-10-23 15:39:54.142 T:1005 info <general>: ffmpeg[0x2eb57130]: Stream #0:1(eng): Audio: dts (DTS-HD HRA), 96000 Hz, 7.1, fltp (default) ... 2023-10-23 15:39:54.743 T:875 debug <general>: CActiveAESink::OpenSink - ALSA Initialized: 2023-10-23 15:39:54.743 T:875 debug <general>: Output Device : vc4-hdmi-0 (vc4hdmi0) 2023-10-23 15:39:54.743 T:875 debug <general>: Sample Rate : 96000 2023-10-23 15:39:54.743 T:875 debug <general>: Sample Format : AE_FMT_S24NE3 2023-10-23 15:39:54.743 T:875 debug <general>: Channel Count : 8 2023-10-23 15:39:54.743 T:875 debug <general>: Channel Layout: FL, FR, LFE, FC, BL, BR, BC, UNKNOWN1 2023-10-23 15:39:54.743 T:875 debug <general>: Frames : 4800 2023-10-23 15:39:54.743 T:875 debug <general>: Frame Size : 24Note that in general it's recommended to use passthrough. Use PCM output only if your AVR doesn't support the format, but note that software decoding and converesion to PCM is quite limited (eg none of the object formats will work).
so long,
Hias
-
Quick test on RPi5 with DTS HD HRA says yes, both decoding to PCM 7.1 and passthrough work fine (same goes for RPi4 BTW).
so long,
Hias
-
Quick heads up: I've just updated the rpi-tools addon and if builds go well it should be available from the repo in the next few days.
rpi-tools: update addon and build for aarch64 as well by HiassofT · Pull Request #8230 · LibreELEC/LibreELEC.tvupdate gpiozero to 2.0 and switch from RPI.GPIO to the libgpiod-based lg-gpio, like RPiOS did in it's bookworm release Also drop the ancient adafruit libraries…github.comIt updates gpiozero to the current 2.0 version and RPI.GPIO is now gone for good (being replaced by the libgpiod based lg-gpio), aligning with current RPiOS bookworm packages.
Any out-of-tree addons and scripts that are still using RPI.GPIO should switch to gpiozero, otherwise they won't work on LE12.
so long,
Hias
-
Display More
To upgrade:
- Full Backup
- Upload via FTP img file for Pi 5 to ".update" folder
- create in ".update" folder ".nocompat" file
- turn off
- Plugin USB Stick into PI 5 - restart
- Hope
No. Don't turn it off, you need to reboot the RPi4 so the update gets installed.
If that was successful LE won't boot any longer on RPi4 but should work fine on the RPi5.
If you turn it off without installing the update it won't boot on RPi5 (as it's still using the RPi4 installation) and thus the RPi5 update will never get installed.
so long,
Hias
-
Same process for a installation on a USB 3.0 Stick?
Yes.
BTW: If you plan to use USB boot be sure to buy the new official(!) 5A RPi power supply as well - stay away from 3rd party power supplies, testing with those (eg Radxa 5V/5A one) was really depressing, none of them worked reliably.
The old 3A PS is too weak (RPi5 needs a lot more power) and thus USB current will be limited to 0.6A - which isn't enough for most USB3 sticks/SSDs/HDDs etc and the bootloader will loudly warn about that and refuse to boot from them by default. You can override that with a press on the power button or a config.txt entry but I strongly advise against doing that as there's a high risk of data corruption.
With the official 5V/5A PS everything should work just fine and you'll get up to 1.6A (total) for USB devices.
PS: I don't have the official PS yet so haven't verified it myself but I trust the testing done by RPi devs in that matter.
so long,
Hias
-
What I'd really like is an LE11 update which I can apply on my Pi 4, move the SD card to a Pi 5, and it will still work.
I haven't tested it myself yet but a manual "cross grade" on RPi4 (copy RPi5 tar/img.gz to the /storage/.update folder and also create a ".nocompat" file there, then reboot to install it) should work fine.
so long,
Hias
-
Am i right, that LE will release a 11.x version?
That will depend on how testing feedback from our LE11 nightlies will be.
If it's going well we might do a kind of stop-gap LE11 pre-release for RPi5. But keep in mind that it's all very bleeding edge right now so there might be minor or even major issues that we don't know about yet and it'll also not have all the performance improvements (like NEON accelerated deinterlace) as LE12 has right now.
Our main development focus is on LE12 which will take a lot amount of our time as we need to be moving to the next LTS kernel (might be 6.6 or maybe 6.7 - we don't know yet for sure), regularly track latest kodi versions to make sure they work fine (and in case of issues provide feedback to kodi devs) and also tackle a ton of outstanding updates to LE packages and addons.
So if we do an RPi5 LE11release it will be kind of "provided as is, use at your own risk", and if there are issues they might only get fixed in LE12, not future LE11 nightlies (depending on how involved the fixes are).
Still, I hope we can do some LE11 release as that might be a more stable stop-gap for you users than LE12 nightlies (which will become quite rough and bumpy in the next few months).
so long,
Hias
-
Alright, when I have some time, I'll PR the addons so the arm32 devices will attempt to use the arm64 images, which will serve as a stopgap until LE12.
Keep in mind that we also have 32bit-only devices, with 32bit kernels (eg our RPi2 images which is used for RPi2/3 and which are still a significantly large part of our userbase).
You should also cater that, eg by not offering the ls.io addons/repo to those installations at all since it can't work. CvH can provide you info how to properly disable/deprecate/remove your addons/repo for those installations.
so long,
Hias
-
Thanks for reporting back, it's good to know that LE11 has working video so I guess it's one of the other (X11 or maybe kodi) changes then - nvidia driver in LE11 and LE12 seems to be the same version.
BTW: I didn't have much luck with the 535 Nvidia driver on my workstation with RTX 4060, Xorg just crashed.
I guess sending audio to a different HDMI/DP output should be possible, lots of people are doing that on RPi4.
First make sure your amp is detected as a valid video sink: the HDMI audio devices in kodi should have the name (or model number) of your TV/amp/... written next to them (eg something like "Foo Bar on HDMI" )
Also make sure video output on the HDMI/DP port is enabled - check with xrandr.
There's no audio output without video so if the cable or amp is too broken to be detected or if video output on the port is disabled it won't work.
so long,
Hias
-
Do a clean install without any banned addons/repos installed https://kodi.wiki/view/Official:Forum_rules/Banned_add-ons
so long,
Hias
-
Hi,
About AV1, does LE use [dav1d](https://code.videolan.org/videolan/dav1d) decoder? Maybe RPi5 is powerfull enough to make it run?
yes - scroll back a page, this was already discussed
so long,
Hias
-
Can you test if the LE11 nightly Generic Legacy image works?
https://test.libreelec.tv/11.0/Generic/Generic-legacy/
The graphics driver seems to be working, kodi detected the card but it's showing repeated xrandr errors - that could also be due to some X11 changes in LE12 (not really sure though).
BTW: the quadro P400 isn't that old, looks like it was released in 2017, and the current nvidia drivers still support it.
so long,
Hias
