Forum Replies Created
-
Hmmmm, I’ve not been aware of the service falling over once running except as per my posting re if another device already has control of the sound card when you start to send from spotify (Spotify Connect service crashes if used when Squeezelite player not paused), but then I have not been using it heavily. Out of interest, and not wishing to interfere with the process of the guys here, does the Spotify Connect page say the service has stopped running when you say it stops working and if so does the DEBUG information on the Spotify Connect page tell you anything AFTER the service has crashed ?
I have not been massively pushing the Auto Start testing but have had no failures since disabling Activate WPS on Boot on the WiFi/LAN page, even on a Pi 2 which has no wifi dongle attached.
I will try that, but unless there has been a very new build of librespot I suspect there will be no change.
I refer you to Issue #165 on librespot github, raised 17 March and apparently still open (https://github.com/plietar/librespot/issues/165). It was also recently announced (https://github.com/plietar/librespot/commit/171be66fd959b956a8aab58e886cdc986ab4b4a4) that plietar can no longer support librespot.
Having said that, I do have a Pi Zero running Volumio 2 with their Volumio Spotify Connect 2 which is also based on librespot and I find that does work OK. Start playing through Spotify connect while currently playing via say AirPlay and it will allow the Spotify control if the Airplay is paused after the Spotify has started. I do wonder if they are simply relaunching the librespot or using it in a different way. Whatever, it is more elegant than the Max2Play implementation crashing and needing restarting.
With regards to librespot, what happens now ? Everybody seems to have switched to it including yourselves, Volumio, I believe the Spotty LMS plugin is built around librespot, as are some hardware products. Will someone pick it up and run with it ? Will we ever get gapless Spotify Connect ? Am I going to have to buy a Yamaha WXAD-10, I hope not.
Thanks for the time you spend on this project and your help
Foz
I did a complete rebuild from recently downloaded image from Max2Play. I think I need to do more testing. I had a scenario all tagged out, which I had detailed here, which has just been shown to be wrong when I rebooted again. Will post when I am more confident of repeatable results.
Thanks
OK done that, exactly same result. Shareport is not in use anyway at the moment but may be needed when box is deployed so I will test with Squeezelite and Shareport on Auto Start after we resolve the Spotify Connect alone. Any other info that would be helpful ?
===============================================================================================================================================
DEBUG information after boot
———————————————————————————————————————————————–
#### Librespot Output ####
INFO:librespot: librespot cc9dba8 (2017-03-26). Built on 2017-07-17. Build ID: 8zQE3Bpb
WARN:librespot::apresolve: Failed to resolve Access Point: HTTP error
WARN:librespot::apresolve: Using fallback „ap.spotify.com:80“
INFO:librespot::session: Connecting to AP „ap.spotify.com:80“
thread ‚main‘ panicked at ‚calledResult::unwrap()on anErrvalue: Error { repr: Custom(Custom { kind: Other, error: StringError(„failed to lookup address information: Name or service not known“) }) }‘, /checkout/src/libcore/result.rs:859
note: Run withRUST_BACKTRACE=1for a backtrace.#### Librespot Command Line Options ####
error: Required option ’name‘ missing.
Usage: /opt/spotifyconnect/librespot [options]
———————————————————————————————————————————————–FYI DEBUG Information when manually started, still not started Squeezelite at this point although there have been no problems manually starting Spotify Connect when Squeezelite running in the past
===============================================================================================================================================
DEBUG Information
———————————————————————————————————————————————–
#### Librespot Output ####
INFO:librespot: librespot cc9dba8 (2017-03-26). Built on 2017-07-17. Build ID: 8zQE3Bpb
INFO:librespot::session: Connecting to AP „lon6-accesspoint-a29.ap.spotify.com:4070“
INFO:librespot::session: Authenticated as „theonlyfoz“ !
INFO:librespot::audio_backend::alsa: Using alsa sink
INFO:librespot::session: Country: „GB“#### Librespot Command Line Options ####
error: Required option ’name‘ missing.
Usage: /opt/spotifyconnect/librespot [options]
———————————————————————————————————————————————–
