-
Notifications
You must be signed in to change notification settings - Fork 235
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
MPD protocol: "noidle" command returns "OK" even when not in idle #1611
Comments
The maintainer of the mpd part of owntone isn't active any more. I can make a fix if it is a simple one, but I'm not myself well acquiented with the protocol, and I didn't completely understand your description. Could you spell out for me what it is owntone should or shouldn't do? |
When The fix for this is simple, but I found other problems with the MPD protocol implementation in owntone mainly in For example it breaks from the loop on If you like I can try fixing it and making a pull request. |
That would be awesome, sounds like you know this stuff |
isn't this just an |
Fixed in PR #1794 |
owntone 28.4
Debian 4.19.282-1
MPD ignores "noidle" commands unless the client connection is already in "idle" state.
Owntone responds with "OK" to "noidle" even when the connection is not in "idle" state.
To reproduce:
This may cause MPD clients to not be able to keep track of the response to request sequence.
A client needs to send "noidle" when the last command it sent was "idle" to interrupt it and send another command.
But it is possible that the client connection in MPD has already sent a response to the last "idle" that the client has not yet received. So MPD must ignore the noidle command unless the client connection is still in idle state.
The text was updated successfully, but these errors were encountered: