-
Notifications
You must be signed in to change notification settings - Fork 11
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
Unable to broadcast #29
Comments
Hi! I think I've seen this before, can you try filling in the server's lan ip instead in the conf?
|
That did it, thanks! |
As a note, this seems to have a side-effect of causing the snapserver service to fail on boot. Manually starting the service after bootup works as expected. Certainly not a show stopper, just something I have to remember. |
This definitely shouldn't cause snapserver to fail like that - is it possible the service is trying to start before your LAN connection is up? It might be worth opening an issue at https://github.com/badaix/snapcast if the problem persists |
After playing around with it a bit, this also seems to get the job done without any errors on boot.
|
Thanks for the update - that's a much better solution! I've updated the readme to suggest this instead |
I'm unable to get broadcasting working in Windows. Clicking the button to start a broadcast does nothing (not even a momentary state change) and running "Snap.Net.Broadcast.exe -s 1 -h 192.168.4.100 -p 4953" returns "Failed to connect. Exception: No connection could be made because the target machine actively refused it 192.168.4.100:4953" I am using a Virtual Audio Cable as shown in the readme so I can broadcast specific apps, but I get the same behavior regardless of which output I try to use.
The snapcast server appears to be listening on port 4953:
tcp 0 0 127.0.0.1:4953 0.0.0.0:* LISTEN 1361/snapserver
My snapserver.conf is as follows, and the tcp line is basically just cutting and pasting the example text:
Both of the MPD instances, Spotify and Airplay all work as expected. I can't figure out if I'm doing something wrong or not.
The text was updated successfully, but these errors were encountered: