- This topic has 43 replies, 10 voices, and was last updated 4 years, 3 months ago by
.
-
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.
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“ loadedIt’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.
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 ‚calledResult::unwrap()on anErrvalue: 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.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 worksCheers,
Stefan
You must be logged in to reply to this topic.