The firmware fix is in rpi-update firmware. It should be picked up by LE in the near future.
Posts by popcornmix
-
-
You need an edid to be provided by display to be able to choose a suitable output mode.
My guess is yours doesn't.
If you power on, connected to display with no sdcard or usb connected do you see the diagnostic screen?
What does the "display:" line report?
-
-
We've had a look. The unusual feature of the file is the SPS/PPS headers initially report the aspect ratio, then at ~2mins stop reporting it. While that is not illegal, it is strange and it triggers a bug in the firmware processing (it repeatedly reports "aspect ratio has changed", but as there is no aspect ratio to update to, that condition never stops).
I've had a go at fixing firmware. The guy show needs to sign off on this is on holiday, but you could test it from here.
Extract start4x.elf and fixup4x.dat and replace the files start.elf and fixup.dat on the first partition of your sdcard.
(Keep a copy of the original versions just in case).
-
I can reproduce - I've asked our codec guy to take a look.
-
The information you have linked to is over 7 years old and doesn't apply. Don't try this.
-
Okay so that matches:
2024-03-31 (726b493): #8780 kodi-binary-addons: update to latest version
which I believe you are reporting as broken, and the previous build you are reporting as working:
2024-03-30 (ae242cb): #8778 linux (Dragonboard): drop EXT2_FS to match other targets
It looks like there was only one commit between those two builds: https://github.com/LibreELEC/LibreELEC.tv/pull/8780
and that only affects binary addons. Is your issue with local files, or using an addon?
-
I'm not seeing a 1st April nightly here: https://test.libreelec.tv/12.0/RPi/RPi5/
I do see 3rd April had an unwanted kodi bump that was bumped back on 4th April.
Does 4th April nightly also have the issue?
-
SO, it's obvious this is a command to the chip that turns it off or on. And it remembers.
No. There is no command that disables hdmi and remembers it (other that manually editing configuration files).
-
Soooo... first thanks for the help and second, how come gpu_mem=96 isn't the default instead of 76?
The Pi's hardware video decoder is designed for level High Profile, level 4.1 H.264 encodes, as used by Blu-Ray.
We'll play any file encoded to that format with the default gpu_mem.
My guess if your file has been badly encoded (possibly a large number of reference frames requiring level 5).
You may be able to play these with increased gpu_mem (but it's not guaranteed). Best to avoid these encodes if you can.
-
-
With no sdcard inserted and just hdmi and power connected you should get a diagnostic display.
If you don't, then make sure bootloader is up to date (the Raspberry Pi imager has a option to update the bootloader).
-
Have tried delaying the start of the Raspi a while after the AVR but does not help so far. No biggie but reported FWIW.
Have you tried using get_edid create?
-
It's worth testing with video acceleration disabled.
In settings/player/video disable "Use DRM PRIME decoder".
Any change?
If it avoids the issue, then it it suggests the problem is in the hw accelerated codec.
If it doesn't (which I suspect is more likely), then it's a kodi/addon issue and best pursued on kodi forum.
-
Hi, I have the same probleme. Did you find a solution to use this DAC with kodi on rpi5?
Can you try a nightly LE12 build? There may be kernel fixes that aren't in the stable LE11 build.
-
This doesn't sound like a LibreELEC issue.
And USB isn't something I know too much about.
I'd suggest opening a kernel issue and describing the issue,
where a USB expert may have better advice.
If you can reproduce the issue with RPiOS then that would be even better (as there may be more debugging tools available).
-
My videos are encoded as AVC 5.1 with 16 reference frames, and will only play audio, the screen freezes and GUI elements start leaving trails on the screen. If I press top, the screen returns to normal.
The Pi hardware decode is only specced for level 4.1 (which is the BluRay standard).
Don't encode videos like that.
If you set gpu_mem (in config.txt) high enough, the videos will probably play, but you may have issues with the reduction in arm side memory this results in.
-
I did fix this (locally) a while back, but it does involve bumping libcec (RPiOS uses a newer, modified libcec which doesn't hard code that), which LE may be reluctant to do. But it did work.