illustrate
Products            Buy            Support Forum            Registrations            Professional            About           
 

Problem in CDRipper when retrieving UTF-8 encoded MetaData

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Saulius

    • Aug 2025
    • 2

    #1

    Problem in CDRipper when retrieving UTF-8 encoded MetaData

    I am experiencing some problems with the metadata retrieval in a language different from English when ripping some CDs produced in Lithuania. I can see that the metadata for the CD I am trying to rip into FLAC files is available and displayed properly (UTF-8 encoded) on the DISCOGS web site, but dBpoweramp (I am using V17.2) fails to find it and opens the manual metadata search window. If I copy the release URL from Discogs web site to clipboard and then click "Lookup Disc" button, the Manual Metadata Search goes forever and never finds anything. Alternatively, if I type the artist and album names into the relevant fields, it finds the data but in the wrong encoding - instead of UTF-8 it is supposed to use by default, it actually uses 8-bit ANSII-1257 encoding, even though the Discogs data is clearly in UTF-8. Unfortunately I was unable to find out from which database it finds this data. When trying to review the the perfect metadata matches, it finds none. Even if I select the manually found metadata in the wrong encoding, Review PerfectMeta Matches fails to show which database this metadata came from.

    In the past I used to be able copy the the release URL from Discogs to the clipboard and then Retrieve MetaData from dBpoweramp cache, which worked quite well, but recently I haven't been able to do it. For some CDs I am still able to get the MetaData correctly encoded without the need to go through the Manual MetaData Search window but it is rare.

    I would appreciate it if somebody could help me with this issue.
  • Spoon
    Administrator
    • Apr 2002
    • 45241

    #2
    This issue with utf8 was fixed around 3 years back, you need the R2025 version.
    Spoon
    www.dbpoweramp.com

    Comment

    • Saulius

      • Aug 2025
      • 2

      #3
      Thank you for your quick response, but I find it puzzling. I have reported 3 issues:

      1. In the initial search dBpoweramp fails to find the CD's metadata which is available in Discogs, even though Discogs is one of the 4 databases it is supposed to be scanning.
      2. The manual search from the actual Discogs URL in the clipboard never finds the metadata, which is present there.
      3. The manual search based on the entered artist and album using UTF-8 encoding for some reason returns data in ANSII-1257 but this data does not appear to match any entries in any of the 4 metadata databases. So, I assume it does not come from Discogs.

      So, which of these 3 problems has been solved 3 years ago?

      Comment

      • garym
        dBpoweramp Guru

        • Nov 2007
        • 6083

        #4
        Originally posted by Spoon
        This issue with utf8 was fixed around 3 years back, you need the R2025 version.
        ​​​​​​problem #3.

        Comment

        • Spoon
          Administrator
          • Apr 2002
          • 45241

          #5
          Possibly all (there are no known metadata outstanding issues currently):

          R2025 includes many updates to the ever changing metadata landscape, in the recent years: All Media Guide (AMG) service has been discontinued freedb.org has also been discontinued musicbrainz updated their servers, resulting in R16 or older not being able to read the metadata AccurateRip Meta has been introduced R2025
          Spoon
          www.dbpoweramp.com

          Comment

          Working...