aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarc Pavot <m.pavot@gmail.com>2008-11-25 16:19:53 +0100
committerMax Kellermann <max@duempel.org>2008-11-25 16:19:53 +0100
commitfd1144145caaefee0a5c5fdfe18508e0dc2c77cc (patch)
tree03920277fc6d978ae5252314e1dd8961a452b9b5
parentc570aa20faf7d0b747e8509390dc8580f91581d4 (diff)
downloadmpd-fd1144145caaefee0a5c5fdfe18508e0dc2c77cc.tar.gz
mpd-fd1144145caaefee0a5c5fdfe18508e0dc2c77cc.tar.xz
mpd-fd1144145caaefee0a5c5fdfe18508e0dc2c77cc.zip
player: set elapsed=0 at song change
I have found something that looks like a bug in MPD: - When a song is finished, the next one is played and the 'player' event is emitted. - When the client sends the status command just after this event, the songid is the new one but the 'elapsed' time is not reseted to 0. This is problem because I have implemented the solution using a timer on client side to compute the elapsed time but with this bug the elapsed time continues to be incremented on a new song.
Diffstat (limited to '')
-rw-r--r--src/player_thread.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/player_thread.c b/src/player_thread.c
index 1595c0af8..7da412dfa 100644
--- a/src/player_thread.c
+++ b/src/player_thread.c
@@ -109,6 +109,7 @@ static int player_wait_for_decoder(struct player *player)
player->song = pc.next_song;
pc.next_song = NULL;
+ pc.elapsed_time = 0;
player->queued = false;
player->decoder_starting = true;