Le 16/04/2016 16:31, Max Kellermann a écrit : > On 2016/04/16 00:58, Calimero <calimerotek...@free.fr> wrote: >> I believe I have discovered an regression where mpd's response times on the >> control socket got slow while playing. >> `mpc next`, `mpc previous` or `telnet localhost 6600` and typing next or >> previous can take a whole second and a half before mpd responds with OK. > Intended change. Previously, "next" and "previous" were asynchronous > - MPD would reply "OK" immediately, even if playback actually failed. > Now those commands wait for completion, and give a useful response. > > If you still believe that's a regression, explain why. I'm sorry, I didn't mention the most important part: the current song continues playing for 1.5 second!
Audibly, it's just the same as if I had replaced my `mpc next` shortcut command with `sleep 1.5; mpc next`. Hearing that bothered me immediately after updating, and led me to bisect. Since that didn't happen before 45f6129, I labeled this a regression. Of course, I don't mind mpd taking a second and a half to respond with 'OK' on the socket. (none of my use cases need a prompt reply, but for others it might differ) However, when I ask mpd to switch to the next song, I expect that to hear that happening fast, not almost two seconds later. Cheers _______________________________________________ mpd-devel mailing list mpd-devel@musicpd.org http://mailman.blarg.de/listinfo/mpd-devel
