-
Notifications
You must be signed in to change notification settings - Fork 462
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
Default stream is not correct #1293
Comments
I seem have hit the exact same issue on From @erahhal and my own logs we can see that How an the @badaix Could this be a snapcast defect or is it due to misconfiguration on our side ? |
Cause Workaround ? Feature Request Options ?
|
Describe the bug
Despite being first in the server configuration, the stream defined first is not being selected by clients as default.
Steps to Reproduce
snapserver --daemon --stream.stream=meta:///b_bluetooth/d_mediaserver/e_speakerserver/c_spotify?name=a_main --stream.stream=pipe:///run/snapserver/bluetooth?name=b_bluetooth --stream.stream=pipe:///run/snapserver/spotify?name=c_spotify --stream.stream=pipe:///run/snapserver/mediaserver?name=d_mediaserver&dryout_ms=2000&idle_threshold=5000&mode=create&send_silence=false&silence_threshold_percent=1.0 --stream.stream=pipe:///run/snapserver/speakerserver?name=e_speakerserver&dryout_ms=2000&idle_threshold=5000&mode=create&send_silence=false&silence_threshold_percent=1.0 --stream.bind_to_address=:: --stream.port=1704 --stream.sampleformat=44100:16:2 --stream.codec=flac --tcp.enabled=1 --tcp.bind_to_address=:: --tcp.port=1705
b_bluetooth
is selected as default rather thana_main
Environment details
Attach logfile if applicable
Nothing notable in snapclient or snapserver logs. Snapserver log below (FIFO paths were changed since it was run interactively):
The text was updated successfully, but these errors were encountered: