Posts by chewitt

2025-03-09 06:19:04.211 T:13590   debug <general>: ADDON: Dll Initializing - Sidplay Audio Decoder
2025-03-09 06:19:04.211 T:13590   debug <general>: SECTION:LoadDLL(/storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.20.2.0)
2025-03-09 06:19:04.211 T:13590   debug <general>: Loading: /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.20.2.0
2025-03-09 06:19:04.211 T:13590   error <general>: Unable to load /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.20.2.0, reason: /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.20.2.0: undefined symbol: _ZTI7SidTune

It's so much more helpful when you post a log file with the actual error. You need to report it in Kodi forums to the add-on maintainers.

I forget the exact command, but you can change mixer config with "amixer sset" commands. On boot the soundconfig script is run by udev (which provides the card device as the $0 variable), see:

LibreELEC.tv/packages/audio/alsa-utils/scripts/soundconfig at master · LibreELEC/LibreELEC.tv

Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.

github.com

You cannot overwrite the soundconfig script as it's embedded in the read-only part of the OS, but you can create an autostart.sh script to run a command to change the mixer controls on boot, or (better, as it supports more precise scheduling) a systemd service that runs the command before Kodi starts.

Two threads that might (or might not) help:

Thread

Raspberry 7" Touchscreen Rotation LE 11.0.3

I have a Raspberry Pi 3B with the official 7" touchscreen in a frame and have upgraded from LE 9.2.8 to 11.0.3. In order for the display to be the correct way up I added lcd_rotate=2 to config.txt in LE 9.2.8. This worked perfectly.

Since updating to 11.0.3 I have been unable to rotate the screen. Below are the four separate additions to config.txt tried unsuccesfully.

dtoverlay=vc4-kms-dsi-7inch

video=DSI-1:800x480@60,rotate=180

dtoverlay=vc4-kms-dsi-7inch

panel_orientation=upside_down

…

jcpreston

August 12, 2023 at 1:14 PM

Thread

Video Orientation

I decided it was time to update my Pi 2 running 9.2.8 to a Pi4 running 11.0.3. which was easy to do but now I have some changed behaviour with video orientation:

On some of my home videos which were shot inverted I could change the orientation using either the metadata or by 180 degree rotation, no problem and it seemed to work seamlessly on the earlier version.

With the newer version on the same videos from my server I can change the orientation by 90 degrees but selecting metadata or 180…

BillB

September 19, 2023 at 2:14 PM

I looked at the log, but mostly I saw filenames that indicate torrented/pirated media so I didn't look much further. Viel Glück.

There are also lots of inexpensive audio HAT devices that will give you an S/PDIF output direct from the RPi to AVR.

LE doesn't package i2c utilities into the core image as they're not normally required, but the System Tools bundle add-on in the LE repo contains i2c-tools. The user response in the first thread you linked Help installing DDCUTIL also suggests copying the ddcutil binary from an Ubuntu image worked, so perhaps Ubuntu compiles it static whereas RPiOS compiles it shared? You can avoid the need to install Ubuntu by downloading the .deb package from online resources and unpacking it with ar x file.deb on LE to get the binary, then use ldd to see if it's static and usable.

NB: Another possibly useful thing is the "Turn Off" screensaver in the Kodi repo. It will normally trip shutdown/wake on a monitor instead of showing pretty things on-screen.

Quote from Hawkeye72

Could you perhaps give me a more specific hint?

Nope. I have enough architectural knowledge of Kodi to know the API is the correct way to make a remote device play something, but I've never needed to do anything with JSON-RCP myself, and thus have no knowledge to share.

That said, have a look at how "kodi-send" wraps API commands?

The better place to ask Q's will be the Kodi forum.

Note that it's possible to install the NTFS-3G driver add-on; the OS will then use them to mount NTFS drives instead of the in-kernel drivers, thus replicating the experience of older LE versions.

Like any modern internet-enabled app, even you're not actively watching a movie Kodi is doing "something" in the background, so will make connections to external services and those typically require a DNS lookup to be done; hence you see connections on port 53 (DNS) to 8.8.8.8/8.8.4.4 which are Google DNS servers. These are the default DNS servers we configure in the OS, so they will be used unless DHCP provides something different (and often routers might provide them too). Can you stop it? .. probably not without disabling addons and functionality. Is it an issue? .. also probably not. If you suspect something bad is happening you'll need to look deeper into the network traffic using something like WireShark to sniff and see what's actually being looked-up (as the router isn't logging anything forensically useful like the actual queries).

As written above, Kodi does not support dual-screen output and LE does not support mirroring.

The question is a little off-topic for this forum since it's all about Kodi itself and nothing specific to LE use.

You need to use the JSON-RPC api, so start reading here: https://kodi.wiki/view/JSON-RPC_API

You can (or should be able to) automate mounting with udev. See https://github.com/openzfs/zfs/tree/master/udev/rules.d

It's unclear where in the interface you are seeing the problem, but it's probably in Kodi core or the Estuary skin.

If in Kodi core, the Dutch localisation was installed through an add-on, so the files are in /storage/.kodi/addons/ and you can edit them and restart Kodi (or reload the skin via kodi-send commands) to effect the change. Note that any bump to localisation addon upstream will result in the addon updating int he background and your changes will need to be reapplied.

If in the Estuary skin, the translations are contained in the skin addon which is embedded in the read-only part of the LE filesystem under /usr/share/kodi/ and you cannot edit this location. So you need to clone the skin to /storage/.kodi/addons, then change the skin name and change the translation, then select/enable the modified/renamed skin in Kodi settings. Note that any changes to the upstream skin will not be automatically applied. Probably not a big deal but skins do receive maintenance fixes over time.

If you want to fix the root cause for the future, you need to register with https://kodi.weblate.cloud/ and submit a change to the required set of translations; either Kodi core or the skin (wherever the translation resides) and then it'll end up in the LE image via maintenance updates that we make over time.

The alternative option is educating the user to understand that "Instellen" is how/where you setup? movie sets.

The BlackCatDevel0per patch with pinctrl-0 = <&spdif_out_h_pins>; uncommented in the &aiu node looks complete to me.

ACODEC (Analog CODEC) is used for the 3.5mm jack present on Android boxes. You shouldn't need any of that for a VIM2 board.

Are you using the Khadas DAC board or trying to wire pins from the GPIO header?

Kodi does not support dual-screen output on any OS, and does not support mirrored output on Linux without running under some kind of Windowing environment that provides that function; and LE either runs with no windowing environment (Generic) or one that is intentionally the bare minimum to support X11 output (Generic-Legacy). You'll need to experiment with a conventional Linux distro or Windows to have dual-displays working. Or you use some kind of hardware device in the HDMI output chain to switch between TV and Projector, although Kodi only detects the available resolutions and audio capabilities for it's output device (not devices) during startup so unless both devices have the same capabilities, switching the HDMI output between devices post-boot may run into problems.

Quote from balbes150

the performance of the 3588 is so high that it does not require HW decoders for video playback up to 4K in the banal SW mode

RPi5 is the same for common media formats. Codecs are not a barrier to an LE image, but HDMI needs to be reliable. I think Jonas is still working on some HDMI support.

Quote from THRobinson

Resolved... one of those cases where it was two problems at the same time,

PEBKAC

Deprecation is normal and nothing bad (hence it's a warning in the log, not an error). It's a necessity for handling a diverse set of clients. OpenVPN won't upgrade the connection from CBC to GCM but the initial handshake exchanges a list of what's supported and then the client will negotiate with the server on what to use; generally starting from best to worst.

It's simple enough to start an OpenVPN connection on boot using a systemd service. You can crib the process from the WireGuard service sample in /storage/.config/system.d.