from http://bugs.musicbrainz.org/ticket/5062

Related Forum Post

...I am ripping my CD collection to FLAC and along the way I am generating the PUIDs and DISCIDS. In order to tie the metadata of the rips to that of the CDs I do a lookup using the FreeDB id (I maintain a localhost copy of the XMCD files). All is fine until I encounter a mixed mode CD as the returned FreeDB id is incorrect. I know the data tracks aren't used for the MD discids, but this shouldn't be the case for the FreeDB ones. Is this a bug/feature of libdiscid itself or is it due to the Ruby mb-discid binding that I am using?

The Release for the example, which has a video as the third track. The data tracks seem not to be used in the calculation of the FreeDB id;

Full TOC: 3 150 16421 44259 1518

FreeDB id: 1b05ec03

libdiscid TOC: 1+2+32859+150+16421

libdiscid FreeDB id: 0d01b402