Bug 155 - parsing cue sheets treats time offsets incorrectly
: parsing cue sheets treats time offsets incorrectly
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Misc
: unspecified
: All All
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-01-20 04:53 UTC by michael
Modified: 2008-12-15 11:57 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description michael 2004-01-20 04:53:12 UTC
I noticed in server/Slim/Formats/Parse.pm the following lines...
 } elsif (defined $currtrack and
                         /^\s+INDEX\s+01\s+(\d+):(\d+):(\d+)/i) {
                     $tracks{$currtrack}->{'START'} = ($1 * 60) + $2 + ($3 / 100);


meanwhile, according to goldenhawk (which, as the source of the cue sheet
format, is probably the closest thing to a spec that we're going to see anytime
soon) the time offset is clearly indicated to be in the format of
minutes:seconds:frames and there are 75 frames to second, not 100. peek at their
documentation and you'll see what I mean.
Comment 1 Blackketter Dean 2004-01-20 13:09:57 UTC
The latest nightly build has the 100 changed to a 75.  Can you download and verify?
Comment 2 michael 2004-01-20 14:16:03 UTC
I see the change after cvs up, so I'll trust that means it'll be in the builds
as well.

Thanks!
Comment 3 James Richardson 2008-12-15 11:57:00 UTC
This bug has been fixed in the latest release of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.