Posts by Kaspar Winckler

I have created a package for libatomic that allows soloist to run natively. Because the package reuses GCC, it is non-standard. I would therefore be grateful if heitbaum could review it.

LD_LIBRARY_PATH=. ldd soloist
    linux-vdso.so.1 (0x00007fff0de38000)
    libm.so.6 => /usr/lib/libm.so.6 (0x00007fff0bd20000)
    libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fff0bcf0000)
    libdl.so.2 => /usr/lib/libdl.so.2 (0x00007fff0bcc0000)
    libatomic.so.1 => ./libatomic.so.1 (0x00007fff0bc90000)
    librt.so.1 => /usr/lib/librt.so.1 (0x00007fff0bc60000)
    libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fff0bc20000)
    libc.so.6 => /usr/lib/libc.so.6 (0x00007fff0ba90000)
    /lib/ld-linux-aarch64.so.1 => /usr/lib/ld-linux-aarch64.so.1 (0x00007fff0de00000)

LD_LIBRARY_PATH=. ./soloist --version
soloist 1.3.9.4 build 1791547338 (20261009) (g440165f200) (linux/aarch64)

LD_LIBRARY_PATH=. ./soloist --help
Usage: ./soloist -n <name> -k <key> [options]
      ./soloist ctl <command> [options]
Soloist options:
 -h, --help                 Print help message
 -n, --device-name <name>   Device name for Spotify Connect (required)
 -D, --data-dir <path>      Persistent data directory (default resolution:
                            $STATE_DIRECTORY if set by systemd, then
                            $XDG_DATA_HOME/soloist, then
                            ~/.local/share/soloist.
                            For systemd: add StateDirectory=soloist
                            to the [Service] section)
 -C, --cache-dir <path>     Cache directory (default resolution:
                            $CACHE_DIRECTORY if set by systemd, then
                            $XDG_CACHE_HOME/soloist, then
                            ~/.cache/soloist.
                            For systemd: add CacheDirectory=soloist
                            to the [Service] section)
 -z, --cache-size <MB>      Max cache size in MB (min 100, 0 = no limit, default: no limit)
 -d, --pipewire-device <device>  If using PipeWire, route audio to this device (node name/ID)
 -i, --initial-volume <n>   Initial volume 0-100 (default: 40)
 -w, --ws <addr>:<port>     Enable WebSocket API on addr:port (use port 0
                            for OS-assigned; port file written to <data-dir>/ws.port)
 -k, --api-key <key>        Developer API key (required)
 -s, --single-track <uri>   Play a single playable Spotify URI and exit when done
 -p, --pair                 Authenticate via Connect and exit (run once before
                            --single-track to store credentials)
 -v, --verbose              Show all logs
 -V, --version              Print version and exit
Run './soloist ctl --help' for control commands.

Thank you for sharing this, willhunting

According ldd, only libatomic is missing to run soloist natively on LibreELEC 12 and 13. Although the LibreELEC GitHub shows that adding libatomic directly to the base image was discussed and declined, it would be possible to build and bundle it within an add-on. This approach would eliminate the Docker requirement entirely. Doing so excludes running soloist on Windows, but so does the existing reliance on PulseAudio RTP.

I could try to build a package for libatomic for LibreELEC 12.2 for RPi5.aarch64 if you are interested. Let me know.

ldd soloist
	linux-vdso.so.1 (0x00007ffede918000)
	libm.so.6 => /usr/lib/libm.so.6 (0x00007ffedc800000)
	libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007ffedc7d0000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007ffedc7a0000)
	libatomic.so.1 => not found
	librt.so.1 => /usr/lib/librt.so.1 (0x00007ffedc770000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007ffedc730000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007ffedc5a0000)
	/lib/ld-linux-aarch64.so.1 => /usr/lib/ld-linux-aarch64.so.1 (0x00007ffede8e0000)

Thank you for the answer, but THREADCOUNT has no effect on Ninja.

CONCURRENCY_MAKE_LEVEL does.

Throwing it back here for anyone who needs it.

Hello,

I am building packages that require LLVM, and building LLVM either hangs (LE 12) or bails out (LE 13).

This occurs because my system does not have enough RAM and swap space for building LLVM with the default thread count.

I would prefer not to increase RAM or swap space.

Is there a variable I can add to the build command to limit the number of threads used during build?

I am certain there is one, but it rolled out of my command cache, and I can't find one in the code or in this forum.

Thank you in advance for any help with this.

Hello ruud

The first way to set the volume when Kodi starts playing content that I can think of is to set the volume of the TV (or device that feeds your speakers). This is how I do it and have seen it done.

When the initial volume of libespot is set to 100%, librespot/pulseaudio starts playing at the same volume as other contents (audio, video, tv, radio), and the volume of all content can be adjusted in the same manner, usually via the Kodi/CEC or the remote of the TV.

Your question suggests that you are using a specific audio configuration (headless exclusively for Spotify). If so, please elaborate.

Do you play content other than Spotify? If so, how do you adjust the volume?

Hello lutz108

See if the latest version of librespot (12.2.0.3) from the LibreELEC repository fixes your problem

Hello toroB86

I have submitted pull requests #10672 and #10673 that fix our issue.

I hope that the addon will soon be updated in the repository.

Hello,
I have managed to build and run the TBS5520SE drivers for LibreELEC 12.2.0 on RPi5 using this patch.

I had an issue with Librespot lately (it did not show up on my phone anymore).

I uninstalled the add-on and removed the add-on settings while doing so. Then I reinstalled the add-on. My problem was fixed.

I hope that this will work for you too.

The TBS 5520SE drivers for LibreELEC 12.0.2 on Raspberry Pi 5 do not require the commit of post #4 to build and run, because the commit has been committed upstream. Thank you all for keeping TBS 5520SE alive on LibreELEC.

Thank you smp, your solution solves the problem.

Thank you for creating a new thread.

Here is the log: https://paste.libreelec.tv/novel-phoenix.log

Hello,

Thank you for the patches, they work fine for me with LibreELEC 12.0.0 for RPi5.

I have applied them to LibreELEC 12.0.1 for RPi5 (with and without the change of post #5). LibreELEC builds fine, but I am unable to use DVB-C. The log shows "dvb-usb: TurboSight TBS 5520SE error while loading driver (-22)".

I need help to solve this problem.

Thank you in advance