Posts by smf007

Just to document it then, the Kodi changes that are included as part of this commit are what causes the subtitle issue:

Kodi "Piers" by heitbaum · Pull Request #8936 · LibreELEC/LibreELEC.tv

kodi: update to githash d212b0a (July 6 2024) kodi: update to githash d7876de (July 9 2024) kodi: update to githash 060417c (July 14 2024) pcre: drop unused…

github.com

The Kodi delta being:

Comparing 21.0-Omega...060417ccfa5b21939669d404b9a223c3004ba132 · xbmc/xbmc

Kodi is an award-winning free and open source home theater/media center software and entertainment hub for digital media. With its beautiful interface and…

github.com

EDIT :: Looking at that Mesa issue, it looks like that change was only made in 25.0 which wasn't included in the nightlies at that time. I started further bisecting the issue and similarly proved it was not the font scaling. I was able to determine the front to back rendering change is the culprit. The later FBO fix-up has no impact. The default is supposed to be FBO off, so I also tried explicitly setting it to off with no effect.

Quote from forum

There are, actually, LE13 versions that supports internal and external subtitles for the C2 (https://test.libreelec.tv/13.0/Amlogic/odroid-c2/). The latest version that worked for me is the 20240710 nightly.

So LibreELEC-AMLGX.aarch64-13.0-nightly-20240715-a8655f2-odroid-c2.img.gz doesn't work for you?

My understanding is it would have broke on July 18th due to the mesa bump, but the nightly builds had stopped during that time.

Have you turned down the resolution for videos on Netflix? I seem to recall Netflix needs to be set to SD max now, except for specific hardware cases. You'll find the setting for max resolution in the Netflix plugin settings.

Turning the TV off will put the C2 to sleep. That's the default setting for CEC. You can change it in Kodi, system -> input -> one of the entries gets you the CEC configuration.

Regarding the reboot and black screen, you have the reboot error. Instead of rebooting it is essentially shutting down. Seems to depend some on which revision your C2 is and which kernel.

In the logs he had from v13 nightlies, the traceback showed

Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --audio-backend=alsa+pulseaudio'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00000000014f9189 in ActiveAE::CActiveAE::RunStages() ()
[Current thread is 1 (Thread 0x7f1a50ff96c0 (LWP 1168))]

Instead of the generic libc that v12 logs were showing.

So must be something with that mp3 that has a problem there. Maybe run that mp3 through ffmpeg at the command line to check if it shows any errors. The command is something like

ffmpeg -v error -i song.mp3 -f null -

Quote from Da Flex

Since nobody can reproduce the issue, smf007 is maybe on the right track.

Looking over the code, I do not think those settings should have an impact. Visualizations are essentially a secondary sink at a fixed 44.1khz, with the audio buffer being resampled if required.

I haven't been able to reproduce the issue using master on Android. For x86-64 GBM, I have missing libgl errors so visualizations cannot start (this had been fixed a couple years back, so not sure what's changed).

You're seeing the issue on GBM systems, so perhaps a GBM - visualization issue? Occurring only when buffer resampling is required though doesn't make sense.

I might have missed it, but what is your audio output configuration set to?

Audio quickstart guide - Official Kodi Wiki

Settings/System/Audio - Official Kodi Wiki

Quote from chewitt

Luni the subtitle issue is due to Kodi changes from @sarbes that impact Mali 400/450 GPUs. I've flagged the issues to him.

I gather this has not been resolved as I was trying to use them the other day and found them not working. Is there an issue or pull request talking about it? I've seen it stated in passing in xbmc/xbmc#24611 but couldn't find anything further. Thanks.

Looking for some understanding of how Kodi should be responding once it has become an inactive source in CEC.

Setup: Odroid C2 connected to a Panasonic Plasma via HDMI. PS3 and Google Chrome Cast Ultra attached directly to the other 2 HDMI ports on the TV.

A number of Kodi/libreelec versions ago, when the TV would be switched to another input or even a channel, navigating in Kodi would result in the TV input being switched back to Kodi on the C2. Something changed years back that resulted in that no longer occurring. Once Kodi/C2 is the inactive source, it does not bring it back to being the active source. Only manually switching the source on the TV results in Kodi/C2 once again becoming the active source.

When Kodi is the active source, everything works fine. For example, if the TV was off, navigating in Kodi results in the TV being turned on.

So my questions then are:

• Should Kodi be able to force itself back to being the active source? i.e. is something wrong in my current setup?
• If it should still work, is there a libCEC option that I might have wrong?

If it should work, I'll pull the debug logs to look further into it. LibCEC in Kodi though does appear to not log any messages when it is the inactive source. Using cec-client though does show the cec messages that occur while being the inactive source.

A quick test, and haven't noticed any issues with the FFmpeg bump.

chewitt Thanks! That fixed the GUI.

A couple things to let people know:

(1) To close out the widevine issue, it was related to changes in inputstream adaptive and is already resolved per

Thread

joyn / widevine does not work

I installed joyn (ip tv provider) to watch some tv shows in german. Unfortunately, i get an error and the plugin aborts.

In the logs i found this:

(Code, 14 lines)



Anyone an idea whats going on? Is it the wrong widevine that this plugin downloads? Unfortunately i have no netflix, otherwise i would install that addon and see what it downloads.

olze

November 16, 2024 at 6:35 PM

(2) I notice, with the latest bump of Kodi in both the nightlies and chewitt's experimental builds, the GUI no longer renders on my Odroid C2. That is due to a bug in Kodi, looks like the following should correct that https://github.com/xbmc/xbmc/pull/25981 once it is merged.

(3) Found a minor error being thrown related to the clock:

error <general>: SETTINGS: execute # Command failed: /sbin/hwclock --systohc --utc 2>/dev/null

Both the nightlies and chewitt's experimental builds are giving me issues with symbols for libwidevine. Not sure if something changed with libc, this had been working a month or so ago. If need be, I can find time to trace it down to a specific

Quote

error <general>: AddOnLog: inputstream.adaptive: Initialize: Initialize: Failed to load library: /storage/.kodi/cdm/libwidevinecdm.so: undefined symbol: __aarch64_ldadd4_acq_rel

I ran this script, https://github.com/AsahiLinux/wid…devine_fixup.py which adds some stuff for those symbols, resulting in a working library again.

chewitt I see in master that ffmpeg wasn't bumped to 6.1.1. I gather this was due to Kodi having the pull-request to 7.1 ?

Update to ffmpeg 7.1 by sundermann · Pull Request #24972 · xbmc/xbmc

Description Update to ffmpeg 7.0. The most prominent issue is that in 7.0 some members from AVInputFormat became private API. We were using the now private…

github.com

Considering that pull-request seems to have issues at this time, would it be possible to bump the ffmpeg in libreelec master, for only amlogic, to 6.1.1 as you had done above?

chewitt thanks for the kernel bump! We have nightlies again.

Looks like something happened to the nightlies. July 19th is the last one posted.

Quote from special

smf007 any suggestions on which SD card to get?

Sorry, I had gone back to the microSD cards I had gotten when I first got my C2s, so they would be rather old at this point. It's also been a couple years since those issues, so might be possible things have improved in mainline.

If you need a new microSD card though, maybe try asking on the Armbian forum or the HardKernel forum. HK had a thread on the mainline kernel, think a few things about SD card speed was mentioned there
Odroid C2 mainline kernel support - ODROID

Mainline kernel is pickier about the micro-SD card speed than the older kernel. Could be the card speed is too fast. I did have that issue with my C2 and moving back to a slower card made the mainline kernel happy.