-
Notifications
You must be signed in to change notification settings - Fork 463
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
Mopidy track control #23
Comments
Hi, is this related to issue #11? |
The Mopidy track control issues are actually a follow-on issue related to the fix they implemented for the gapless playback mentioned in #11. So in that way they are related. Probably relevant to users of snapcast+Mopidy, but not a snapcast issue. The audio artifacting could be a snapcast issue though (but of course only triggered by an issue in an upstream program - so maybe not a priority). |
This Mopidy problem has been resolved in the |
It should also be fixed with this commit 73a9223 in Snapcast's |
Hi, first off, this is a fantastic initiative. Very happy to have found it.
I'm using it in conjunction with Mopidy, but I'm experiencing a problem with track control. If I hit pause/play/next/prev in Mopidy, my clients report:
No errors in the server.
Accompanying this on one of my clients is some audio artifacting - it sounds like it is playing back the last chunk in an infinite loop (I suspect this is actually a separate issue?)
If I let Mopidy transition to the next track without manual intervention, it works fine. I'm guessing this is more of a Mopidy problem than a snapcast problem, but I wanted to document the issue here just in case/as a note for other Mopidy users.
edit: I followed up on this with Mopidy - the track control is certainly a Mopidy issue, but this issue is still relevant due to the audio artifacting.
The text was updated successfully, but these errors were encountered: