On Sun Aug 03 19:06:39 2008, chuck@ece.cmu.edu wrote:
Show quoted text> Hi-
>
> There is a bug in CDDB.pm that is mostly being masked by the CDDB's
> fuzzy matching (at least on my system). The current code is mishandling
> the 2 second (150 frame) interval at the start of a disc. The fix
> is simple (remove the "+ 150" from line 519)
I'm not sure this recommendation is correct. For example, this Java
example says that the first track (beginning at 0m0s) starts at frame 150:
http://www.cs.princeton.edu/introcs/51data/CDDB.java.html
Wikipedia says the first track starts at 2 seconds, which is 150 frames
/ 75 frames per second. So again, the first track's 0m0s start time is
at 150 frames.
I think CDDB.pm's calculation may be in error for considering the frames
in the TOC's MSF data. The algorithms I've seen truncate the frames.
By adding them, CDDB.pm's track times could accumulate significant error.