Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Verifying CD rip against AccurateRip database without log file (Read 1720 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Verifying CD rip against AccurateRip database without log file

I have rips made with EAC, tracks to individual files, gap appended to previous track. Settings are correct (drive offset properly configured, no overread, replace missing offsets with silence…), but the .log files have been deleted.

If I use CUETools to verify the rips, it doesn't find them in the AccurateRip database:
Code: [Select]
[CUETools log; Date: 2024-08-02 6:38:20; Version: 2.2.6]
[CTDB TOCID: jgPZvkR841et.0bYqPkJuBR26.A-] found.
Track | CTDB Status
  1   | (2/2) Accurately ripped
  2   | (2/2) Accurately ripped
  3   | (2/2) Accurately ripped
  4   | (2/2) Accurately ripped
  5   | (2/2) Accurately ripped
  6   | (2/2) Accurately ripped
  7   | (2/2) Accurately ripped
  8   | (2/2) Accurately ripped
  9   | (2/2) Accurately ripped
 10   | (2/2) Accurately ripped
[AccurateRip ID: 00113edf-0087dc80-7b0ac70a] disk not present in database.

Track Peak [ CRC32  ] [W/O NULL] 
 --   99.6 [5E65743F] [8D665B7E]           
 01   99.6 [D8C55D86] [D8F400D0]           
 02   99.6 [CDA2DAD2] [421251C1]           
 03   99.6 [9CB0F3E9] [EB9B1427]           
 04   99.6 [76285A9E] [B423BE5E]           
 05   99.6 [9CC6FAB4] [300318B9]           
 06   99.6 [56F36E0B] [50A973EE]           
 07   99.6 [BD229E78] [F443AA5D]           
 08   99.6 [BC469736] [5E93209A]           
 09   99.6 [1832E126] [5533900C]           
 10   99.6 [C38BACB6] [BFC8EFB8]          

If I make again the exact same rip, but keeping the .log file, CUETools finds the rip in the AccurateRip database:
Code: [Select]
[CUETools log; Date: 2024-08-02 6:38:30; Version: 2.2.6]
Pregap length 00:00:32.
[CTDB TOCID: jgPZvkR841et.0bYqPkJuBR26.A-] found.
Track | CTDB Status
  1   | (2/2) Accurately ripped
  2   | (2/2) Accurately ripped
  3   | (2/2) Accurately ripped
  4   | (2/2) Accurately ripped
  5   | (2/2) Accurately ripped
  6   | (2/2) Accurately ripped
  7   | (2/2) Accurately ripped
  8   | (2/2) Accurately ripped
  9   | (2/2) Accurately ripped
 10   | (2/2) Accurately ripped
[AccurateRip ID: 0011403f-0087e4bf-740ac70a] found.
Track   [  CRC   |   V2   ] Status
 01     [d79b626b|ec2d8199] (0+3/3) Accurately ripped
 02     [586bdfc7|ea5ccf48] (0+3/3) Accurately ripped
 03     [dfbcd7bc|b46ad979] (0+3/3) Accurately ripped
 04     [b9301f4d|3b211ccf] (0+3/3) Accurately ripped
 05     [e0fffe9d|d64dc00d] (0+3/3) Accurately ripped
 06     [d03b0224|57cc8d8b] (0+3/3) Accurately ripped
 07     [0883fc29|e47a68bf] (0+3/3) Accurately ripped
 08     [58bccc63|e88ea9d0] (0+3/3) Accurately ripped
 09     [7fa2f6d4|15795da0] (0+3/3) Accurately ripped
 10     [8bb0da4e|d704b139] (0+3/3) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL] [  LOG   ]
 --   99.6 [84FE1354] [8D665B7E]           
 01   99.6 [D8C55D86] [D8F400D0]   CRC32   
 02   99.6 [CDA2DAD2] [421251C1]   CRC32   
 03   99.6 [9CB0F3E9] [EB9B1427]   CRC32   
 04   99.6 [76285A9E] [B423BE5E]   CRC32   
 05   99.6 [9CC6FAB4] [300318B9]   CRC32   
 06   99.6 [56F36E0B] [50A973EE]   CRC32   
 07   99.6 [BD229E78] [F443AA5D]   CRC32   
 08   99.6 [BC469736] [5E93209A]   CRC32   
 09   99.6 [1832E126] [5533900C]   CRC32   
 10   99.6 [C38BACB6] [BFC8EFB8]   CRC32  

In my collection, I have had deleted all the .log files, and I do not want to keep the .log files under any circumstances (non-negotiable, heavy OCPD guy here).

So, without these .log files, is there still a way to verify the rips against the AccurateRip database?

Re: Verifying CD rip against AccurateRip database without log file

Reply #1 –
I take it you deleted the CUE sheets too as that's the file that contains the track 1 pregaps, as can be seen from the EAC log.
Code: [Select]
Pregap length 00:00:32.

I don't keep log files but I do keep the CUE sheets if they contain PREGAP information.

If you change the following setting in CUETools it will display the list of PREGAPS associated with that disc.
Code: [Select]
Settings > Advanced > CTDB > Detailed log: True

You could use that information to build a basic CUE sheet for verification purposes:
Code: [Select]
FILE "01.flac" WAVE
  TRACK 01 AUDIO
    PREGAP 00:00:32
    INDEX 01 00:00:00
FILE "02.flac" WAVE
  TRACK 02 AUDIO
    INDEX 01 00:00:00

You can embed the CUE sheet, but I don't like having that information in the files.

Re: Verifying CD rip against AccurateRip database without log file

Reply #2 –
foobar2000 usually has no problems verifying such logless files with AccurateRip. At least Mac version.

Re: Verifying CD rip against AccurateRip database without log file

Reply #3 –
Quote from: Guildencrantz on
foobar2000 usually has no problems verifying such logless files with AccurateRip. At least Mac version.
If the pregap information isn't retained you're potentially going to get some erroneous results.

Here's the output from foobar:
Code: [Select]
Track 1: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC DFE15866]
Track 2: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC 0C3E9073]
Track 3: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC F3DB24BD]
Track 4: AccurateRip Verified Confidence 200, Pressing Offset +0 [ARv2 CRC 51B566C6]
Track 5: AccurateRip Verified Confidence 200, Pressing Offset +0 [ARv2 CRC 9676C9B7]
Track 6: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC 909AAC69]
Track 7: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC A656AC11]
Track 8: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC 4E33D548]
Track 9: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC 46AAAC28]
Track 10: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC 075F392D]
Track 11: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC BD1DCE5D]
Track 12: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC 404E11FB]
Track 13: AccurateRip Verified Confidence 200, Pressing Offset +149 [ARv2 CRC 07EBD8D0]

And here's the pertinent information from CUETools using the correct pregap:
Code: [Select]
Pregap length 00:00:33.
[AccurateRip ID: 0012525b-00b975e3-c009560d] found.
Track   [  CRC   |   V2   ] Status
 01     [4c916eda|b919d5d6] (171+200/4228) Accurately ripped
 02     [340d929e|c63f1218] (169+200/4233) Accurately ripped
 03     [4012a400|c8e02e7e] (170+200/4227) Accurately ripped
 04     [1ab6e980|51b566c6] (170+200/4236) Accurately ripped
 05     [c4ad7b54|9676c9b7] (170+200/4234) Accurately ripped
 06     [806c28d5|a9e0332c] (168+200/4230) Accurately ripped
 07     [98673c22|03c308d9] (170+200/4224) Accurately ripped
 08     [a2e95b18|0863ee94] (170+200/4211) Accurately ripped
 09     [41e2bc6a|6d9c96b6] (171+200/4236) Accurately ripped
 10     [799c5407|31d5a5d4] (169+200/4223) Accurately ripped
 11     [f4216f6b|7af8e7fd] (167+200/4216) Accurately ripped
 12     [632337f9|1afd74be] (173+200/4231) Accurately ripped
 13     [ca16943c|a7b7de87] (169+200/4192) Accurately ripped

This is from a disc with many pressings and multiple pregaps (Sgt. Pepper's Lonely Hearts Club Band: CDP 7 46442 2), which is rare, but for some users (especially those with OCPD) the correct identification is important.

Re: Verifying CD rip against AccurateRip database without log file

Reply #4 –
Quote from: SimBun on
If you change the following setting in CUETools it will display the list of PREGAPS associated with that disc.
Code: [Select]
Settings > Advanced > CTDB > Detailed log: True

You could use that information to build a basic CUE sheet for verification purposes:
Code: [Select]
FILE "01.flac" WAVE
  TRACK 01 AUDIO
    PREGAP 00:00:32
    INDEX 01 00:00:00
FILE "02.flac" WAVE
  TRACK 02 AUDIO
    INDEX 01 00:00:00
You don't need to build a CUE sheet.
X
You could simply add the info you found in the detailed log to the 'Extra' section before verify.

Quote from: BigBertrand on
I have rips made with EAC, tracks to individual files
Quote from: SimBun on
You can embed the CUE sheet, but I don't like having that information in the files.
Embed CUE in individual track files?
korth

Re: Verifying CD rip against AccurateRip database without log file

Reply #5 –
Quote from: korth on
Quote from: SimBun on
You could use that information to build a basic CUE sheet for verification purposes:
Code: [Select]
FILE "01.flac" WAVE
  TRACK 01 AUDIO
    PREGAP 00:00:32
    INDEX 01 00:00:00
FILE "02.flac" WAVE
  TRACK 02 AUDIO
    INDEX 01 00:00:00
You don't need to build a CUE sheet.
[attach type=image]31806[/attach]
You could simply add the info you found in the detailed log to the 'Extra' section before verify.
My assumption is that the OP will want to be able to run a verification step without any manual intervention going forwards (possibly in batch), but if it's only a one-off then yes you could just perform an interactive verification.

Quote from: korth on
Quote from: SimBun on
You can embed the CUE sheet, but I don't like having that information in the files.
Embed CUE in individual track files?
I've never done it but yes, if you really don't want to keep any external text files you could embed the cuesheet in your music files, although it's a lot of redundant information and I assume CUETools won't read them so you'd still have a problem with verification, except you'll now have a record of the correct pregap.

Keeping the CUE sheets is useful for recording other attributes that are otherwise lost e.g. discs with multiple subindexes (>01) or pre-emphasis.

Re: Verifying CD rip against AccurateRip database without log file

Reply #6 –
Quote from: SimBun on
My assumption is that the OP will want to be able to run a verification step without any manual intervention going forwards (possibly in batch), but if it's only a one-off then yes you could just perform an interactive verification.
CUETools can get information from the EAC extraction .log file, .CUE sheet, .toc file (as saved by CUETools), AccurateRip tags, and CDTOC tag.
The .toc file and CDTOC tag are only written (by CUETools) when encoding.
korth

Re: Verifying CD rip against AccurateRip database without log file

Reply #7 –
Quote from: korth on
CUETools can get information from the EAC extraction .log file, .CUE sheet, .toc file (as saved by CUETools), AccurateRip tags, and CDTOC tag.
The .toc file and CDTOC tag are only written (by CUETools) when encoding.
You lose visibility of the pregap (if that's important to you) but if you only care about verification then the ACCURATERIPID tag seems like a good concise embedded option, even though it requires a two stage process if the OP is still using EAC.

Re: Verifying CD rip against AccurateRip database without log file

Reply #8 –
Thank you all for your answers, that solved my problem. I'm using the solution provided in SimBun's reply and augmented in korth's reply:

  • Enable detailed log.
  • Do a first verification, using zero pregap.
  • If the result reported a pregap, do a second verification using that pregap.

By the way, I like this detailed log, as it reports data track for instance.

Also, I understood why I said myself "hey, I didn't have this issue previously", that's because:
  • some CDs don't have pregap, thus verifying their rips gives the AccurateRip results "out of the box",
  • and some other CDs have pregap (seems to be often 32s), thus requiring the extra steps above to get the AccurateRip results.
 

Re: Verifying CD rip against AccurateRip database without log file

Reply #9 –
You could use PerfectTUNES, the AccurateRip component is free, it will lookup the pregap (we have a database of 2 million pregaps) and will cross pressing check also.