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: CUETools - Custom scripts (fix offset) (Read 293 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CUETools - Custom scripts (fix offset)

I am a new user of CUETools and would like to know what is the difference in function between repair and fix offset profiles.

Custom scripts

For testing purposes, I ripped the CD without the offset correction set in EAC (Read offset correction : 0). Then I used the fix profil. In Extra settings I set the correct offset correction for my recorder (ASUS DRW-2014L1T) which is +6

Code: [Select]
EAC extraction logfile from 19. July 2024, 19:50

Scorpions / White Dove

Used drive  : ASUS    DRW-2014L1T   Adapter: 1  ID: 0

Read mode               : Secure
Utilize accurate stream : Yes
Defeat audio cache      : Yes
Make use of C2 pointers : No

Read offset correction                      : 0
Overread into Lead-In and Lead-Out          : No
Fill up missing offset samples with silence : Yes
Delete leading and trailing silent blocks   : No
Null samples used in CRC calculations       : Yes
Used interface                              : Native Win32 interface for Win NT & 2000

X

Before using the fix script
Code: [Select]
[CUETools log; Date: 19.07.2024 19:52:34; Version: 2.2.5]
Pregap length 00:00:32.
[CTDB TOCID: lgF_0QjFMQ8s5oRFV3j7IsWJ2pY-] found.
Track | CTDB Status
  1   | (138/140) Accurately ripped
  2   | (139/140) Accurately ripped, or (1/140) differs in 131 samples @03:19:47
  3   | (137/140) Accurately ripped
[AccurateRip ID: 0001a0b6-00056072-1f02b603] found.
Track   [  CRC   |   V2   ] Status
 01     [2d1afefb|1f04eb7b] (00+00/54) No match
 02     [b7c1bae6|ffff3903] (00+00/54) No match
 03     [b4bfd65f|26a59193] (00+00/53) No match
Offsetted by -469:
 01     [65d2d47b] (03/54) Accurately ripped
 02     [ebfcf0a7] (03/54) Accurately ripped
 03     [fd2533fe] (03/53) Accurately ripped
Offsetted by 6:
 01     [520f4948] (18/54) Accurately ripped
 02     [e1d2747d] (18/54) Accurately ripped
 03     [4aa29c96] (18/53) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL] [  LOG   ]
 --  100,0 [5D5BEF6F] [5FAC04B1]   CRC32  
 01   99,9 [B1AEA757] [D3B3D6AA]          
 02  100,0 [86DDCA81] [FB1875CA]          
 03   93,4 [9E06E5F0] [58B73564]

After using the fix script (verify script)
Code: [Select]
[CUETools log; Date: 19.07.2024 20:24:33; Version: 2.2.5]
Pregap length 00:00:32.
Offset applied: 6
[CTDB TOCID: lgF_0QjFMQ8s5oRFV3j7IsWJ2pY-] found.
Track | CTDB Status
  1   | (138/140) Accurately ripped
  2   | (139/140) Accurately ripped, or (1/140) differs in 131 samples @03:19:47
  3   | (137/140) Accurately ripped
[AccurateRip ID: 0001a0b6-00056072-1f02b603] found.
Track   [  CRC   |   V2   ] Status
 01     [520f4948|44abe61b] (18+31/54) Accurately ripped
 02     [e1d2747d|287dcd8b] (18+31/54) Accurately ripped
 03     [4aa29c96|bc8d2d85] (18+30/53) Accurately ripped
Offsetted by -475:
 01     [65d2d47b] (03/54) Accurately ripped
 02     [ebfcf0a7] (03/54) Accurately ripped
 03     [fd2533fe] (03/53) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL] [  LOG   ]
 --  100,0 [127735C4] [98389886] [5D5BEF6F]
 01   99,9 [17BEC7A7] [C7FE2865]          
 02  100,0 [8906583F] [52387B9E]          
 03   93,4 [FEB7E580] [58B73564]

CUETools recoded the input file using the set offset and the resulting file is now correct (AccurateRip), ok.
The problem occurs when I want to use offset correction -469 then offset 6 is still used. Of course I know that offset 6 has more confidence but I am doing this for testing purposes.

X

I have changed the settings but this does not help
X

Why, despite the offset being changed to -469, still +6 is in use?

Re: CUETools - Custom scripts (fix offset)

Reply #1 –
'fix offset' adjusts the offset to a pressing that has the highest overall AccurateRip confidence level (if exists).
See the 'to nearest' setting http://cue.tools/wiki/CUETools_Advanced_Settings:_AccurateRip#Fix_offset
Quote
to nearest
When checked, the smallest amount of offset will be applied that gives an accurate result at zero offset after fix. When unchecked, offset will be applied that gives the highest AccurateRip confidence result at zero offset after fix.
korth

Re: CUETools - Custom scripts (fix offset)

Reply #2 –
Quote from: korth on
'fix offset' adjusts the offset to a pressing that has the highest overall AccurateRip confidence level (if exists).

Ah, so it's an 'automat' that matches the rip to the offset with the highest AccureRip match value. Does the 'to nearest' setting then make any sense in this case?

X

So if I want to add the offset I am interested in manually I will have to use the repair script? The fix offset script is full automatic without the possibility of defining the offset manually, right? If my CD pressing is in the AccurateRip database, then this offset will be applied automatically (fix offset script), right?

Re: CUETools - Custom scripts (fix offset)

Reply #3 –
I modified my post above before you completed yours.

You manually add offset in the 'extra' section as in one of your images above except Action: Encode 'default'.

'Repair' is a completely different topic. It doesn't have anything to do with offset.



korth
 

Re: CUETools - Custom scripts (fix offset)

Reply #4 –
@korth Thank you very much, now everything is clear.