Posts by popcornmix

this might be it: llctl

If I revert the backport of this PR (https://github.com/xbmc/xbmc/pull/21410), the closed caption subs work again.

Interestingly with it working, kodi sees one subtitle stream.

With it not working kodi sees two subtitle streams (but neither show anything).

I've pinged the dev, so may be no need for the issue if they can reproduce issue.

I can play that stream (in UK). And it doesn't have close captions on LibreELEC on Pi.

It does have closed captions on VLC.

I installed kodi on Ubuntu 22.10. It describes itself as:

Kodi from Debian (20.0-ALPHA2 Debian package version: 2:20.0~alpha2+dfsg1-1build1). Platform: Linux x86 64-bit

and it behaves the same as kodi on pi. No subs or closed captions visible (although I can choose between two options).

As this seems to be a general kodi issue, it's best to report it here.

Make sure you follow the template, include a debug log, indictate which versions of kodi this worked on, and which it fails on

Include the URL to reproduce the issue, and hopefully someone who knows this code can help.

Can you test with "Allow hardware acceleration with DRM PRIME" disabled?

If that works, test with "Allow using DRM PRIME decoder".

I know the streams may not play well with these options disabled, but it may narrow down where the problem lies if you confirm if closed captions start working.

It would be helpful if you can find a file that has the issue that isn't geolocked.

Yes, disabling DRM Prime isn't recommended but provides a workaround if you just need to screenshot video occasionally.

Quote from ghtester

Perhaps not an important feature for most users but the screenshot command still does not work in LE 10/11 (it does not save the screenshot picture like in release 9.x but only the active GUI screen).

Assuming this is an occasional requirement, if you disable DRM Prime in video acceleration settings first, I believe screenshot will work.

Use 10.0.3 and add "vc4.force_hotplug=1" to cmdline.txt (on end of existing line).

The things you mentioned are all normal and occur on my system with working audio.

Another display would be a useful test.

Also if your current display has another hdmi port try that.

I don't see any audio errors in log (it looks much like mine).

Can you confirm if any local setting are causing the issue? Simplest way is to ssh in and:

systemctl stop kodi
mv /storage/.kodi /storage/.kodi_back
systemctl start kodi

You should now have kodi running with default settings. Any audio from navigating gui or playing a video?

If you want to return to your old settings then:

systemctl stop kodi
rm -rf /storage/.kodi
mv /storage/.kodi_back /storage/.kodi
systemctl start kodi

Quote from Deri

I have noticed that the latest nightly does have the same kernel oops as in the original log. So favourite is the popcornmix fix scheduled for linux 6.1, maybe it has not been back ported to 6.0.5 properly.

You are correct. I've just checked and the fix from 6.1 is missing from 6.0 tree. I've cherry-picked it to rpi-6.0.y, so should appear next time LibreELEC bumps their kernel version (probably best to wait for confirmation here, as that's not an automatic process).

I believe a backport of the VC-1 patches are in current LE. e.g. see https://github.com/LibreELEC/LibreELEC.tv/pull/6538

I think errors like "mmco: unref short failure" are common when source is live TV (where there may be errors in stream, or it may start from a non-I frame). I don't think it fatal for playback.

But otherwise I don't know much about non-pi kodi, especially the audio drivers (which sounds like where the issue is).

Quote from Deri

Kodi is left running all the time and the LG is put into standby with the remote. After a while, the TV is restarted and the message no video signal appears.

Looks like you are using the Nightly/kodi 20 build. I assume that stable/matrix build works okay?

The error relates to i2c, and may be fixed by this.

Quote from Cpedregal

This weekend I'm visiting my mother, I can test two more displays there.

That would be useful. If it works on both of those, then it suggests your original TVs have an issue we don't cope well with.

If they also fail, then it's not the TV, but something related to the pi (what's on sdcard, or pi hardware or hdmi cable).

Is there any type of file that makes them occur more frequently?

Finding a use case that can reliably reproduce the issue without too much waiting will make debugging easier.

Quote from Cpedregal

I’m using the original cable included with the RPI. Tried to include”hdmi_force_hotplug=1“ in config.txt, but it doesn’t solve the problem.

In general, hdmi_* lines in config.txt apply to deprecated firmware display driver.

A more suitable line would be to add:

video=HDMI-A-1:1920x1080@60D

to the end of cmdline.txt (on the same line).

For testing you can also try switching to the fkms driver. In /flash/distroconfig.txt change:

dtoverlay=vc4-kms-v3d,cma-512

to

dtoverlay=vc4-fkms-v3d,cma-512

Can you confirm that you have two displays that behave this way?

One display that doesn't play nicely would be surprising, two seems very unlikely and may suggest an issue elsewhere (but your issue is not affecting the vast majority of users).

Can you confirm you don't have a case with hdmi extenders?

Quote from Shazb0t

well, I've updated to 10.0.3 and this problem is instantly back. Do we still need to edit the cmdline.txt in 10.0.3 or was this supposed to be resolved permanently? Thanks!

The command line will always be required if you have equipment that is affected by this issue.

It looks like this should be supported.

HiassofT can you think of a reason for sink to fail to open?