My freedb-submission was rejected with error-reason “Discid collision in category xy”. Whats the problem?
The disc ID, which is an important factor in identifying a CD, is not as good as it could be – in fact, it is pretty bad as a unique identifier for a CD. Therefore completely different CDs (with the same length in seconds and the same track number) can have the same disc ID. A disc ID, however, can only exist once in each of the 11 categories. This disc ID algorithm and the cddb protocol can unfortunately not be changed without loosing backwards compatibility to existing applications – and we definitely want to keep backwards-compatibility. If you receive a rejection e-mail telling you, that there was a disc ID collision in the category you tried to submit the entry to, that means, that in that category the disc ID of your CD is already used for a different CD. When querying the server for disc information with your CD, you don’t see the existing entry (which is for a different CD), because the server software checks not only the discid, but also the track offsets when trying to determ
Related Questions
- My freedb-submission was rejected with error-reason "Existing entry found with higher revision than submitted". Whats the problem?
- My freedb-submission was rejected with error-reason "Discid collision in category xy". Whats the problem?
- My freedb-submission was rejected with error-reason "Unsupported charset in header". Whats the problem?
