Posts by popcornmix

Try swapping the sdcards now. Do the jerks remain with the Samsung?

Quote from dippes

Yes, each of the Pis is hooked up to its own TV.

So can you confirm if the 8GB Pi is the problem or the setup (i.e. swap the two Pi's over and leave sdcard/power supply/cables/TV where they are).

Does the 8GB Pi still have the problem, or is it now with the 4GB Pi?

Quote from dippes

I have two Rpi 4 with Libreelec.10.0.One has 4 Gig and the other 8 Gig Ram.

Do the two Pi's have their own sdcard/cables/power supply/TV connected?

Or are you purely swapping the Pi and using the same sdcard/cables/power supply/TV etc?

Working log has:

DEBUG <general>: CActiveAESink::OpenSink - trying to open device ALSA:hdmi:CARD=vc4hdmi0,DEV=0
INFO <general>: CAESinkALSA::Initialize - Attempting to open device "hdmi:CARD=vc4hdmi0,DEV=0"
INFO <general>: CAESinkALSA::Initialize - Opened device "hdmi:CARD=vc4hdmi0,DEV=0,AES0=0x06,AES1=0x82,AES2=0x00,AES3=0x09"
DEBUG <general>: CAESinkALSA::InitializeHW - Request: periodSize 9600, bufferSize 38400
DEBUG <general>: CAESinkALSA::InitializeHW - Got: periodSize 9600, bufferSize 38400
DEBUG <general>: CAESinkALSA::InitializeHW - Setting timeout to 200 ms
DEBUG <general>: CAESinkALSA::GetChannelLayout - Input Channel Count: 8 Output Channel Count: 8
DEBUG <general>: CAESinkALSA::GetChannelLayout - Requested Layout: RAW, RAW, RAW, RAW, RAW, RAW, RAW, RAW
DEBUG <general>: CAESinkALSA::GetChannelLayout - Got Layout: RAW, RAW, RAW, RAW, RAW, RAW, RAW, RAW (ALSA: none)
DEBUG <general>: CActiveAESink::OpenSink - ALSA Initialized:
DEBUG <general>:   Output Device : vc4-hdmi-0 (vc4hdmi0)
DEBUG <general>:   Sample Rate   : 192000
DEBUG <general>:   Sample Format : AE_FMT_S16NE
DEBUG <general>:   Channel Count : 8
DEBUG <general>:   Channel Layout: RAW, RAW, RAW, RAW, RAW, RAW, RAW, RAW
DEBUG <general>:   Frames        : 9600
DEBUG <general>:   Frame Size    : 16

and non-working has:

DEBUG <general>: CActiveAESink::OpenSink - trying to open device ALSA:hdmi:CARD=vc4hdmi0,DEV=0
INFO <general>: CAESinkALSA::Initialize - Attempting to open device "hdmi:CARD=vc4hdmi0,DEV=0"
INFO <general>: CAESinkALSA::Initialize - Opened device "hdmi:CARD=vc4hdmi0,DEV=0,AES0=0x06,AES1=0x82,AES2=0x00,AES3=0x09"
DEBUG <general>: CAESinkALSA::InitializeHW - Request: periodSize 9600, bufferSize 38400
ARNING <general>: CAESinkAlsa::InitializeHW - Using default alsa values - set failed
DEBUG <general>: CAESinkALSA::InitializeHW - Could not init a valid sink
DEBUG <general>: CActiveAESink::OpenSink - trying to open device ALSA:default

and log file continues with this "could not init a valid sink".

I've just tried and it worked fine for me on latest 10.0.0. My log:

http://ix.io/3z9q

Can I suggest you go to settings/system/audio and "Reset above settings to default", and then just enable "Allow passthrough" and "TrueHD capable receiver". Don't change any other settings in that page. That was enough for TrueHD passthrough to work for me.

This issue should be fixed with latest firmware.

Can you post on here: RPi4 - kodi 19.0 b1 - Dvd menu highlighting not working with some dvd's · Issue #18898 · xbmc/xbmc · GitHub

I think it's the same issue, but it would be useful if others could confirm the issue is scaling when display resolution differs from gui resolution.

Quote from Sjostrand

I have a theory: My case and my micro-hdmi cable don't seem to be fully compatible (it seems like the connector cannot get fully seated) so the connection sometimes fails.

It's not an Argon One case is it? We see a lot of issues reported with those.

If you aren't seeing button presses in debug log then the TV isn't sending them and there is nothing you can do from Kodi's end.

Now it's possible you can do something from the TV's end. Read the manual closely and check all menus carefully.

For example on my Panasonic I can enable extra buttons with a secret remote control code (see here).

That was described in the user manual (but pretty hard to find). If your specific TV doesn't offer that option, then there's nothing that can be done.

I have a Panasonic TV and CEC is fine on a Pi4.

Usually when there is a problem with CEC, you should disconnect all HDMI devices from the TV.

Unplug from mains for a few minutes. Power on TV and connect just the Pi4 through hdmi and power it on.

See if that simple setup works. If it does gradually connect other HDMI cables and check if any cause an issue.

If the simple case doesn't work, I'd be suspicious of the hdmi cable. Some cheaper cables don't actually wire up the CEC lines (or they could be faulty).

Also not all HDMI sockets on TV are the same. There may be some (perhaps labelled PC) that don't support CEC. Test with same socket that you've seen working on a Pi0.

Teddychen can you run

pastebinit /flash/config.txt

and post the url.

Quote from Da Flex

popcornmix The user has video at HDMI-1, but not at HDMI-0.

Ah, in that case I agree. If no picture from HDMI-0 (but HDMI-1 works) on RPiOS, then there's likey a physical problem with HDMI-0 connector.

You should return Pi for a replacement.

The audio issue with Kodi using HDMI-1 is software (only hdmi-0 is supported, and that may be resolved with the LE 10 beta).

But still best to get the faulty Pi replaced.

Quote from Da Flex

HDMI-0 (closest to the USB-C port) is the primary output for A/V. You shouldn't have deal with config.txt for this. Defective device.

I don't think I've *ever* heard of a defective pi that has working hdmi video and non-working hdmi audio (the physical pins used are the same for audio and video).

The issue if either going to be a configuration issue, or some incompatibility with the specific display.

If you have another hdmi display, please try that.

If you have no hdmi audio on a clean install of RPiOS, then try creating an issue here.

Quote from newluck77

Is there something wrong with the hdmi_force_hotplug=1 setting?

LE10/kodi 19 has switched to using arm-side kernel drivers for display, rather than the (closed source) firmware side drivers previously used.

hdmi_force_hotplug (and most display settings) only apply to firmware so will have no effect.

Use getedid (described in previous post) to get the same effect applied to kernel driver.

You need LibreELEC (Matrix) 10.0 BETA version for HD audio passthrough.

Your sample file plays correctly for me on a Pi4.

So, either problem is with your Pi4 hardware, power supply or something wrong on sdcard (incorrect settings/corruption).

Usually an issue with power supply generates an "Under-voltage detected!" message in dmesg, so I'd be surprised if that fixed it.

You could try a clean install to a different sdcard to rule the sdcard contents out.

Ideally, if you could find another Pi4 to test your sdcard/power supply/TV etc with then we could be sure if it's the Pi4 or not.

One last thing. Try adding "gpu_freq=250" and "arm_freq=600" to config.txt. That will make the Pi4 much slower, but I'd be interested if corruption is still present.

Libreeelec 9.2.6 does not support TrueHD passthrough (or DTS-HD) on Pi.

It should be supported on LE 10 beta.

Are you quite sure your soundbar supports TrueHD passthrough? Do you have a link to the specs?

When the video is corrupt, and you bring up OSD, is that clean, or have corruption?

This feels like a hardware issue. Did HW h.264 decode on that board work with LE9/Kodi 18?