If it used the old CDDB-style method of checking then it really is very simplistic
However, I think the musicbrainz way is slightly different and less prone to clashes > > The CD Index algorithm simply takes the following pieces of data and > runs them through the SHA-1 hash function: > > First track number (normally one): 1 byte > Last track number: 1 byte > Lead-out track offset: 4 bytes > 99 frame offsets: 4 bytes for each track > If there are less than 99 tracks (almost certainly), the value 0 will be > used instead. > That result is then (sort of) converted to ASCII and BASE64 encoded. Example of clashes (11 at the time of posting) https://musicbrainz.org/cdtoc/lwHl8fGzJyLXQR33ug60E8jhf4k- The original CDDB algorithm is this (wikipedia) > CDDB1 identifies CDs with a 32-bit number, usually displayed as a > hexadecimal number containing 8 digits: XXYYYYZZ. The first two digits > (labeled XX) represent a checksum based on the starting times of each > track on the CD, mod 255. The next four digits (YYYY) represent the > total time of the CD in seconds from the start of the first track to the > end of the last track. The last two digits (ZZ) represent the number of > tracks on the CD. Simpler and more chances of clashes if the CDs have the same total play times and number of tracks. Paul Webster http://dabdig.blogspot.com Author Radio France (FIP etc) plugin ------------------------------------------------------------------------ Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105 View this thread: http://forums.slimdevices.com/showthread.php?t=109604 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
