mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #793] Cannot use librespot if there are multiple librespot devices on the same network with discovery enabled. #413
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#413
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Jun 9, 2021).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/793
My current setup is:
Both devices are on the same network and both devices have discovery enabled and no credentials provided.
When I have both devices online and one is playing music, I am unable to switch playing to the other. I can see it in the spotify app as an available device, but as soon as I choose it, it starts playing for a second, then automatically switches back to the previous device.
I have to shutdown the first device to have the other device start playing successfully.
I can provide more info if anyone tells me what you need.
Thanks!
@roderickvd commented on GitHub (Jun 9, 2021):
Cannot reproduce. Tested here:
1x instance named X running on RPi
1x instance named Y running on macOS
Running
0.2.0-dev. Connected to the same switch. Zeroconf enabled, no credentials.Starting playback on X. Switching to Y -- seamless transition without jumping back. Switching to X - as expected. Y - again.
@JasonLG1979 commented on GitHub (Jun 10, 2021):
I can't reproduce either. I run 2 or 3 simulations instances, sometimes on the same machine all the time while testing things and never have any trouble.
Purely anecdotal but some routers don't play well with mDNS. I had nothing but trouble with my wifi router to the point that I ended up just getting a cheap standalone router/switch and just using it as a wireless AP. If you have an old router laying around that's a different brand or can barrow one you might try switching it out to see if it clears things up. At the very least I would check with Google to see if anyone else has had mDNS issues with your router.
@roderickvd commented on GitHub (Jun 14, 2021):
Cannot reproduce and no further replies.