[SOLVED] Spotify connect problems

Max2Play Home 2016 (en) Forums Max2Play Add-ons [SOLVED] Spotify connect problems

This topic contains 43 replies, has 10 voices, and was last updated by  flysurfer Moderator 1 month, 1 week ago.

Viewing 14 posts - 31 through 44 (of 44 total)
  • 21. März 2018 at 10:30 #34589

    Hi Stefan,

    The latter output is that of a working system. Please make sure your other players are not occupying the output device you want to use.

    24. März 2018 at 1:54 #34710

    hi, Heiner – Spotify Connect has been stable and working well for the last two weeks. If we run into trouble we will update to beta and reinstall Spotify Connect. Thanks for all your help.

    11. Oktober 2018 at 8:13 #38541

    Since the time, I have been reading news the things are going normal for me.
    Men a Liet

    13. Juni 2019 at 13:59 #45731

    Hi,

    I’m also having no sound issue with the spotify connect plugin. Even through it’s running and I can select it in the Spotify app, there is no sound. It used to work the few first times.

    There is no other audio player running, I closed the squeezebox server, disabled the build-in audio.

    Hardware: HifiBerry Amp2 + RP3B+

    Thx for any help

    14. Juni 2019 at 9:14 #45746

    Hi nipape,

    Can you copy the debug info log from the plugin here? Also, have you tried Spotty and encountered the same issue, yet?

    20. Juni 2019 at 18:46 #45882

    Hi,

    Thx for the reply and apologies for the late answer.

    I managed to make it work by installing from scratch on a temporary SDCard. But when installing again on another it doesn’t work anymore.

    Here are the logs from the DEBUG:

    #### Librespot Output ####
    INFO:librespot: librespot 431be9e (2018-05-18). Built on 2018-05-30. Build ID: YlMJ8i49
    INFO:librespot_core::session: Connecting to AP „gew1-accesspoint-a-khl6.ap.spotify.com:4070“
    INFO:librespot_core::session: Authenticated as „######################“ !
    INFO:librespot_playback::audio_backend::alsa: Using alsa sink
    INFO:librespot_core::session: Country: „FR“
    INFO:librespot_playback::player: Loading track „Trois nuits par semaine“ with Spotify URI „spotify:track:3X9XJLwQPWqRnsNaL9z6ss“
    INFO:librespot_playback::player: Track „Trois nuits par semaine“ loaded
    INFO:librespot_playback::player: Loading track „Un été français“ with Spotify URI „spotify:track:4Ngeca4zs304bDnDh3pjzI“
    INFO:librespot_playback::player: Track „Un été français“ loaded
    INFO:librespot_playback::player: Loading track „Un été français“ with Spotify URI „spotify:track:4Ngeca4zs304bDnDh3pjzI“
    INFO:librespot_playback::player: Track „Un été français“ loaded

    #### Librespot Command Line Options ####
    error: Required option ’name‘ missing
    Usage: /opt/spotifyconnect/librespot [options]

    Many thanks for your help.

    • This reply was modified 8 months, 1 week ago by  nipape.
    20. Juni 2019 at 22:56 #45885

    I now get this error

    ALSA lib pcm_hw.c:1713:(_snd_pcm_hw_open) Invalid value for card
    ERROR:librespot_playback::audio_backend::alsa: Alsa error PCM open -19
    ERROR:librespot_playback::player: Could not start audio: Alsa error: PCM open failed

    21. Juni 2019 at 11:11 #45886

    Hi nipape,

    The new error indicates that you have the wrong parameters for your sound card. Make sure you have the right output device selected and please paste any other parameters of the player here as well. It looks like Spotify is using the built-in Pi sound card instead of the amp. Check to see that „sysdefault_hifiberry…“ is selected and no other player is running concurrently with the same card.

    Also, as I’ve mentioned, the Squeezebox Server solution Spotty is a great multiroom-capable alternative that also supports Spotify Connect.
    Here’s a tutorial on setting it up

    21. Juni 2019 at 11:18 #45889

    I reinstalled everything from scratch, and it still doesn’t work even through I’m back to the „no error“ logs:

    #### Librespot Output ####
    INFO:librespot: librespot 431be9e (2018-05-18). Built on 2018-05-30. Build ID: YlMJ8i49
    INFO:librespot_core::session: Connecting to AP „gew1-accesspoint-a-jq5f.ap.spotify.com:4070“
    INFO:librespot_core::session: Authenticated as „####################“ !
    INFO:librespot_playback::audio_backend::alsa: Using alsa sink
    INFO:librespot_core::session: Country: „FR“
    INFO:librespot_playback::player: Loading track „Creep“ with Spotify URI „spotify:track:6b2oQwSGFkzsMtQruIWm2p“
    INFO:librespot_playback::player: Track „Creep“ loaded

    It’s indeed the hifiberry device selected. I disabled bluetooth and stopped by default all the other audio players.

    Regarding spotty, I’m afraid I’m not sure I want a dependency on squeezebox. I’d rather have a set-up as light as possible and I was happy with the spotify connect plugin when it was working.

    • This reply was modified 8 months, 1 week ago by  nipape.
    21. Juni 2019 at 15:59 #45892

    Ok, so I managed to make it work by:

    – ssh connecting to the max2play device,
    – run ‚amixer set Digital unmute‘.

    24. Juni 2019 at 13:13 #45904

    very odd, this should be the default when selecting the Amp2. Glad you got it working though 🙂

    28. Dezember 2019 at 20:38 #47842

    Hello

    I am having diffuculty with the Spotify Connect plugin autostart. It works fine with Max2Play on my older Raspberry Pi B+ and 3B+ but not with my newer Pi4. When I access the Max2Play interface and manually start the Spotify Connect service it works fine but I can’t get the Spotify Connect plugin to automatically start when the Pi4 boots up (which it does on the B+ and 3B+). This is a fresh Max2Play install (Pi4 Beta version) downloaded yesterday from the M2P site. I have Spotify Premium and have tried with HiFiBerry DAC+ installed and removed (HDMI output), and I have disabled all other players (Squeezelite, Shareport, DLNA etc). To be clear, the Spotify Connect plugin works fine when I manually start it on the Max2Play but it won’t start automatically. (this is an updated post as originally it was not working on the P3B+ either but turns out I had entered the Spotify account password wrong)

    Here is the debug log:

    #### Librespot Output ####
    [2019-12-28T18:13:56Z INFO librespot] librespot 4e3576b (2019-06-01). Built on 2019-07-17. Build ID: dJS4Cwwn
    thread ‚main‘ panicked at ‚called Result::unwrap() on an Err value: Os { code: 19, kind: Other, message: „No such device“ }‘, src/libcore/result.rs:1051:5
    stack backtrace:
    0: 0x954520 – backtrace::backtrace::libunwind::trace::hb6a132d591ca7611
    at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/libunwind.rs:88
    1: 0x954520 – backtrace::backtrace::trace_unsynchronized::h57632732de182e95
    at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/mod.rs:66
    2: 0x954520 – std::sys_common::backtrace::_print::h6cb4809c66c99661
    at src/libstd/sys_common/backtrace.rs:47
    3: 0x954520 – std::sys_common::backtrace::print::h6669d3820c576c3e
    at src/libstd/sys_common/backtrace.rs:36
    4: 0x954520 – std::panicking::default_hook::{{closure}}::h0ade7ad8763731e3
    at src/libstd/panicking.rs:200
    5: 0x9540d0 – std::panicking::default_hook::hd3ea7a3eadd333fe
    at src/libstd/panicking.rs:214
    6: 0x954ce4 – std::panicking::rust_panic_with_hook::hce5e0d6d2351d34c
    at src/libstd/panicking.rs:477
    7: 0x9548a8 – std::panicking::continue_panic_fmt::h442f516a43aa110c
    at src/libstd/panicking.rs:384
    8: 0x954794 – rust_begin_unwind
    at src/libstd/panicking.rs:311
    9: 0x970da8 – core::panicking::panic_fmt::hffa19936292f87b2
    at src/libcore/panicking.rs:85
    10: 0x466948 – core::result::unwrap_failed::hfc6d0a87e5a21e1a
    11: 0x442a9c – librespot::main::h3c3dc133e36a93ea
    12: 0x449e28 – std::rt::lang_start::{{closure}}::h2edd886586580efa
    13: 0x95470c – std::rt::lang_start_internal::{{closure}}::hcdb405dd64721e03
    at src/libstd/rt.rs:49
    14: 0x95470c – std::panicking::try::do_call::hfebf9402a8333320
    at src/libstd/panicking.rs:296
    15: 0x95bd7c – __rust_maybe_catch_panic
    at src/libpanic_unwind/lib.rs:82
    16: 0x955174 – std::panicking::try::h4211c5f7da29f2ec
    at src/libstd/panicking.rs:275
    17: 0x955174 – std::panic::catch_unwind::h59ca36657f00e168
    at src/libstd/panic.rs:394
    18: 0x955174 – std::rt::lang_start_internal::ha24163ef22e56cef
    at src/libstd/rt.rs:48
    19: 0x4431ac – main
    20: 0xb6dfd718 – __libc_start_main

    #### Librespot Command Line Options ####
    error: Required option ’name‘ missing
    Usage: /opt/spotifyconnect/librespot [options]

    Options:
    -c, –cache CACHE Path to a directory where files will be cached.
    –disable-audio-cache
    Disable caching of the audio data.
    -n, –name NAME Device name
    –device-type DEVICE_TYPE
    Displayed device type
    -b, –bitrate BITRATE
    Bitrate (96, 160 or 320). Defaults to 160
    –onevent PROGRAM
    Run PROGRAM when playback is about to begin.
    -v, –verbose Enable verbose output
    -u, –username USERNAME
    Username to sign in with
    -p, –password PASSWORD
    Password
    –proxy PROXY HTTP proxy to use when connecting
    –ap-port AP_PORT
    Connect to AP with specified port. If no AP with that
    port are present fallback AP will be used. Available
    ports are usually 80, 443 and 4070
    –disable-discovery
    Disable discovery mode
    –backend BACKEND
    Audio backend to use. Use ‚?‘ to list options
    –device DEVICE Audio device to use. Use ‚?‘ to list options if using
    portaudio or alsa
    –mixer MIXER Mixer to use (alsa or softmixer)
    -m, –mixer-name MIXER_NAME
    Alsa mixer name, e.g „PCM“ or „Master“. Defaults to
    ‚PCM‘
    –mixer-card MIXER_CARD
    Alsa mixer card, e.g „hw:0“ or similar from `aplay
    -l`. Defaults to ‚default‘
    –mixer-index MIXER_INDEX
    Alsa mixer index, Index of the cards mixer. Defaults
    to 0
    –initial-volume VOLUME
    Initial volume in %, once connected (must be from 0 to
    100)
    –zeroconf-port ZEROCONF_PORT
    The port the internal server advertised over zeroconf
    uses.
    –enable-volume-normalisation
    Play all tracks at the same volume
    –normalisation-pregain PREGAIN
    Pregain (dB) applied by volume normalisation
    –linear-volume
    increase volume linear instead of logarithmic.

    • This reply was modified 2 months ago by  erik.
    9. Januar 2020 at 13:10 #47905

    Hi eric,

    Spotify Connect Plugin on Pi4 is still having some issues.

    We recommend using the Spotty Plugin for Squeezebox Server for the full Spotify experience. (Guide)

    20. Januar 2020 at 16:43 #47949

    Hi eric,

    in your error message it seems like the some needed device is not available yet. We built a delay into the startup of the spotifyconnect service to make sure all needed prerequisites are met. As you tested recently you already had this in your setup.
    Could you check the following:
    – are you using WiFi? Try with a cable connection and see if that fixes the problem.
    – do you use ethernet with a fixed IP? try with normal dhcp (default setting) and without fixed IP
    – try setting the audio output of spotifyconnect to „hw:alsa“ and see if that works

    Cheers,
    Stefan

    • This reply was modified 1 month, 1 week ago by  flysurfer.
Viewing 14 posts - 31 through 44 (of 44 total)

You must be logged in to reply to this topic.

Register here