Bug 3977 - CLI command "time ?" does not return the right time at the beginning of the tracks
: CLI command "time ?" does not return the right time at the beginning of the t...
Status: RESOLVED DUPLICATE of bug 4098
Product: Logitech Media Server
Classification: Unclassified
Component: CLI
: 6.5b1
: PC All
: P2 normal (vote)
: ---
Assigned To: Fred
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-08-21 08:08 UTC by pulp_136
Modified: 2008-09-15 14:39 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pulp_136 2006-08-21 08:08:44 UTC
The CLI command "time ?" does not return the right time at the beginning of the tracks. The problems occure only when slimserver changes track by it's self. When I change the track through a command, the "time ?" order returns the time correctly from the beginning to the end.
Comment 1 Chris Owens 2006-08-21 10:19:15 UTC
It seems like you're a popular person lately, Fred. :)

Could you have a look at this one as well?
Comment 2 Fred 2006-08-26 14:42:51 UTC
Can't reproduce. I get the previous time for about 1s after playlist index changes, then 0 and normal values. If you play with time +/-, there are some issues. Tried with AIF and MP3 files...
Comment 3 pulp_136 2006-08-27 08:37:05 UTC
After further investigation it seems the problem appears if I also use the "time x" command while playing the track.
tried with mp3 and flac files.
Comment 4 pulp_136 2006-08-27 08:47:12 UTC
Ok, I'm pretty sure that it has to do with the "time x" command. It seems that CLI looses path of time after I use that order and it returns the wrong time until the end of the song (CLI ahead of the song). But I can only notice it when the song ends. So my bug description is not very exact.
Comment 5 Fred 2006-08-31 18:09:26 UTC
Fixed in SVN 9332.
Comment 6 pulp_136 2006-09-07 11:16:22 UTC
Well, still not OK Fred. At the beginning it seems fine. Try using the "time x" command especially at the end of the track, and it goes nuts. Then, whenever I use the next track command, it doesn't start from zero.
Comment 7 Fred 2006-09-14 14:05:40 UTC

*** This bug has been marked as a duplicate of 4098 ***