raspotify: Pipe backend not working
Compatible OS
- I’m running Raspotify on a compatible OS
Latest Version
- I’m running the latest version of Raspotify
Due Diligence
- I have done my due diligence
What happened?
I’m not having any luck using the pipe backend. I found and read #458 and #468, read the wiki entry and changed LIBRESPOT_DEVICE to /var/run/snapfifo, but it seems Raspotify can’t write to the locations specified. Using LIBRESPOT_DEVICE="/var/run/snapfifo" gives me an os error 30 and I either receive an os error 2 or an os error 30 if I point at/create a new folder inside /var/run/.
Jan 16 15:45:02 PiOffice librespot[796]: [2022-01-16T21:45:02Z ERROR librespot_playback::player] Audio Sink Error Connection Refused: Read-only file system (os error 30)
Jan 16 16:08:38 PiOffice librespot[858]: [2022-01-16T22:08:38Z ERROR librespot_playback::player] Audio Sink Error Connection Refused: No such file or directory (os error 2)
Previously I was using BACKEND_ARGS="--backend pipe --device /tmp/snapfifo" and this worked very nicely.
After the change I’m using LIBRESPOT_BACKEND="pipe" and LIBRESPOT_DEVICE="/var/run/snapfifo" as described above.
This is a brand new Bullseye install and a brand new Raspotify install on a Pi4. I’m hoping I’m just missing something simple as I was looking forward to playing around with some of the new options.
Relevant log output
Jan 16 16:39:56 PiOffice systemd[1]: Started Raspotify (Spotify Connect Client). Jan 16 16:40:03 PiOffice librespot[1022]: [2022-01-16T22:40:03Z ERROR librespot_playback::player] Audio Sink Error Connection Refused: Read-only file system (os error 30) Jan 16 16:40:03 PiOffice systemd[1]: raspotify.service: Main process exited, code=exited, status=1/FAILURE Jan 16 16:40:03 PiOffice systemd[1]: raspotify.service: Failed with result 'exit-code'.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19
Sounds good.
Yep.
I’d love to see this in the wiki. Feel free to add a page about snapcast integration.
Don’t forget to disable the raspotify service unless ofc you want 2 instances of librespot running?
@JasonLG1979 I think the best way to handle this moving forward is to just not use pipe–I was able to get my system back up and running by using librespot directly, just like you suggested. Maybe we could add this to the wiki?
Here’s the snapserver conf line for my setup, including all the parameters I usually set with Raspotify:
source = spotify:///usr/bin/librespot?name=Spotify&username=***&password=***&devicename=***&bitrate=320&wd_timeout=7800&volume=100&normalize=false&autoplay=false&disable_audio_cache=true¶ms=--device-type%20avr¶ms=--volume-ctrl%20fixed¶ms=--format%20S32¶ms=--disable-discovery%20trueThe nice thing about this is you can use the
paramsargument to add any options from librespot very easily.Edit: no writing of anything (beyond the source line) is necessary, Raspotify has already installed librespot, you just have to point snapcast at librespot instead of the pipe/Raspotify.