| commit | fd1144145caaefee0a5c5fdfe18508e0dc2c77cc | |
| author | Marc Pavot <m.pavot@gmail.com> | |
| Tue, 25 Nov 2008 15:19:53 +0000 (25 16:19 +0100) | ||
| committer | Max Kellermann <max@duempel.org> | |
| Tue, 25 Nov 2008 15:19:53 +0000 (25 16:19 +0100) | ||
| tree | 03920277fc6d978ae5252314e1dd8961a452b9b5 | treesnapshot (tar.gz zip) |
| parent | c570aa20faf7d0b747e8509390dc8580f91581d4 | commitdiff |
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.
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.
| src/player_thread.c | diffblobblamehistory |