Posts by HiassofT

The fix is in our latest nightly build: https://test.libreelec.tv/12.0/RPi/RPi4/…-dd2ecfa.img.gz

morfikcould you please test it?

so long,

Hias

Nightly build with the fix is here: https://test.libreelec.tv/12.0/RPi/RPi4/…-dd2ecfa.img.gz

mokkurkalve could you please test it?

so long,

Hias

Yes. The issue has been fixed now in the RPi kernel https://github.com/raspberrypi/linux/pull/6110 and I'll add that to LE in the next few days.

so long,

Hias

You have to make sure that the voltage stays well above 4.8V all the time.

If it drops below about 4.65V you'll see the undervoltage errors in the log, but USB devices and other stuff running from +5V may already started to work erratically at voltage above that - the minimum spec for USB and other +5V devices is typically 4.75V min.

See also the power supply section of the official RPi documentation https://www.raspberrypi.com/documentation/…ml#power-supply

Note that the current draw / power consumption is highly dynamic and you'll get issues if the voltage drop lasts for a few milliseconds or shorter. Also note that lots of power supplies don't cope well with those dynamic loads, it's essential that they have very fast regulation.

You have to hook up a scope to +5V/GND at the RPi PCB to check that, using a multimeter is useless as it's way too slow.

so long,

Hias

Get a proper power supply (I recommend using the official one) and the issues should be gone.

From the log:

RPi throttled=0x50000
...
Apr 16 23:44:30.671589 LibreELEC kernel: hwmon hwmon0: Undervoltage detected!

so long,

Hias

IIRC long-press isn't supported with CEC remotes (aka your TV remote) in kodi.

so long,

Hias

mokkurkalve can you please give this build a try?

https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.aarch64-12.0-devel-20240415221807-10e57a1.img.gz

I think I spotted a bug in the Hifiberry DAC driver that lead to wrong clock rates at 24bit output. This build should fix that.

so long,

Hias

No, this doesn't happen on the RPi5.

The green line is a bug in the HW-assisted deinterlacer (which only exists in RPi0-4) at 1080i. On RPi5 a software deinterlacer is used (and H264 is also software decoded).

In LE12 you can disable the HW deinterlacer and use a better quality software deinterlacer (BWDIF), but the combination of HW decoding and SW deinterlace caused a kodi crash with your sample file (that's the new issue we found and are investigating now, with our other test videos this combination worked fine).

so long,

Hias

No, and thanks for the sample, we could reproduce the issue (it's a known one) and also discovered another one

so long,

Hias

Update tp LE12 beta, then you can do BWDIF deinterlacing with hardware decoding - there's a new option to disable hardware deinterlacing in player settings.

so long,

Hias

As last year please test with just the TV hat installed.

Also note that the TV hat is running the SPI bus at 50MHz, so adding fancy stacks is likely to cause issues.

so long,

Hias

Please test without the librespot addon and make sure you set the audio output device to ALSA in system->settings->audio.

I suspect pulseaudio (which seems to get enabled by the librespot addon) might be the culprit.

so long,

Hias

Start by replacing the broken 32GB drive

Apr 06 12:51:23.642517 PiKodi kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Apr 06 12:51:23.643238 PiKodi kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Apr 06 12:51:23.643529 PiKodi kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Apr 06 12:51:23.643802 PiKodi kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 95 67 88 00 00 68 00
Apr 06 12:51:23.644082 PiKodi kernel: critical medium error, dev sda, sector 60123016 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2

I wouldn't be surprised if the dying drive causes file buffers to increase until the kernel kills tvheadend as the drive cannot keep up with the amount of data that tvheadend wants to write.

so long,

Hias

Yes, this looks fine (OFC replace 0x00000000 with your actual license).

But, for the 3rd time now, please run vcgencmd codec_enabled WVC1 and post the result and a debug log.

so long,

Hias

Of course you need a licence, and if in doubt add the decode... line to /flash/config.txt.

But IIRC for quite a long time (several years) it's fine if you had entered a valid license key once in the lifetime of the RPi, then the firmware mad the activated license "stuck" and you didn't need to add it on new installations.

Anyways, the vcgencmd codec_enabled command will tell you whether the license is enabled or not so please run that before digging further.

so long,

Hias

Any place in the /flash/config.txt should be fine. Actually, once you have entered a license key it should "stick" so you don't need to edit config.txt anymore.

What does vcgencmd codec_enabled WVC1 report on your RPi?

I did a quick test with LE 11.0.6 on my RPi3B+ (without any keys in config.txt) and VC1 playback worked fine, pressing "o" on the keyboard showed that kodi was using the "ff-vc1_v4l2m2m-drm_prime (HW)" decoder and CPU load was quite low.

LibreELEC (official): 11.0.6 (RPi2.arm)
kodi3:~ # vcgencmd codec_enabled WVC1
WVC1=enabled

Please post a debug log if you can't get it working.

Just add the decode... lines to the end of /flash/config.txt

so long,

Hias

FYI: you can adjust udevil mount options in latest LE11 and LE12 images by copying /etc/udevil/udevil.conf to /storage/.config/udevil.conf and then editing the file. After that reboot so the changes take effect.

Note that you'll also have to adjust allowed_options_exfat in addition to default_options_exfat

so long,

Hias