spotifyd icon indicating copy to clipboard operation
spotifyd copied to clipboard

linux-armhf-full doesn't have pulseaudio as backend

Open desolateunicorn opened this issue 3 years ago • 1 comments

Description I've downloaded the three most recent linux-armhf-full binaries and after running spotifyd --help. The backend options shows only The audio backend to use [possible values: alsa].

To Reproduce Steps to reproduce the behavior:

  1. wget https://github.com/Spotifyd/spotifyd/releases/download/v0.3.3/spotifyd-linux-armhf-full.tar.gz
  2. tar xzvf spotifyd-linux-armhf-full.tar.gz
  3. ./spotifyd --help
  4. See -b, --backend <string> The audio backend to use [possible values: alsa]

Expected behavior The pulseaudio backend should be available.

Logs

Click to show logs
<!-- PLEASE PASTE YOUR LOGS BELOW THIS LINE WHEN REPORTING BUGS. Make sure to run spotifyd using the `--verbose` flag -->
spotifyd 0.3.3
Simon Persson <[email protected]>, Sven Lechner <[email protected]>
A Spotify daemon

USAGE:
    spotifyd [FLAGS] [OPTIONS]

FLAGS:
        --autoplay                Autoplay on connect
        --debug-credentials       Whether the credentials should be debugged
    -h, --help                    Prints help information
        --no-audio-cache          Disable the use of audio cache
        --no-daemon               If set, starts spotifyd without detaching
        --use-keyring             Enables keyring password access
    -V, --version                 Prints version information
        --verbose                 Prints more verbose output
        --volume-normalisation    Enable to normalize the volume during playback

OPTIONS:
    -b, --backend <string>                         The audio backend to use [possible values: alsa]
    -B, --bitrate <number>
            The bitrate of the streamed audio data [possible values: 96, 160, 320]

    -c, --cache-path <string>                      The cache path used to store credentials and music file artifacts
        --config-path <string>                     The path to the config file to use
        --control <string>                         The control device
        --device <string>                          The audio device
    -d, --device-name <string>                     The device name displayed in Spotify
        --device-type <string>
            The device type shown to clients [possible values: computer, tablet, smartphone,
            speaker, tv, avr, stb, audiodongle]
        --initial-volume <initial_volume>          Initial volume between 0 and 100
        --mixer <string>                           The mixer to use
        --normalisation-pregain <number>
            A custom pregain applied before sending the audio to the output device

        --on-song-change-hook <string>
            A script that gets evaluated in the user's shell when the song changes [aliases: onevent]

    -p, --password <string>                        The Spotify account password
    -P, --password-cmd <string>
            A command that can be used to retrieve the Spotify account password [aliases: password_cmd]

        --pid <pid>                                Path to PID file
        --proxy <string>                           The proxy used to connect to spotify's servers
        --use-mpris <use-mpris>
    -u, --username <string>                        The Spotify account user name
    -U, --username-cmd <string>
            A command that can be used to retrieve the Spotify account username [aliases: username_cmd]

    -v, --volume-controller <volume-controller>
            The volume controller to use [aliases: volume-control]  [possible values: softvol,
            alsa, alsa_linear]
        --zeroconf-port <number>                   The port used for the Spotify Connect discovery 

Versions (please complete the following information):

  • OS: Raspbian GNU/Linux 11
  • Spotifyd: v0.3.3
  • cargo:

desolateunicorn avatar Jan 22 '22 20:01 desolateunicorn

Thank you for the report! There are currently several pressing issues with CD and #992 was/is an attempt to fix that. Unfortunately, configuring that correctly is quite complicated due to the many hoops one has to jump through to cross build with all the non-rust libraries, this project depends on. This is probably also the reason, why pulseaudio isn't enabled by default on armhf.

Nonetheless, you can always try to compile spotifyd yourself on the RPi. (I've done it several times already myself, it takes quite some time, but it's much easier than cross building in my experience.) See here for some very rough instructions. Then you can decide, yourself, which features you'd like to enable.

eladyn avatar Mar 02 '23 22:03 eladyn