Skip to content
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

Closed
eriqjaffe opened this issue Jun 27, 2021 · 6 comments
Closed

Unable to broadcast #29

eriqjaffe opened this issue Jun 27, 2021 · 6 comments

Comments

@eriqjaffe
Copy link

eriqjaffe commented Jun 27, 2021

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:

source = pipe:///tmp/snapfifo?name=MPD
source = pipe:///tmp/snapfifo1?name=MPD Christmas
source = librespot:///usr/bin/librespot?name=Spotify&username=******e&password=*********&devicename=Snapcast&bitrate=320&nomalize=true&autoplay=false&killall=false
source = airplay://usr/bin/shairport-sync?name=Airplay&devicename=Airsnap
source = tcp://127.0.0.1?port=4953&name=snapbroadcast

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.

@stijnvdb88
Copy link
Owner

Hi! I think I've seen this before, can you try filling in the server's lan ip instead in the conf?

source = tcp://192.168.4.100?port=4953&name=snapbroadcast

@eriqjaffe
Copy link
Author

That did it, thanks!

@eriqjaffe
Copy link
Author

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.

@stijnvdb88
Copy link
Owner

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

@eriqjaffe
Copy link
Author

After playing around with it a bit, this also seems to get the job done without any errors on boot.

source = tcp://0.0.0.0?port=4953&name=snapbroadcast

@stijnvdb88
Copy link
Owner

stijnvdb88 commented Jul 5, 2021

Thanks for the update - that's a much better solution! I've updated the readme to suggest this instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants