-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snapcast server starts, no Spotify connect device appears though #8
Comments
Hi @febs, I had the same problem with amd64 tag. I've used latest-amd64 and it works well. Did you try this ? |
Thank you very much for your suggestion @f-necas . I ended up dropping this solution altogether and building the components by hand the old school way. |
Same issue here |
I just updated the image to snapcast 0.25.0 and librespot 0.2.0. Everything built successfully and it seems to work on all architectures. Please try the latest version. (Or the |
Unfortunately, right now it's not working once again. Logs is exactly the same as above. |
Just tried once again after an hour, and now it's appearing... Strange |
Well, no changes to the image in the meantime, so it should work all the time.. |
Yes, I have no problems for already a week. Thank you for your work! |
Anyone still having problems? Otherwise I will close this. |
I haven't had any issues since then, but I would be very happy if you could consider isolating the snapserver.conf from the container. I saw someone already mention such a request - it would be great if we could use snapserver's built-in modularity with this container (for example, I would really like to connect shairport) |
I am facing the same issue. It was working just fine before, but today Snapcast does not show up in Spotify connect anymore on my smartphone. Strangely, it does show up on my desktop computer and I can start it there, then control it with my smartphone.
|
Using ubuntu server on a raspberry Pi 3B+.
Using mazzolino/librespot-snapserver:arm as per the other issue. As expected and thescribed in #7 , the default image won't run.
No spotify connect device is added to the list, though. Other spotify connect devices (using raspotify) are showing up correctly, for what it matters.
If ran without detaching the terminal, here's what I get. I see no line related to librespot.
ubuntu@ubuntu:~$ sudo docker run --name snapserver --net host --rm -e DEVICE_NAME=Snapcast mazzolino/librespot-snapserver:arm
2021-01-06 11-08-29.830 [Info] (main) Adding source: pipe:///tmp/snapfifo?name=default
2021-01-06 11-08-29.831 [Notice] (init) Settings file: "/root/.config/snapserver/server.json"
2021-01-06 11-08-29.833 [Error] (Avahi) Failed to create client: Daemon not running
2021-01-06 11-08-29.834 [Info] (PcmStream) PcmStream: default, sampleFormat: 48000:16:2
2021-01-06 11-08-29.834 [Info] (PcmStream) Stream: default, metadata={
2021-01-06 11-08-29.834 [Info] (PcmStream) "STREAM": "default"
2021-01-06 11-08-29.834 [Info] (PcmStream) }
2021-01-06 11-08-29.834 [Info] (Server) onMetaChanged (default)
2021-01-06 11-08-29.835 [Info] (PipeStream) PipeStream mode: create
2021-01-06 11-08-29.835 [Info] (Server) Stream: {"fragment":"","host":"","path":"/tmp/snapfifo","query":{"chunk_ms":"20","codec":"flac","name":"default","sampleformat":"48000:16:2"},"raw":"pipe:////tmp/snapfifo?chunk_ms=20&codec=flac&name=default&sampleformat=48000:16:2","scheme":"pipe"}
2021-01-06 11-08-29.837 [Error] (PosixStream) Exception: end of file
2021-01-06 11-08-29.838 [Info] (ControlServer) Creating TCP acceptor for address: 0.0.0.0, port: 1705
2021-01-06 11-08-29.838 [Info] (ControlServer) Creating HTTP acceptor for address: 0.0.0.0, port: 1780
2021-01-06 11-08-29.838 [Info] (StreamServer) Creating stream acceptor for address: 0.0.0.0, port: 1704
2021-01-06 11-08-29.839 [Info] (main) number of threads: 4, hw threads: 4
2021-01-06 11-08-30.242 [Notice] (StreamServer) StreamServer::NewConnection: 192.168.8.129
2021-01-06 11-08-30.247 [Info] (Server) Hello from 15133707-0ad4-46b4-862c-1d9a7ce7cfa1, host: SM-A405FN, v0.22.0, ClientName: Snapclient, OS: Android 10, Arch: arm64-v8a, Protocol version: 2
How can I help debug this?
Thanks,
The text was updated successfully, but these errors were encountered: