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: EAC CUETools DB Plugin: wrong offset is set, CTDB still says Accurately ripped (Read 1329 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

EAC CUETools DB Plugin: wrong offset is set, CTDB still says Accurately ripped

I was trying to help a friend to rip his collections.

He forgot to set the offset initially, and got this result (sorry for being in Chinese, he forgot to change that setting too):

Code: [Select]
     峰值电平 95.3 %
     抓取速度 4.4 X
     范围质量 100.0 %
     复制 CRC 54B1FF1B
     复制成功

没有错误发生

状态报告结尾

---- CUETools DB Plugin V2.1.6

[CTDB TOCID: wsL1uzVmlgneplbiKO3McVTB9NI-] found
Submit result: already submitted
Track | CTDB Status
  1   | (55/55) Accurately ripped
  2   | (55/55) Accurately ripped
  3   | (55/55) Accurately ripped

After corrected the offset to +6, the correct one is

Code: [Select]
     Peak level 95.3 %
     Extraction speed 1.9 X
     Range quality 100.0 %
     Copy CRC EC62C024
     Copy OK

No errors occurred

End of status report

---- CUETools DB Plugin V2.1.6

[CTDB TOCID: wsL1uzVmlgneplbiKO3McVTB9NI-] found
Submit result: already submitted
Track | CTDB Status
  1   | (55/55) Accurately ripped
  2   | (55/55) Accurately ripped
  3   | (55/55) Accurately ripped

As you can see, despite the first one is wrong and has the different CRC, CTDB Status claims it's "Accurately ripped".

Is it normal? If so, how can I even tell if my offset it correct or not?
Thanks.


Full los for the interested.

BAD (in Chinese):
Code: [Select]
Exact Audio Copy V1.6 from 23. October 2020

EAC 抓取日志文件从27. 五月 2023, 14:54

Various Artists / 電撃コミックNEXT『アイドルマスター ミリオンライブ！ Blooming Clover』第11巻限定版オリジナルCD

使用驱动器  ：PHILIPS CDRW/DVD SCB5265   Adapter: 1  ID: 2

读取模式      : 可靠Secure
使用精确流     : 是
清空音频缓存    : 是
使用 C2 指示器 : 否

读取偏移校正：               : 0
读取 Lead-In 和 Lead-Out : 否
用静音填充抓取中丢失偏移的采样       : 是
去除首尾静音块               : 否
 在CRC 计算中使用了空样本       : 是
已用接口                  : Win NT 及 2000 本地 Win32 接口

所用输出模式：   : 用户定义的编码器
已选比特率     : 768 kBit/s
质量        : 高
添加 ID3 标签 : 否
命令行压缩器    : H:\Program Files (x86)\Exact Audio Copy\FLAC\FLAC.EXE
附加命令行参数：  : -6 -V -T "ARTIST=%artist%" -T "TITLE=%title%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "TRACKNUMBER=%tracknr%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "BAND=%albuminterpret%" -T "ALBUMARTIST=%albuminterpret%" -T "COMPOSER=%composer%" %haslyrics%--tag-from-file=LYRICS="%lyricsfile%"%haslyrics% -T "DISCNUMBER=%cdnumber%" -T "TOTALDISCS=%totalcds%" -T "TOTALTRACKS=%numtracks%" %hascover%--picture="%coverfile%"%hascover% %source% -o %dest%


已抓取 CD 的 TOC

     音轨 |    起始    |    长度    |  起始扇区  |  结束扇区  
    --------------------------------------------
      1 |  0:00.00 |  4:19.36 |      0 |  19460 
      2 |  4:19.36 |  5:23.47 |  19461 |  43732 
      3 |  9:43.08 | 35:23.61 |  43733 | 203018 


范围状态及错误

已选择范围

     文件名 D:\[220627] 電撃コミックNEXT『アイドルマスター ミリオンライブ！ Blooming Clover』第11巻限定版オリジナルCD\Various Artists - 電撃コミックNEXT『アイドルマスター ミリオンライブ！ Blooming Clover』第11巻限定版オリジナルCD.wav

     峰值电平 95.3 %
     抓取速度 4.4 X
     范围质量 100.0 %
     复制 CRC 54B1FF1B
     复制成功

没有错误发生

状态报告结尾

---- CUETools DB Plugin V2.1.6

[CTDB TOCID: wsL1uzVmlgneplbiKO3McVTB9NI-] found
Submit result: already submitted
Track | CTDB Status
  1   | (55/55) Accurately ripped
  2   | (55/55) Accurately ripped
  3   | (55/55) Accurately ripped


==== 记录校验日志 D6ABA6F369B82F7648D217042BD19DA5468166C22D483F19D7B35C087A6BAB7D ====

GOOD:

Code: [Select]
Exact Audio Copy V1.6 from 23. October 2020

EAC extraction logfile from 27. May 2023, 15:59

Various Artists / 『アイドルマスター ミリオンライブ！ Blooming Clover』第11巻限定版オリジナルCD

Used drive  : PHILIPS CDRW/DVD SCB5265   Adapter: 1  ID: 2

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

Read offset correction                      : 6
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

Used output format              : User Defined Encoder
Selected bitrate                : 896 kBit/s
Quality                         : High
Add ID3 tag                     : No
Command line compressor         : H:\Program Files (x86)\Exact Audio Copy\Flac\flac.exe
Additional command line options : -8 -V %source%


TOC of the extracted CD

     Track |   Start  |  Length  | Start sector | End sector 
    ---------------------------------------------------------
        1  |  0:00.00 |  4:19.36 |         0    |    19460   
        2  |  4:19.36 |  5:23.47 |     19461    |    43732   
        3  |  9:43.08 | 35:23.61 |     43733    |   203018   


Range status and errors

Selected range

     Filename D:\Various Artists - 『アイドルマスター ミリオンライブ！ Blooming Clover』第11巻限定版オリジナルCD.wav

     Peak level 95.3 %
     Extraction speed 1.9 X
     Range quality 100.0 %
     Copy CRC EC62C024
     Copy OK

No errors occurred

End of status report

---- CUETools DB Plugin V2.1.6

[CTDB TOCID: wsL1uzVmlgneplbiKO3McVTB9NI-] found
Submit result: already submitted
Track | CTDB Status
  1   | (55/55) Accurately ripped
  2   | (55/55) Accurately ripped
  3   | (55/55) Accurately ripped


==== Log checksum 3B8F09A8511FAD960BD0EC643FE083D27159E18C1957F5E8FCFD79000AD3B654 ====

Re: EAC CUETools DB Plugin: wrong offset is set, CTDB still says Accurately ripped

Reply #1 –
http://cue.tools/wiki/CUETools_Database#What_are_the_advantages.3F
Quote
CTDB is free of the offset problems. You don't even need to set up offset correction for your CD drive to be able to verify and what's more important, submit rips to the database. Different pressings of the same CD are treated as the same disc by the database; it doesn't care.
korth

Re: EAC CUETools DB Plugin: wrong offset is set, CTDB still says Accurately ripped

Reply #2 –
Thanks. I have read that before, but I thought that means it will just handle different pressings (by storing a few "legit" offset values in database), than accepting arbitrary offset (since it's unlikely this random -6 offset data is another "real" pressing).

Re: EAC CUETools DB Plugin: wrong offset is set, CTDB still says Accurately ripped

Reply #3 –
Quote from: fireattack on
(since it's unlikely this random -6 offset data is another "real" pressing).
Oh? A surprise for you at https://www.daefeatures.co.uk/search . Yes those are read offsets and not write offsets, but just have a few glances at the amount of different figures and how they can differ by six: 6, 12, and also 685, 691 and 696, 702.
Also it does happen that a new pressing is "mastered" from ripping a CD, in which case read offset becomes relevant also for pressings.

Re: EAC CUETools DB Plugin: wrong offset is set, CTDB still says Accurately ripped

Reply #4 –
Quote from: Porcus on
Quote from: fireattack on
(since it's unlikely this random -6 offset data is another "real" pressing).
Oh? A surprise for you at https://www.daefeatures.co.uk/search . Yes those are read offsets and not write offsets, but just have a few glances at the amount of different figures and how they can differ by six: 6, 12, and also 685, 691 and 696, 702.
Also it does happen that a new pressing is "mastered" from ripping a CD, in which case read offset becomes relevant also for pressings.

Sure, that's a good point. But for this specific disk it's unlikely.

Anyway, the point is CTDB  will consider any offset to be valid.

Re: EAC CUETools DB Plugin: wrong offset is set, CTDB still says Accurately ripped

Reply #5 –
AccurateRip stores a separate checksum for each track at each offset.

CTDB stores the entire disc under one checksum. The checksum of the original submission can be offset  ≈+/- 5880 samples to verify if the audio in your rip matches.
korth