Posts by popcornmix

#0  0xf7de4198 in strlen () from /usr/lib/libarmmem-v7l.so
#1  0xf54cfe68 in std::string::operator=(char const*) () from /usr/lib/libstdc++.so.6
#2  0x0037a4a8 in ?? ()
#3 0xf775d330 in ?? () from /usr/lib/libpython3.8.so.1.0

suggests it is a python addon that provokes the crash.

If you enable debug logging before capturing the log it may (or may not) give a clue which addon caused it.

The usual way to track this down is to disable all addons, check the crash has gone and then enable them one by one to identify the culprit.

There is a spidev kernel fix for 5.15.

Hopefully it will appear in nightlies soon.

I'm interested if this issue only occurs with AVR+TV. So connecting directly to the TV, (bypassing the AVR) is of interest.

I'm suspecting the issue won't occur but it would be interesting (and simpler to debug) if TV switches on when directly connected.

What do you see in the audio block after running:

edid-decode /sys/devices/platform/gpu/drm/card0/card0-HDMI-A-1/edid

It's always useful to report when an issue starts with nightlies. If you can report a latest good and oldest bad build it might help narrow it down.

Does anyone have this issue without an AVR connected?

Might be useful if users affected can report make of AVR/TV.

Unfortunately, while I have identified the commit that provokes this behaviour, the commit it correct and is necessary for 4kp60.

The bug looks to be in libcec which is a bit of a mysterious black box.

We have found this behaviour also occurs on a Fire TV stick, so isn't Pi specific.

Check this thread.

At the moment the playback buttons are not being sent, so there's nothing kodi can do to see them.

There may be a secret option to enable this at the TV end (possibly a magic code you enter on remote).

Do you get the popping when listening to hdmi audio?

This issue is discussed here, but it seems to be mostly an issue with hifiberry amp2.

I suspect the hardware generates a pop when switching stream properties (e.g. sample rate).

Does setting system/audio configuration from optimised to fixed help?

Quote from Dozeros

i read here and there that playing with edid files wrongly can damage monitor / screen so i'm a bit scared

I think that is urban myth.

Replied here: https://forum.kodi.tv/showthread.php?tid=365529

You say "in the latest nightly builds".

Does it also occur in older nightly builds, or 10.0.1?

2021-11-15 11:24:26.974 T:1172 INFO <general>: ffmpeg[0x4deb0f0]: Stream #0:0[0x1011]: Video: vc1 (Advanced) (VC-1 / 0x312D4356), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc

See: [Pi 4] Lots of frame drops when playing high bitrate VC-1

H264 Hi10p (10-bit) is not supported.

Quote from luguber

I have the exact same problem. It appeared when I upgraded from LE 10.0.0 to 10.0.1.
I have an r-pi4 which connects to a Pioneer receiver (VSX-1131) which again connects to a Sony TV (KDL-52W4500).

It is quite annoying, but if I turn off the receiver first, I can turn off the TV after, and it stays off.

If you revert back to 10.0.0 can you confirm the problem goes away?

I can't think of anything that might have changed in 10.0.1 to cause that, so I want to rule out some other environmental change

(e.g. a new cec device that's interfering, or TV getting into a bad state).

If you can confirm problem is always present on 10.0.1 and never present on 10.0.0 we can try to narrow it down.

I think you'll need to add to cmdline.txt (on same line) something like:

video=Composite-1:720x576@50i

if you are using LE10. But I don't have a composite display to hand so can't confirm that.

Quote from makima

interestingly enough, a HDR10 encoded media played on a non-HDR10 capable display on Firetv stick plays okay. so it’s RPi4 limitation?

The HDR colour space is much larger than SDR, so there's no perfect way to do this, but tonemapping is an algorithm that squashes the range down in a way that looks okay. I suspect the Firetv stick has hardware support for this, but the Pi doesn't.

HDR10 encoded media played on a HDR10 capable display is supported.

HDR10 encoded media played on a non-HDR10 capable display will not have correct colours.

Quote from burny02

On one of the pi HDMI ports, it works perfectly. However; the other it fails to detect CEC and it appears as if once rebooted, some of the CEC settings revert (HDMI port).

libcec is hardcoded to /dev/cec0 so will only ever work with hdmi0 (i.e. the one closest to power connector).