Posts by TomMnemonic

Great, thanks for the help.

Quote from popcornmix

Opus is a common audio encoding and is supported.

The crash is in libass, so it's subtitle related.

Are you able to create a cutdown file that exhibits the crash?

It will obviously need to include the subtitle track.

(e.g. use ffmpeg to create a 2 minute cut of file, and confirm it still crashes).

Here is a 1min cut (from the beginning) of the file that includes all the original video/audio/subtitle tracks. As it is 1min from a 2hour movie for all intents and purposes that would be considered fair use. I confirmed it still crashes my raspberry kodi system but works on windows.

Quote from Da Flex

Also test latest LE 11 from here: https://test.libreelec.tv/11.0/RPi/RPi4/

I have tested the latest LibreELEC-RPi4.arm-11.0-nightly-20230213-0b6ce71 build and the sample file above works without any issues - does not crash; video/audio/subtitles are all working. Here is a kodi.log of the file running if it helps:

http://ix.io/4o0r

Quote from Da Flex

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

Debugging enabled, uploaded both the kodi.log and crash.log via system settings as advised:

http://ix.io/4nV0

http://ix.io/4nUZ

Quote from MatteN

The .opus is a fileformat developed for webstreaming, not sure if its supported.

I can see it being mentioned briefly as supported on the kodi wiki and a few people on reddit saying they are using it without issue:

Music tagging - Official Kodi Wiki

r/kodi on Reddit

Does Kodi 18 support Opus audio? - 9 votes and 14 comments

www.reddit.com

I've been using LE since 9.x, and this is the first time I've seen a video file that crashes the system. I have a Raspberry Pi 4 with 4GB ram.

I tried running the file after temporarily resetting the settings(didn't help), i.e.:

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

This is the crashlog I retrieved from /storage/.kodi/temp/kodi_crash.log immediately after the crash:

Detailed info for the file(1080p HEVC, 4Gb, Opus, ASS) here:

The file works without issue on Windows 10 using VLC.

I just use different buttons to turn TV on and off, and execute an appropriate python script. CECToggleState seems to be iffy with some TVs, so I only use CECActivate and CECStandby.

import xbmc

xbmc.executebuiltin('Action(stop)')
xbmc.executebuiltin('activatewindow(home)')
xbmc.executebuiltin('CECStandby')

<keymap>
<global><keyboard>
<key id="61622">runscript(special://masterprofile/turn_on.py)</key>
<key id="61656">runscript(special://masterprofile/turn_off.py)</key>
</keyboard></global>

<pvr><keyboard>
<key id="61622">runscript(special://masterprofile/turn_on.py)</key>
<key id="61656">runscript(special://masterprofile/turn_off.py)</key>
</keyboard></pvr>

<fullscreenvideo><keyboard>
<key id="61622">runscript(special://masterprofile/turn_on.py)</key>
<key id="61656">runscript(special://masterprofile/turn_off.py)</key>
</keyboard></fullscreenvideo>
</keymap>

Quote from popcornmix

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

Thank you. That worked perfectly.

Alternatively, is there any way I can resolve this issue manually just for myself via command line/config files in a non-dev build? I've tried the new LE 10.0.3, and the issue remains so I'm still stuck with LE 10.0.0.

Quote from popcornmix

You said you fixed it with "vc4.inval_delay=0 vc4.cec_debug=0x100".

Have you fixed it with "vc4.inval_delay=<some number> vc4.cec_debug=0"

If not, there's no point adding a gui option to adjust the delay for you.

Ah, apologies, I naively assumed vc4.cec_debug adds some verbose logs to help debug problems or something like that. Did not realize it can actually affect anything.

The results when adding to the end of the "/flash/cmdline.txt" file:

vc4.inval_delay=0 vc4.cec_debug=0

TV does not switch on.

vc4.inval_delay=3000 vc4.cec_debug=0

TV switches on as long as I send CECActivateSource within 3 seconds. Does not switch on if I wait longer (e.g. 5-7seconds).

vc4.inval_delay=5000

TV switches on as long as I send CECActivateSource within 5 seconds. Does not switch on if I wait longer (e.g. 10seconds).

vc4.cec_debug=0x100

TV always switches on when I send CECActivateSource.

Then my question is, what does vc4.cec_debug=0x100 do and why does it fix my case? Is it something that can be added in the options instead of delay? Or is there a way to fix whatever that is affecting me? I'm happy to try anything else if it helps.

I've tried the dev build and added "vc4.inval_delay=0 vc4.cec_debug=0x100" in cmdline.txt file (as per link below) which has resolved the issue for me. From what I understand the delay was set to prevent the TV from inadvertently turning back on after shutting down. With the standard delay of 1000ms (1sec) you would expect to be able to turn the TV back on almost immediately. In my case, however, waiting for 5 seconds or 2 minutes did not help and the TV was not waking up at all via CECActivateSource.

Post

RE: TV/AVR turns back on right after turning them off

There is a test build here.

Place in /storage/.update and reboot to update. It's a Matrix build with some kernel debug options added.

By default it should behave the same as official release. But you can try some modifications by adding options to /flash/cmdline.txt

The default behaviour delays invalidating cec address when hotplug is deasserted for 1000ms (in case it gets reasserted).

That fixes the AVS off/on problem for me with a Panasonic TV and Onkyo reciever.

Try with vc4.inval_delay=5000…

popcornmix

March 27, 2022 at 9:50 PM

Would it be possible to add the option within the GUI to adjust this delay?

Quote from Mayoru

not sure if the same source, but since 10 we sometimes have to manually select Anynet+ on my Samsungtv to be able to ue the tv-remote on kodi.

Sadly, the issue is not remote-exclusive, as sending commands directly to raspberry via ssh still has no desired effect.

Hello,

My specs:

JVC LT-55C550 TV

Panasonic SC-HTB488EBK Soundbar

Raspberry Pi 4 Model B

LibreELEC 10.0.1 & 10.0.2

Never had this issue in LE 9.* or 10.0.0. Also, downgrading to LE 10.0.0 from 10.0.1/10.0.2 immediately resolves the problem.

The soundbar and the raspberry have no direct connection with each other. Instead, they are connected with their own respective HDMI cables to ports 1 and 3 on the TV.

After switching the TV off with "CECStandby" command, issuing "CECActivateSource" has no effect. I normally use a Flirc remote to issue the commands via script, i.e:

runscript(special://masterprofile/turn_on.py)


import xbmc
xbmc.executebuiltin('CECActivateSource')

However, I also tried sending the command via ssh kodi-send -a "CECActivateSource" which again yields no results (but does work on earlier LE versions).

Disconnecting the soundbar, restarting the raspberry, and then reconnecting the soundbar resolves the issue temporarily. But, if the raspberry is shutdown/restarted again with soundbar connected, the issue returns.

I've searched the forum, but most issues I found relate to CEC not working at all, not just the one command. The few things suggested from those topics that I tried:

- Put `hdmi_force_hotplug=1` in config.txt

- Buy a new microhdmi cable and make sure it's connected in the raspberry port closest to the power port

- Cut off power to TV for 20min

- Tried "CECToggleState" instead of "CECActivateSource", but that command never worked consistently even in the older versions, and it's no better in the new ones

CECActivateSource stopped working for me after the update. But CECStandby was still working. Tried restarting my Rpi4 and cutting the power to the TV without luck. Reverted back to 10.0.0, and the functionality immediately came back.