Bug in Batch Ripper

[Boffy]

Hi,

I think I discovered a bug in the newest version of Batch Ripper.

The naming scheme is the same as I have always used:
[SETLEN]2,48,,[disc][][SETLEN]2,48,,[track][]_[title]_etc.

Batch Ripper (more often than not) names the files 0001, 0002, 0003, etc. instead of 0101, 0102, 0103, etc.

I haven’t figured out what exactly the pattern is, but I have to manually rename every file. Also problematic with multi-disc albums.

Has anyone else encountered this, and is it maybe something Spoon et al. might look into for a future update?

Best regards,

[Boffy]

Using a nimbie btw

[Spoon]

>Batch Ripper (more often than not) names the files 0001, 0002, 0003

That would suggest there is not a disc number

[Boffy]

I don't know how cdripper/batchripper determines a disc number, but when ripping the same cd's in cdripper (not through BR) with the same nimbie drive, the files are named correctly.
The CD's I tried for this test:

Faithless
Paul Simon
Neil Young
Daft Punk
Wings
Groove Armada

So CD Ripper still names the files correctly 0101, 0102, etc.
It's a problem I first encountered after updating to the first 2024 update to BR.

I'll attach a screenshot. I ripped on a win11 machine, although the screenshot is from OSX.

Can I get you to look into it?

Have a nice weekend

[Spoon]

You would have to add GD3 lookups to batch ripper to have the same metadata as CD Ripper

[Boffy]

Ah, interesting!
I might very well have run out of lookups, so I'll check up on that.
Btw, is there a way to track how many lookups are left?

However, I should have added that the metadata providers enabled in both programs are CD-Text, CD-UPC, and CD-ISRC.
If GD3 is not enabled in either, shouldn't they just name the files the same in both programs?

Again, it's not a problem I have encountered previously in Ref15.
Finally switched to R2024 around end of August/start September. I think I noticed around October, but I can't say if it was there before the September update, though.

[Spoon]

Not if the naming relies on a tag which is missing. You should be able to lookup on the GD3 website.

[Boffy]

But if CD ripper can succesfully name the files 0101 with only local metadata (no cache), it would mean that the tags are not missing.
That's why I suspect BR handling it differently somehow.
Same as when I had the UPC problem. Thank you very much, btw. Made my day!

I have also experienced it with all providers enabled (except musicbrainz) in both cdr and br.

If I'm not right on this, I would really like to understand what happens then. I'm quite intrigued by your program and how it works.

[Spoon]

Local metadata? Disc number only exists online.

[Boffy]

You're making me doubt myself spoon.
Now, I'm no expert but I'm trying to learn.
I would assume that all the data is stored in CD-text or CD-toc, if present.
I see it when looking at the drive through my terminal.

I just tried again to be sure, and it's simply not true.
I just ripped Graceland in CD Ripper with only CD-text, CD-UPC, and CD-ISRC enabled.
I even unplugged all internet connections...

The files are named correctly: 0101, 0102, etc.

And your answer still does not address why CD Ripper and Batch Ripper yields different results, when the settings are the exact same.
I consider myself a heavy user, and I have never encountered this problem in CD Ripper. Not even with shabby homemade cd's that don't have any online info.

Please enlighten me, because it feels like you're dismissing everything I find.
I don't want to be a nuisance, so I try to be thorough when giving feedback on a program I'm heavily invested in, and enjoy using.

Best regards,

[Boffy]

Just did one more test.
Same CD.
Ripped in CD Ripper.
No internet.
All metadata providers disabled.

The files are named correctly: 0101, 0102, etc

[Spoon]

If you have ever put that CD in the drive before it would be taken from the cache, you would have to click:

Clear Track Metadata

Then retrieve from, to read from a single provider to see which one provides disc number. Neither CD Text or UPC can provide those.

[Boffy]

It still does not address why CD Ripper and Batch Ripper yields different results, when the settings are the exact same.

For none of the above tests have the cache been enabled as a provider in either program.
I set the cache size to 0MB, cleared track metadata, and refreshed with no metadata providers. Not even cache..

CD Ripper still names the files correctly:
0101, 0102, etc.

Did the same exact settings in BR. Disabled all providers in BR, and checked that the profile settings in CDR is still the exact same as before.
BR still names the files incorrectly:
0001, 0002, etc.

Still disconnected from the internet.

Whether disc number only exists online or is present on the cd seems irrelevant at this point.
The disc number is already present with no providers enabled.

CD Ripper does it correctly, Batch Ripper does not.
If this is not a bug, I would really like to understand the logic behind it.

[Spoon]

We shall take a look next time updating Batch Ripper.

[Boffy]

Thank you! Looking forward to it