title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Buggy freedb lookup?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Porcus
    dBpoweramp Guru

    • Feb 2007
    • 792

    Buggy freedb lookup?

    It happens fairly often that dBpoweramp finds no CD in freedb, but when I submit I get a reject due to discid collision. Might need to look up the lookup algorithm?


    For the record
    - 'no CD' means that there is nothing under the freedb column in PerfectMeta.
    - freedb settings: from internet
    - dBpoweramp's ID matches the one which the freedb daemon reports back to me, so there is presumably nothing wrong with the actual calculation
    - just downloaded the latest 14.3 beta and replicated the finding.


    An example follows, in case it is of any interest:


    CDTOC and AccurateRip-ID from tags:
    A+96+31FC+10642+16498+1D770+24ADE+2DE9A+34C77+3C68 A+4401F+4B423
    010-00199f25-00ce8cec-88100c0a-*



    From freedb mail:

    The rejected submission follows:
    > * xmcd
    > *
    > * Track frame offsets:
    > * 150
    > * 12796
    > * 67138
    > * 91288
    > * 120688
    > * 150238
    > * 188058
    > * 216183
    > * 247434
    > * 278559
    > *
    > * Disc length: 4110 seconds
    > * Revision: 1
    > * Processed by: cddbd v1.5.2PL0 Copyright (c) Steve Scherf et al.
    > * Submitted via: dBpowerAMP V12.0
    > *
    > DISCID=88100c0a




    "V12.0"
  • Spoon
    Administrator
    • Apr 2002
    • 44582

    #2
    Re: Buggy freedb lookup?

    It might just be a server which is not responding, you are using freedb.org? rather than a mirror such as uk.freedb.org
    Spoon
    www.dbpoweramp.com

    Comment

    • eaglescout1998
      dBpoweramp Enthusiast

      • Apr 2009
      • 197

      #3
      Re: Buggy freedb lookup?

      Does this help?

      2.7. My freedb-submission was rejected with error-reason "Discid collision in category xy". What's 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 determine, if an entry is a match or not. In order to submit your CD to freedb successfully, you will have to select a different category - even if it does not really fit for the music style of your CD. Since a specific genre can be specified for a database entry in addition to the category, a wrong category choice is not really that problematic.

      Comment

      • Porcus
        dBpoweramp Guru

        • Feb 2007
        • 792

        #4
        Re: Buggy freedb lookup?

        Originally posted by Spoon
        It might just be a server which is not responding, you are using freedb.org? rather than a mirror such as uk.freedb.org
        Hm. Good point. I've reloaded helluvalot of times, but maybe the main server is chronically overloaded.



        eaglescout: nope, that's not helpful. My point was that if there is a collision, then a lookup should have found something.

        Comment

        • eaglescout1998
          dBpoweramp Enthusiast

          • Apr 2009
          • 197

          #5
          Re: Buggy freedb lookup?

          My point was that if there is a collision, then a lookup should have found something.
          If I understand correctly, this may not be true. This portion, in particular, stood out: " 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 determine, if an entry is a match or not."

          I am far from knowledgeable in the technical specifics of the freedb. I can only speak from my own personal experience. There have been many times when I've had to manually enter artist, album, and title info because there was NOTHING in PerfectMeta. When I try submitting to the freedb, I would frequently get a discid collision error. Re-submitting using a different category worked (sometimes).

          One thing you might try is fetching freedb information using foobar. There have been times when PerfectMeta would not provide MusicBrainz data foobar2000 would.
          Last edited by eaglescout1998; July 07, 2012, 09:07 PM.

          Comment

          • Porcus
            dBpoweramp Guru

            • Feb 2007
            • 792

            #6
            Re: Buggy freedb lookup?

            Originally posted by eaglescout1998
            [...]
            Argh, I turned the argument upside down. My bad. Thanks.

            Comment

            Working...

            ]]>