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: Result rip in Cuetools (Read 68183 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Result rip in Cuetools

Hi guys, I hope this is right section to post. I ripped a cd with Eac and with this result:

Spoiler (click to show/hide)

When I check with cuetools I got his report:

Spoiler (click to show/hide)

Status in cue log is (000+000/222). My offset is right but if I try to Encode with "fix offset" I get this result:

Spoiler (click to show/hide)

Now...my rip is perfect (maybe with a different cd pressing) or there's something wrong? Because encode with fix offset I get this result Status like in spoiler (013+016/222). Or I trust Eac log with test and copy crc and ignore previous status (00+00/222)?

     Peak level 100.0 %
     Range quality 100.0 %
     Test CRC 0B8F3AFE
     Copy CRC 0B8F3AFE
     Copy OK
"Always account for the change."

Re: Result rip in Cuetools

Reply #1 –
You don't need to apply 'fix offset'. If you enter the offset value in the Offset box and Verify with CUETools, you'll get the same result in the log without altering your rip.

Applying 'fix offset' by xx samples discards xx samples from one end of your rip and adds xx null samples to the other so the audio data in-between can be offset by xx samples. The audio data in-between isn't changed or improved, it is just moved (offset). If the value of xx samples is too large, some of the audio data can even be lost by applying 'fix offset'.

Keep your original rip. You aren't relying on EAC test and copy alone. You verified the rip with CUETools. The CTDB results show your rip matches other rips in that database. The AccurateRip results do show (00+00/nnn) for your pressing but also show the audio data in your rip matches rips from other pressings (offsets) in that database.
korth

Re: Result rip in Cuetools

Reply #2 –
Thanks for the answer @korth! Just another little question...In cuetools log sometimes I see no crc32 text next to voice W/O NULL such as in example:

Track Peak [ CRC32  ] [W/O NULL]
 --   99,2 [1F990C87] [E22323BD]
 01   89,0 [6B0893B1] [D222C284]          
 02   89,1 [7A6B5C8A] [6AB7BC59]          
 03   88,8 [360033A8] [95C7319F]          
 04   89,0 [2AA19A69] [B9B5C54E]          
 05   89,1 [5FAF604A] [2D839B90]          
 06   89,1 [E2D04419] [F765B8BD]          
 07   89,1 [5FA9C736] [5C3876B3]          
 08   89,1 [CA4F28D1] [A5AB605E]          
 09   81,0 [415325E0] [7777DFBB]          
 10   80,0 [83BBB9BC] [18954F89]          
 11   89,1 [8CE07539] [DB0878BA]          
 12   88,3 [81A00931] [07BA7889]          
 13   89,1 [9F20C211] [66B4356B]          
 14   89,1 [EAA38C7F] [F4C74000]          
 15   89,1 [294CEE41] [9F798ADE]          
 16   83,8 [63A6B19F] [6CD8138C]          
 17   77,7 [DE9F8224] [40B2D63B]          
 18   99,2 [F454D1DC] [1BA09781]          
 19   85,2 [423B66F0] [186C3A2E]   

Is it normal? CRC32 in EAC is the same. Or I got this for other album:

Track Peak [ CRC32  ] [W/O NULL] [  LOG   ]
 --  100,0 [0A396253] [A0C3E246]  W/O NULL

"Always account for the change."

Re: Result rip in Cuetools

Reply #3 –
If you're asking about the  [  LOG   ] column ... http://cue.tools/wiki/CUETools_log#EAC-Style_Info_Section

When verifying, CUETools expects the EAC log to have the same name as the input file so if your input is
artist - album.cue
then CUETools expects the EAC log to be named
artist - album.log

When verifying one rip at a time, there is a popup window that lets you select the correct .log file when the EAC log file has a different name than the input file.
When verifying in batch mode (multiple rips at a time) the popup windows are turned off.
If the folder only contains one .log file, CUETools will usually assume that it is the correct one even if named other than expected but if the folder contains more than one .log file, none are named as expected and popups are off, then no .log files are parsed.

CUETools also has a problem when the EAC log contains more than one rip (appended to the end of previous rip).
korth

Re: Result rip in Cuetools

Reply #4 –
Quote from: korth on
If you're asking about the  [  LOG   ] column ... http://cue.tools/wiki/CUETools_log#EAC-Style_Info_Section

When verifying, CUETools expects the EAC log to have the same name as the input file so if your input is
artist - album.cue
then CUETools expects the EAC log to be named
artist - album.log

Yeah I mean that. .log and .cue are renamed equal. So why there's no [ LOG ] column in cuetools log? Anyway without log column the rip is just as right?
"Always account for the change."
 

Re: Result rip in Cuetools

Reply #5 –
That whole section is just additional information. The LOG column is helpful to confirm the audio in the file(s) you have is the same as when ripped. You said you verified the CRC32 manually.
korth

Re: Result rip in Cuetools

Reply #6 –
Yes, I verified manually. CD is ripped in a single track, [1F990C87] first column CRC32. So can I ignore missing log column in simple terms?
"Always account for the change."

Re: Result rip in Cuetools

Reply #7 –
You can, yes.
korth