title
Products            Buy            Support Forum            Professional            About            Codec Central
 

UPC in Batch Ripper R2024

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

    • Aug 2023
    • 22

    UPC in Batch Ripper R2024

    Hi,

    I recently upgraded from R15.3 to R2024, to get Batch Ripper to read CD-ISRC and CD-UPC.
    Finally, I am able to get ISRC's when ripping in Batch Ripper, but I noticed that Batch Ripper (R2024) consistently reads UPC's as "0".
    When ripping the same CD in CDRipper (R2024), it correctly reads and tags the UPCs, so it seems to me that it's a problem with Batch Ripper.

    For reference, the CD I'm ripping is Oasis - Don't believe the truth (UPC 5099752014927/CDDB 950A130B), as I know it contains the data I'm trying to extract.

    Has anyone had a similar problem?
    And if so, is there any fix?

  • Spoon
    Administrator
    • Apr 2002
    • 44412

    #2
    Will take a look shortly
    Spoon
    www.dbpoweramp.com

    Comment

    • Boffy

      • Aug 2023
      • 22

      #3
      Hi again Spoon.

      Yesterday I tried again, with a different path/naming structure.
      I named the folder after the UPC in the path instead of the naming, in the hopes that it would write it correctly before BR alters it.
      Didn't work though.

      path:
      \\path\to\files\[IFVALUE]upc,UPC_[upc],noUPC[]

      naming:
      [SETLEN]2,48,,[disc][][SETLEN]2,48,,[track][]_[title]_[IFVALUE]isrc,ISRC_[isrc],noISRC[]_[length]

      The CD I'm ripping this time is Oasis - What's the story morning glory? (Coincidence, I swear).

      I opened CDripper through BR, and ripped it without problems:
      \UPC_5099748102027\0101_Hello_ISRC_GBBQY9502012_20 1666.wav
      etc...

      I closed CDRipper and started the rip in BR with the same profile and settings:
      \UPC_0\0101_Hello_noISRC_201666.wav

      For some reason I didn't get the ISRC as well this time, even though I've experienced significant improvement since upgrading to R2024

      Have you had an opportunity to have a look at it?
      It still seems to me that BR is the culprit.

      Best regards

      Comment

      • Spoon
        Administrator
        • Apr 2002
        • 44412

        #4
        Try

        [IFVALUE]upc,UPC_[tag]upc[],noUPC[]

        You have to check UPC is being written in br, check the end files there should be an ID Tag
        Spoon
        www.dbpoweramp.com

        Comment

        • Boffy

          • Aug 2023
          • 22

          #5
          I just tried that, but it didn't work.

          path:
          \\path\to\files\[IFVALUE]upc,UPC_[tag]upc[],noUPC[].

          These are the results from CDRipper and BatchRipper with the same settings.

          CDRipper:
          Click image for larger version  Name:	UPC_cdrip.png Views:	0 Size:	184.0 KB ID:	328075

          BatchRipper:
          Click image for larger version  Name:	UPC_BR.png Views:	0 Size:	166.4 KB ID:	328076

          Also notice that ISRCs and AR results are not written in BR.
          Last edited by Boffy; September 25, 2024, 10:00 AM.

          Comment

          • Spoon
            Administrator
            • Apr 2002
            • 44412

            #6
            Check in Batch Ripper >> edit profile >> CD Ripper options >> ID Tags & Metadata

            that those tags are set to write out. It could be a provider such as GD3 is providing those tags, and you need to subscribe in BR to get GD3.
            Spoon
            www.dbpoweramp.com

            Comment

            • Boffy

              • Aug 2023
              • 22

              #7
              You're right, I should narrow down the list of meta providers. It still doesn't explain why BR assigns a value of 0 to all discs, when the value is correctly set in CDripper.

              I have been a GD3 subscriber, but I'm not sure how many lookups I have left.
              I tried again by disabling every metadata provider, cache, cdplayer.ini and intelligent lookup. Turns out AccurateRip Meta was providing the ISRC.

              The metadata on this test comes from freedb, CD-Text, CD-ISRC, and CD-UPC, and I have double checked that its the same in both BR and CDripper settings.

              CDRipper:
              Click image for larger version

Name:	UPC_CD2.png
Views:	59
Size:	38.7 KB
ID:	328082

              BatchRipper:
              Click image for larger version

Name:	UPC_BR2.png
Views:	50
Size:	41.5 KB
ID:	328083

              Comment

              • Boffy

                • Aug 2023
                • 22

                #8
                Hi again Spoon,

                I have now tried to rip 4 cd's which I know for a fact don't have UPC's.
                In CDRipper the tags are just not written as there is no values.
                In BR the tags are still written and given the value 0.

                The metadata providers I used for this test is the same as my last post:
                - freedb
                - CD-Text
                - CD-ISRC
                - CD-UPC

                Comment

                • Boffy

                  • Aug 2023
                  • 22

                  #9
                  Hi again Spoon,

                  I made some tests the other day to see how BR handles UPC values, by enabling/disabling the following metadata providers:

                  CDRipper:
                  - PerfectMeta (Intelligent Lookup)
                  - AccurateRip Meta
                  - Discogs
                  - GD3
                  - MusicBrainz
                  - freedb (archived)
                  - CD-Text
                  - CD-ISRC
                  - CD-UPC

                  Batch Ripper:
                  - Discogs
                  - GD3
                  - MusicBrainz
                  - freedb
                  - CD-Text
                  - CD-ISRC
                  - CD-UPC
                  - Intelligent Meta From all Enabled Providers


                  Click image for larger version

Name:	UPC_test_dbpa.jpg
Views:	15
Size:	32.3 KB
ID:	328295
                  In test_1 I only have UPC enabled in both CDRipper and BR and so forth.
                  In test_9 I tried ripping only in CD Ripper.
                  In test_4, 5, 10 and 11 BR immediately rejected the cd because "User cancelled".

                  I also noticed that BR doesn't write out "[SETLEN]2,48,,[disc][][SETLEN]2,48,,[track][]" correctly.
                  BR wrote 0001, 0002, and so forth, while CD Ripper in test_9 wrote 0101, 0102, etc.

                  I'm mainly concerned with the UPC's but I figured I would share my findings about rejections and the disc/track naming as well.

                  I hope this information can be of use to you.

                  Comment

                  • Boffy

                    • Aug 2023
                    • 22

                    #10
                    Originally posted by Boffy
                    I'm mainly concerned with the UPC's but I figured I would share my findings...
                    It seems to me that whenever CD-UPC is enabled in BR it automatically assigns the value 0, even if upc is not available/present. That's what happened in my previous post.

                    Comment

                    Working...

                    ]]>