IPB

Welcome Guest ( Log In | Register )

9 Pages V  « < 6 7 8 9 >  
Reply to this topicStart new topic
CUETools DB
korth
post Dec 30 2012, 15:27
Post #176





Group: Members
Posts: 431
Joined: 13-March 11
Member No.: 88969



QUOTE (Eli @ Dec 30 2012, 14:53) *
CT was then able to recognize the disc, but still wouldn't do a repair.

The recovery record can only repair a limited amount of damage. Your rip likely exceeds that amount of damage.

This post has been edited by korth: Dec 30 2012, 15:32


--------------------
korth
Go to the top of the page
+Quote Post
Eli
post Dec 30 2012, 16:36
Post #177





Group: Members
Posts: 1056
Joined: 16-October 03
Member No.: 9337



QUOTE (korth @ Dec 30 2012, 09:27) *
QUOTE (Eli @ Dec 30 2012, 14:53) *
CT was then able to recognize the disc, but still wouldn't do a repair.

The recovery record can only repair a limited amount of damage. Your rip likely exceeds that amount of damage.


Korth, you are probably right. I wish CT would tell you something to that effect...


--------------------
http://forum.dbpoweramp.com/showthread.php?t=21072
Go to the top of the page
+Quote Post
lvqcl
post Dec 30 2012, 17:44
Post #178





Group: Developer
Posts: 3362
Joined: 2-December 07
Member No.: 49183



http://www.cuetools.net/wiki/CUETools_log

Accurately ripped -- Your rip matches database records for this track
Differs in ... -- Partial match this track, might be repairable
No match -- Too many samples differ
Go to the top of the page
+Quote Post
ebz777
post Jan 1 2013, 14:49
Post #179





Group: Members
Posts: 5
Joined: 27-November 12
Member No.: 104805



Add Chromaprint and AcoustID relationships within CUETools DB

Hello Gregory,
The CUETools DB is already cross-referencing at the CD TOC level the freedb and MusicBrainz databases.
Would you also consider doing this at the tracklevel with Chromaprint fingerprints and AcoustIDs (see http://acoustid.org/) ?

This would help the match of an individual track to a release, regardless of any later lossy re-encoding. This is something you cannot do with the current CUETools DB tracks CRCs alone : there is now way to calculate that proper CRC for an mp3 track for example. The only way to ensure a consistent fingerprint calculation for a CD release is at ripping time.

It would require to calculate the chromaprint fingerprint for every tracked ripped with CUERipper and add these references to CUETtools DB.
I'm not sure though that CUETools DB should also link the AcoustID; the fingerprint -> AcoustID assignment process is still very far from perfect (see http://forums.musicbrainz.org/viewtopic.php?id=3869). But it could be considered safe, there is no plan to merge AcoustID I believe and it would be a nice bonus !

Maybe CUERipper/CUETools could then also publish the calculated Chromaprint fingerprints to the AcoustID DB (see http://acoustid.org/webservice#submit)

Additionally CUETools could then also tag the tracks it generates with the AcoustID

Thanks
Go to the top of the page
+Quote Post
bilbo
post Jan 1 2013, 17:13
Post #180





Group: Members
Posts: 190
Joined: 16-April 07
Member No.: 42593



QUOTE (ebz777 @ Jan 1 2013, 08:49) *
Add Chromaprint and AcoustID relationships within CUETools DB
This would help the match of an individual track to a release, regardless of any later lossy re-encoding.


CUEToolsDB is meant to verify and/or repair rips from a CD. Why would anyone want to verify a "lossy" track? That is the opposite of what the DB was designed to accomplish.


--------------------
Glass half full!
Go to the top of the page
+Quote Post
ebz777
post Jan 2 2013, 00:11
Post #181





Group: Members
Posts: 5
Joined: 27-November 12
Member No.: 104805



QUOTE (bilbo @ Jan 1 2013, 17:13) *
CUEToolsDB is meant to verify and/or repair rips from a CD. Why would anyone want to verify a "lossy" track?


Yes, the data correction made ​​during a rip is what motivates a large number of users to publish their information in the database in the first place. But once the information is out there it is metadata that can be used for purposes that were not originally intended. Eg to identify similar recordings from different releases, to find out what recordings exactly are included in a compilation. To identify whether a particular release includes the original or remastered version of a recording. Or in the presence of a piece of music lossy you want to tag, to know what CD this song was coming from.

This is something that you cannot do with the track CRC calculated today, but that you could do if you add a fingerprint calculation to the track.

It's of course best calculated at rip time since it's the surest way to ensure consistency between a CD and its track information.
Go to the top of the page
+Quote Post
Gregory S. Chudo...
post Jan 2 2013, 01:15
Post #182





Group: Developer
Posts: 698
Joined: 2-October 08
From: Ottawa
Member No.: 59035



It doesn't seem very fair - people that would be wasting their CPU cycles to calculate those fingerprints would be helping a completely different category of users to identify random mp3s.


--------------------
CUETools 2.1.4
Go to the top of the page
+Quote Post
Eli
post Jun 4 2013, 01:51
Post #183





Group: Members
Posts: 1056
Joined: 16-October 03
Member No.: 9337



CueTools 2.1.5

I am trying to repair a disc
The Rolling Stones
Exile on Main St.
CTDB TOCID: kXCUmR9eH1zJRjVprT_Hvhp_Kzc-

I am able to verify the disc fine:
CODE

[CUETools log; Date: 6/3/2013 8:46:47 PM; Version: 2.1.5]
[CTDB TOCID: kXCUmR9eH1zJRjVprT_Hvhp_Kzc-] found.
Track | CTDB Status
1 | (40/41) Accurately ripped
2 | (41/41) Accurately ripped
3 | (41/41) Accurately ripped
4 | (41/41) Accurately ripped
5 | (40/41) Accurately ripped
6 | (40/41) Accurately ripped
7 | (40/41) Accurately ripped
8 | (39/41) Accurately ripped
9 | (39/41) Accurately ripped
10 | (40/41) Accurately ripped
11 | (40/41) Accurately ripped
12 | (38/41) Accurately ripped
13 | (38/41) Accurately ripped
14 | (39/41) Accurately ripped
15 | (31/41) Differs in 35 samples @00:13:31-00:13:32
16 | (37/41) Accurately ripped
17 | (35/41) Accurately ripped
18 | (36/41) Accurately ripped
[AccurateRip ID: 002ab05f-023b7e5b-f50fc512] found.
Track [ CRC | V2 ] Status
01 [3d93162a|cd2757b3] (074+003/349) Accurately ripped
02 [7c634221|95c2e2e1] (073+003/349) Accurately ripped
03 [23d503ed|98b85eef] (074+003/355) Accurately ripped
04 [3f1e5129|d771c8fa] (074+003/349) Accurately ripped
05 [c8227004|8192ee79] (075+003/355) Accurately ripped
06 [7e1afc91|8565f83f] (074+003/349) Accurately ripped
07 [895203b2|735c7815] (073+003/349) Accurately ripped
08 [47598ba8|ead177ad] (073+003/351) Accurately ripped
09 [479220a6|8ace56d1] (072+003/347) Accurately ripped
10 [4db31259|7bf5c4c3] (072+003/347) Accurately ripped
11 [3eaf488d|1039e7ef] (072+003/346) Accurately ripped
12 [fb309295|5e3a4f6b] (072+003/347) Accurately ripped
13 [1d9e8a7c|25010632] (072+003/338) Accurately ripped
14 [6ef1796d|ea98ffaa] (072+003/336) Accurately ripped
15 [d781ac36|6768463e] (000+000/338) No match
16 [bd9a1da4|6ab7466d] (071+003/334) Accurately ripped
17 [c2e9e1c4|275f2638] (073+003/330) Accurately ripped
18 [0c2fb6e7|39781207] (070+003/321) Accurately ripped
Offsetted by 76:
01 [009fb622] (002/349) Accurately ripped
02 [d23367ae] (002/349) Accurately ripped
03 [159aef17] (002/355) Accurately ripped
04 [53d16027] (002/349) Accurately ripped
05 [554d3116] (002/355) Accurately ripped
06 [cb2c24b8] (000/349) No match (V2 was not tested)
07 [bab54b8d] (000/349) No match (V2 was not tested)
08 [b278672a] (002/351) Accurately ripped
09 [2420d59e] (002/347) Accurately ripped
10 [aef143b6] (002/347) Accurately ripped
11 [021e8ecb] (002/346) Accurately ripped
12 [bf03a663] (002/347) Accurately ripped
13 [c032788c] (002/338) Accurately ripped
14 [fe7c9eb5] (002/336) Accurately ripped
15 [69ee3f21] (000/338) No match (V2 was not tested)
16 [4b96ee3b] (002/334) Accurately ripped
17 [67b38275] (002/330) Accurately ripped
18 [d1be152e] (000/321) No match (V2 was not tested)
Offsetted by 664:
01 [a26e64a2] (168/349) Accurately ripped
02 [f17cd341] (169/349) Accurately ripped
03 [9fb7d390] (172/355) Accurately ripped
04 [4ed38139] (168/349) Accurately ripped
05 [a89fd22b] (175/355) Accurately ripped
06 [fd29d425] (170/349) Accurately ripped
07 [6e12aace] (169/349) Accurately ripped
08 [38ac53d6] (169/351) Accurately ripped
09 [ddfd4d89] (165/347) Accurately ripped
10 [6db7a9a5] (168/347) Accurately ripped
11 [ac16c55d] (167/346) Accurately ripped
12 [f6515282] (171/347) Accurately ripped
13 [0c33b759] (163/338) Accurately ripped
14 [0092fdb4] (164/336) Accurately ripped
15 [b2b9c150] (000/338) No match (V2 was not tested)
16 [df81134e] (161/334) Accurately ripped
17 [aed29e8e] (161/330) Accurately ripped
18 [8d45be26] (154/321) Accurately ripped
Offsetted by 2140:
01 [83ed544a] (075/349) Accurately ripped
02 [12537512] (075/349) Accurately ripped
03 [14c5cc55] (077/355) Accurately ripped
04 [7366a48e] (075/349) Accurately ripped
05 [159973ef] (073/355) Accurately ripped
06 [f3b1b8a4] (075/349) Accurately ripped
07 [a17d3ef2] (077/349) Accurately ripped
08 [c8d95ab6] (077/351) Accurately ripped
09 [4e49411f] (078/347) Accurately ripped
10 [8d8409be] (075/347) Accurately ripped
11 [f7ada841] (075/346) Accurately ripped
12 [da86fb24] (072/347) Accurately ripped
13 [de6ab9b4] (071/338) Accurately ripped
14 [dd314f57] (070/336) Accurately ripped
15 [b6ea7a75] (000/338) No match (V2 was not tested)
16 [365fdba9] (072/334) Accurately ripped
17 [93a1fc6f] (068/330) Accurately ripped
18 [f510276c] (065/321) Accurately ripped

Track Peak [ CRC32 ] [W/O NULL]
-- 97.7 [F215327F] [561E67E0]
01 97.7 [FEB5E1BA] [81AB5674]
02 97.7 [A42C7CAD] [ADBFE045]
03 84.7 [B2486164] [57A64BDD]
04 97.7 [D31DB1EE] [89BD4C76]
05 97.7 [72F66D51] [E62C37D4]
06 97.7 [43EFFACF] [06A347A2]
07 97.7 [46B24C6F] [AF099ACD]
08 97.7 [47EBA0D1] [805EC507]
09 97.7 [EDBA4CEE] [0AF13865]
10 97.7 [8E17B700] [E1C62A3A]
11 85.9 [A621CDE9] [98631D15]
12 97.7 [A49DD7DF] [1FAECAD8]
13 86.9 [B76795DB] [C446C48B]
14 97.7 [4FF15683] [D2788406]
15 97.7 [D0E72E22] [9BA021C4]
16 97.7 [97D1D4D9] [F0E89505]
17 97.7 [61BF4321] [3A1119E0]
18 97.7 [00E9D0D0] [B2DA7473]


But when I try to repair, I get an error that says

"Unsupported Encoder Settings"

I have been able to repair other discs with 2.1.5, also encoded with FLAC by dBpoweramp. And since it can read and verify, I don't understand why it can't repair.


--------------------
http://forum.dbpoweramp.com/showthread.php?t=21072
Go to the top of the page
+Quote Post
Gregory S. Chudo...
post Jun 4 2013, 03:15
Post #184





Group: Developer
Posts: 698
Joined: 2-October 08
From: Ottawa
Member No.: 59035



Does it let you convert without repair? I only have one theory so far - maybe there's an oversized (above 1m) artwork in source folder? 2.1.5 is unintentionally picky about that.


--------------------
CUETools 2.1.4
Go to the top of the page
+Quote Post
Eli
post Jun 4 2013, 04:00
Post #185





Group: Members
Posts: 1056
Joined: 16-October 03
Member No.: 9337



QUOTE (Gregory S. Chudov @ Jun 3 2013, 22:15) *
Does it let you convert without repair? I only have one theory so far - maybe there's an oversized (above 1m) artwork in source folder? 2.1.5 is unintentionally picky about that.


Ding! Ding! Ding!

Yup, 1.1mb folder.jpg. Moved it and repaired NP!

I would never have guessed that one.

Hopefully that bug gets squashed.


--------------------
http://forum.dbpoweramp.com/showthread.php?t=21072
Go to the top of the page
+Quote Post
Boiled Beans
post Jun 10 2013, 15:41
Post #186





Group: Members
Posts: 173
Joined: 8-March 08
Member No.: 51870



When ripping a disc with short silent pregaps, AccurateRip says it's ok, but CUETools DB always say some samples differ.
So I try to repair it with CUETools, but nothing happens, and CUETools' output log determines it's accurate on CUETools DB.

Should I be concerned with this or is this normal behaviour? BTW, my CD drive can't read pregaps.

Here is the EAC log of Suzanne Vega's S/T. Note the CUETools DB section of the log says some samples differ.

CODE

Exact Audio Copy V1.0 beta 3 from 29. August 2011

EAC extraction logfile from 2. June 2013, 22:21

Suzanne Vega / Suzanne Vega

Used drive : HL-DT-STDVD-ROM GDR8161B Adapter: 1 ID: 0

Read mode : Burst

Read offset correction : 102
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 : 1024 kBit/s
Quality : High
Add ID3 tag : No
Command line compressor : C:\Program Files\Exact Audio Copy\Flac\flac.exe
Additional command line options : -8 -V -T "ARTIST=%artist%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "COMPOSER=%composer%" -T "TOTALTRACKS=%numtracks%" %source% -o %dest%


TOC of the extracted CD

Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 0:00.32 | 2:50.45 | 32 | 12826
2 | 2:51.02 | 2:36.25 | 12827 | 24551
3 | 5:27.27 | 3:40.23 | 24552 | 41074
4 | 9:07.50 | 3:55.45 | 41075 | 58744
5 | 13:03.20 | 3:48.72 | 58745 | 75916
6 | 16:52.17 | 3:28.03 | 75917 | 91519
7 | 20:20.20 | 3:41.00 | 91520 | 108094
8 | 24:01.20 | 4:51.15 | 108095 | 129934
9 | 28:52.35 | 3:36.70 | 129935 | 146204
10 | 32:29.30 | 3:20.55 | 146205 | 161259


Range status and errors

Selected range

Filename C:\EAC Temp\Suzanne Vega - Suzanne Vega.wav

Peak level 91.2 %
Extraction speed 22.2 X
Copy CRC B55735BF
Copy OK

No errors occurred


AccurateRip summary

Track 1 accurately ripped (confidence 6) [F35EFB10] (AR v1)
Track 2 accurately ripped (confidence 6) [C8D7A41C] (AR v1)
Track 3 accurately ripped (confidence 6) [65350556] (AR v1)
Track 4 accurately ripped (confidence 6) [11E12428] (AR v1)
Track 5 accurately ripped (confidence 6) [2528CCFA] (AR v1)
Track 6 accurately ripped (confidence 6) [B952A494] (AR v1)
Track 7 accurately ripped (confidence 6) [E06BE4DF] (AR v1)
Track 8 accurately ripped (confidence 6) [B199FC80] (AR v1)
Track 9 accurately ripped (confidence 6) [899AD981] (AR v1)
Track 10 accurately ripped (confidence 6) [ADB6953C] (AR v1)

All tracks accurately ripped

End of status report

---- CUETools DB Plugin V2.1.3

[CTDB TOCID: Qg0b_gWtEeWHdK7xH1oZi2f.i_Q-] found, Submit result: discs with pregaps not supported in this protocol version
[e7389015] (359/359) Differs in 10921 samples @00:00:35-00:00:50
You can use CUETools to repair this rip.


==== Log checksum CC54404B0A57187EB1927F0F834AC46826EB66252E7D0629CFAD2C0E56AAA904 ====


So I try to repair it and this is the CUETools log, where after verification, nothing happens (no repair done even though it was selected)
CODE

[CUETools log; Date: 6/6/2013 11:52:45 AM; Version: 2.1.5]
Pregap length 00:00:32.
[CTDB TOCID: Qg0b_gWtEeWHdK7xH1oZi2f.i_Q-] found.
Track | CTDB Status
1 | (7/7) Accurately ripped
2 | (7/7) Accurately ripped
3 | (7/7) Accurately ripped
4 | (7/7) Accurately ripped
5 | (7/7) Accurately ripped
6 | (7/7) Accurately ripped
7 | (7/7) Accurately ripped
8 | (7/7) Accurately ripped
9 | (7/7) Accurately ripped
10 | (7/7) Accurately ripped
[AccurateRip ID: 000cf8f3-0069a54a-7908660a] found.
Track [ CRC | V2 ] Status
01 [f35efb10|526aaef9] (006+000/509) Accurately ripped
02 [c8d7a41c|707d0538] (006+000/510) Accurately ripped
03 [65350556|0e71e2fe] (006+000/513) Accurately ripped
04 [11e12428|93d775d4] (006+000/510) Accurately ripped
05 [2528ccfa|57a1f977] (006+000/508) Accurately ripped
06 [b952a494|8f5c4f83] (006+000/510) Accurately ripped
07 [e06be4df|359e04ca] (006+000/508) Accurately ripped
08 [b199fc80|10e4f764] (006+000/510) Accurately ripped
09 [899ad981|2aca0bbf] (006+000/511) Accurately ripped
10 [adb6953c|42fe7c91] (006+000/506) Accurately ripped
Offsetted by 664:
01 [a65516ad] (005/509) Accurately ripped
02 [f14b992c] (005/510) Accurately ripped
03 [710cf9b7] (005/513) Accurately ripped
04 [4912f162] (005/510) Accurately ripped
05 [7810f2a6] (005/508) Accurately ripped
06 [b47e2297] (005/510) Accurately ripped
07 [c03f9724] (005/508) Accurately ripped
08 [229b4257] (005/510) Accurately ripped
09 [78ace0fb] (005/511) Accurately ripped
10 [de733224] (005/506) Accurately ripped
Offsetted by 1328:
01 [7d991df3] (053/509) Accurately ripped
02 [6292d017] (053/510) Accurately ripped
03 [9378df28] (054/513) Accurately ripped
04 [3ba6ee76] (053/510) Accurately ripped
05 [4a8c9c15] (052/508) Accurately ripped
06 [7c708585] (053/510) Accurately ripped
07 [d03dfc37] (053/508) Accurately ripped
08 [196d23b0] (054/510) Accurately ripped
09 [9480a3da] (053/511) Accurately ripped
10 [d9632cc2] (052/506) Accurately ripped
Offsetted by 1982:
01 [27787140] (043/509) Accurately ripped
02 [cb71f1f9] (043/510) Accurately ripped
03 [f5565a73] (043/513) Accurately ripped
04 [55534188] (043/510) Accurately ripped
05 [6a875136] (043/508) Accurately ripped
06 [ececab74] (043/510) Accurately ripped
07 [0af0849b] (043/508) Accurately ripped
08 [83e17263] (043/510) Accurately ripped
09 [d1fa8789] (043/511) Accurately ripped
10 [04b48f17] (043/506) Accurately ripped

Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 91.1 [B55735BF] [DEF7E937] CRC32
01 70.0 [C5A70BBB] [D07C3176]
02 76.9 [6D8B2C76] [6C946E4B]
03 86.2 [1D5F1DA9] [9F0AACFB]
04 73.9 [7DBF081B] [2B646C08]
05 84.0 [FB88C3B1] [A15421C2]
06 73.1 [B36FEC9C] [5AA1459C]
07 83.1 [ED92E0DA] [BC371C4B]
08 84.6 [C92788E9] [65F4967B]
09 82.4 [30445AB9] [9DD4B33C]
10 91.1 [2BBFDF5D] [09642A81]


Here is another example, a more modern CD, the latest from RHCP. The EAC and CUETools logs are shown below.

CODE

Exact Audio Copy V1.0 beta 3 from 29. August 2011

EAC extraction logfile from 3. June 2013, 12:30

Red Hot Chili Peppers / I'm with You

Used drive : HL-DT-STDVD-ROM GDR8161B Adapter: 1 ID: 0

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

Read offset correction : 102
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 : 1024 kBit/s
Quality : High
Add ID3 tag : No
Command line compressor : C:\Program Files\Exact Audio Copy\Flac\flac.exe
Additional command line options : -8 -V -T "ARTIST=%artist%" -T "ALBUM=%albumtitle%" -T "DATE=%year%" -T "GENRE=%genre%" -T "COMMENT=%comment%" -T "COMPOSER=%composer%" -T "TOTALTRACKS=%numtracks%" %source% -o %dest%


TOC of the extracted CD

Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 0:00.15 | 4:12.32 | 15 | 18946
2 | 4:12.47 | 4:21.46 | 18947 | 38567
3 | 8:34.18 | 5:39.61 | 38568 | 64053
4 | 14:14.04 | 3:51.00 | 64054 | 81378
5 | 18:05.04 | 3:40.61 | 81379 | 97939
6 | 21:45.65 | 3:28.00 | 97940 | 113539
7 | 25:13.65 | 4:43.03 | 113540 | 134767
8 | 29:56.68 | 4:21.65 | 134768 | 154407
9 | 34:18.58 | 3:52.67 | 154408 | 171874
10 | 38:11.50 | 3:33.09 | 171875 | 187858
11 | 41:44.59 | 5:35.67 | 187859 | 213050
12 | 47:20.51 | 4:01.09 | 213051 | 231134
13 | 51:21.60 | 4:22.17 | 231135 | 250801
14 | 55:44.02 | 3:45.40 | 250802 | 267716


Range status and errors

Selected range

Filename C:\EAC Temp\Red Hot Chili Peppers - I'm with You.wav

Peak level 100.0 %
Extraction speed 4.5 X
Range quality 99.9 %
Copy CRC E14194A9
Copy OK

No errors occurred


AccurateRip summary

Track 1 accurately ripped (confidence 51) [1E4C821A] (AR v2)
Track 2 accurately ripped (confidence 51) [DF54E998] (AR v2)
Track 3 accurately ripped (confidence 50) [DD6BA9B1] (AR v2)
Track 4 accurately ripped (confidence 51) [33BF41DB] (AR v2)
Track 5 accurately ripped (confidence 51) [6F3DA516] (AR v2)
Track 6 accurately ripped (confidence 51) [51B6CC56] (AR v2)
Track 7 accurately ripped (confidence 51) [4A5A1A27] (AR v2)
Track 8 accurately ripped (confidence 50) [0D03EF5A] (AR v2)
Track 9 accurately ripped (confidence 51) [6AE09ADB] (AR v2)
Track 10 accurately ripped (confidence 51) [C0E3384A] (AR v2)
Track 11 accurately ripped (confidence 51) [4BF260FF] (AR v2)
Track 12 accurately ripped (confidence 51) [71D84C9C] (AR v2)
Track 13 accurately ripped (confidence 51) [FB76FC8F] (AR v2)
Track 14 accurately ripped (confidence 51) [AB1AD69D] (AR v2)

All tracks accurately ripped

End of status report

---- CUETools DB Plugin V2.1.3

[CTDB TOCID: Z05mxINrbJ8ZVnge2ceC6GJBBec-] found, Submit result: discs with pregaps not supported in this protocol version
[a8d49654] (103/104) Differs in 5708 samples @00:00:20-00:00:25
[5362c05c] (001/104) No match
You can use CUETools to repair this rip.


==== Log checksum 0E8BBE6B99745A38676DA3BD6D4AB014520D71F2D942AA70D452A7F5CF741685 ====


CODE

[CUETools log; Date: 6/6/2013 11:53:15 AM; Version: 2.1.5]
Pregap length 00:00:15.
[CTDB TOCID: Z05mxINrbJ8ZVnge2ceC6GJBBec-] found.
Track | CTDB Status
1 | (16/17) Accurately ripped
2 | (16/17) Accurately ripped
3 | (16/17) Accurately ripped
4 | (16/17) Accurately ripped
5 | (16/17) Accurately ripped
6 | (16/17) Accurately ripped
7 | (16/17) Accurately ripped
8 | (16/17) Accurately ripped
9 | (16/17) Accurately ripped
10 | (16/17) Accurately ripped
11 | (15/17) Accurately ripped
12 | (14/17) Accurately ripped
13 | (15/17) Accurately ripped
14 | (16/17) Accurately ripped
[AccurateRip ID: 001eea4a-0148ae9d-bf0df10e] found.
Track [ CRC | V2 ] Status
01 [b78679fc|1e4c821a] (071+051/242) Accurately ripped
02 [40dac34c|df54e998] (072+051/244) Accurately ripped
03 [d78d5829|dd6ba9b1] (072+050/242) Accurately ripped
04 [ac33068f|33bf41db] (072+051/244) Accurately ripped
05 [d81eed38|6f3da516] (072+051/244) Accurately ripped
06 [96c419f8|51b6cc56] (072+051/244) Accurately ripped
07 [ba674fef|4a5a1a27] (072+051/244) Accurately ripped
08 [7507b370|0d03ef5a] (072+050/243) Accurately ripped
09 [269855ff|6ae09adb] (072+051/244) Accurately ripped
10 [7ad627c7|c0e3384a] (072+051/244) Accurately ripped
11 [b6523423|4bf260ff] (072+051/243) Accurately ripped
12 [4938a7d4|71d84c9c] (071+051/242) Accurately ripped
13 [f986d470|fb76fc8f] (071+051/241) Accurately ripped
14 [6a0c1386|ab1ad69d] (068+051/240) Accurately ripped
Offsetted by -68:
01 [44bd3978] (002/242) Accurately ripped
02 [18d70fdf] (002/244) Accurately ripped
03 [2d3ab6d3] (002/242) Accurately ripped
04 [f84df1c0] (002/244) Accurately ripped
05 [fdbb92a4] (002/244) Accurately ripped
06 [e6c440e7] (002/244) Accurately ripped
07 [58aa65f4] (002/244) Accurately ripped
08 [70d1303a] (002/243) Accurately ripped
09 [3a01940d] (002/244) Accurately ripped
10 [76c84be3] (002/244) Accurately ripped
11 [6963dffd] (002/243) Accurately ripped
12 [53b57709] (002/242) Accurately ripped
13 [197df91b] (002/241) Accurately ripped
14 [1548e44e] (002/240) Accurately ripped
Offsetted by 6:
01 [67644587] (031/242) Accurately ripped
02 [0677fa98] (031/244) Accurately ripped
03 [32faa2b1] (031/242) Accurately ripped
04 [bcad8a85] (031/244) Accurately ripped
05 [d9b1e6d5] (031/244) Accurately ripped
06 [5cf2184b] (031/244) Accurately ripped
07 [5eb0f830] (031/244) Accurately ripped
08 [cc16642a] (031/243) Accurately ripped
09 [7e2be00f] (031/244) Accurately ripped
10 [ac395338] (031/244) Accurately ripped
11 [a84dd667] (031/243) Accurately ripped
12 [9a985450] (031/242) Accurately ripped
13 [14f63347] (031/241) Accurately ripped
14 [108ff469] (031/240) Accurately ripped
Offsetted by 12:
01 [bbca82d3] (039/242) Accurately ripped
02 [e42252dc] (040/244) Accurately ripped
03 [8f47975d] (040/242) Accurately ripped
04 [afef0e7d] (040/244) Accurately ripped
05 [21742c47] (040/244) Accurately ripped
06 [642ec1fc] (040/244) Accurately ripped
07 [dd42452c] (040/244) Accurately ripped
08 [4c9037bc] (040/243) Accurately ripped
09 [d619210d] (040/244) Accurately ripped
10 [805ed9a6] (040/244) Accurately ripped
11 [70a4dab2] (039/243) Accurately ripped
12 [95affb69] (039/242) Accurately ripped
13 [bdd5f004] (038/241) Accurately ripped
14 [b723d551] (039/240) Accurately ripped

Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 100.0 [E14194A9] [3845DFCA] CRC32
01 100.0 [232AE82E] [6C108268]
02 100.0 [C41EDE35] [0C5A877F]
03 100.0 [8C7394E9] [F79D8FCF]
04 100.0 [A601C4D5] [F6E8AB22]
05 100.0 [C1834BBB] [B0902F80]
06 100.0 [BEDA7784] [E044784E]
07 100.0 [965B33F1] [61119B89]
08 100.0 [0D2283E4] [8C793781]
09 100.0 [BAA82B49] [31DE3286]
10 100.0 [FAEAF6F0] [D3A0C125]
11 100.0 [FA306F45] [6B7D36EF]
12 100.0 [5072D66A] [B3D87E5A]
13 100.0 [8B6B13AF] [A3960C93]
14 100.0 [198A6DFA] [ED81A1CC]
Go to the top of the page
+Quote Post
Gregory S. Chudo...
post Jun 10 2013, 15:44
Post #187





Group: Developer
Posts: 698
Joined: 2-October 08
From: Ottawa
Member No.: 59035



"discs with pregaps not supported in this protocol version"

Your rips are ok. You are just using an old version of CTDB EAC plugin.

You can download the new one here: http://www.cuetools.net/wiki/CTDB_EAC_Plugin


--------------------
CUETools 2.1.4
Go to the top of the page
+Quote Post
Boiled Beans
post Jun 10 2013, 15:56
Post #188





Group: Members
Posts: 173
Joined: 8-March 08
Member No.: 51870



QUOTE (Gregory S. Chudov @ Jun 10 2013, 22:44) *
"discs with pregaps not supported in this protocol version"

Your rips are ok. You are just using an old version of CTDB EAC plugin.

You can download the new one here: http://www.cuetools.net/wiki/CTDB_EAC_Plugin


Thanks for the link, I didn't know it was available for download separately. I thought it just came with EAC. laugh.gif
Go to the top of the page
+Quote Post
Eli
post Jul 3 2013, 15:56
Post #189





Group: Members
Posts: 1056
Joined: 16-October 03
Member No.: 9337



Having an odd situation:

CODE

[CUETools log; Date: 7/3/2013 10:34:49 AM; Version: 2.1.5]
[CTDB TOCID: mzwdPKfBtGHL5aUjLD8FvCt7Lq8-] found.
Track | CTDB Status
1 | (3/3) Accurately ripped
2 | (3/3) Accurately ripped
3 | (3/3) Accurately ripped
4 | (3/3) Accurately ripped
5 | (3/3) Accurately ripped
6 | (3/3) Accurately ripped
7 | (3/3) Accurately ripped
8 | (3/3) Accurately ripped
9 | (3/3) Accurately ripped
10 | (3/3) Accurately ripped
11 | (3/3) Accurately ripped
12 | (3/3) Accurately ripped
13 | (3/3) Differs in 1605 samples @06:04:27,06:14:04-06:14:05,06:16:36-06:16:37,06:17:02,06:17:22,06:18:08,06:18:68-06:18:69,06:19:34,06:19:74,06:21:25-06:21:26,06:21:45-06:21:46,06:22:11,06:23:17,06:23:57,06:24:43,06:24:63-06:24:64,06:25:08-06:25:09,06:26:14-06:26:15,06:27:20-06:27:21,06:27:41,06:29:12,06:30:18,06:32:10,06:32:50-06:32:51,06:34:22,06:35:08,06:35:68-06:35:69,06:37:20,06:37:40,06:37:60,06:38:06,06:38:26,06:38:66,06:39:32,06:40:38,06:40:58,06:41:03-06:41:04,06:41:24,06:41:44,06:41:64,06:42:10,06:42:30,06:42:70-06:42:71,06:44:62,06:45:48,06:47:40,06:47:60-06:47:61,06:49:32,06:51:04,06:52:71,06:53:16,06:53:57
[AccurateRip ID: 001add78-010f2411-a40efc0d] found.
Track [ CRC | V2 ] Status
01 [0bf217c9|067165db] (25+03/28) Accurately ripped
02 [796a4f21|aaf4cc9b] (25+03/28) Accurately ripped
03 [700eea07|9ca0f8c7] (25+03/28) Accurately ripped
04 [5038bf10|569e6bdc] (25+03/28) Accurately ripped
05 [17ee826f|046fec78] (25+03/28) Accurately ripped
06 [099116a7|03cbd736] (25+03/28) Accurately ripped
07 [eb01b984|1b60b060] (25+03/28) Accurately ripped
08 [5f7d4d8e|2c1d0bc0] (25+03/28) Accurately ripped
09 [be7c196b|0c80f699] (25+03/28) Accurately ripped
10 [5a968f4c|85b58f1e] (24+03/27) Accurately ripped
11 [d83fb6f7|e6389b96] (25+03/28) Accurately ripped
12 [a95a221b|a63b20cb] (24+03/27) Accurately ripped
13 [9a348df7|a727961a] (00+00/26) No match

Track Peak [ CRC32 ] [W/O NULL]
-- 100.0 [8AA47F2C] [33AFE4A4]
01 100.0 [8A76B48A] [07AF1899]
02 100.0 [CB4302D3] [A795B85D]
03 100.0 [4846CCC0] [CA291DE9]
04 99.9 [EAACE5C5] [6D145D55]
05 100.0 [800E9F13] [3DBCD818]
06 100.0 [62885B5C] [44FECE35]
07 100.0 [DE9C8A49] [3F149FE0]
08 100.0 [5E78D45D] [6DD6D8E7]
09 100.0 [2C14DAC6] [A1FAB7D8]
10 100.0 [F17B60E5] [6FB2ACF5]
11 100.0 [AF5734FC] [741D2828]
12 100.0 [86AE24B2] [67041A35]
13 100.0 [21C22BED] [92D9AC11]


This disc looks like it should be repairable.
However, using 2.1.5, I go through the repair process and I get:

CODE

[CUETools log; Date: 7/3/2013 10:53:23 AM; Version: 2.1.5]
[AccurateRip ID: 001add78-010f2411-a40efc0d] found.
Track [ CRC | V2 ] Status
01 [0bf217c9|067165db] (25+03/28) Accurately ripped
02 [796a4f21|aaf4cc9b] (25+03/28) Accurately ripped
03 [700eea07|9ca0f8c7] (25+03/28) Accurately ripped
04 [5038bf10|569e6bdc] (25+03/28) Accurately ripped
05 [17ee826f|046fec78] (25+03/28) Accurately ripped
06 [099116a7|03cbd736] (25+03/28) Accurately ripped
07 [eb01b984|1b60b060] (25+03/28) Accurately ripped
08 [5f7d4d8e|2c1d0bc0] (25+03/28) Accurately ripped
09 [be7c196b|0c80f699] (25+03/28) Accurately ripped
10 [5a968f4c|85b58f1e] (24+03/27) Accurately ripped
11 [d83fb6f7|e6389b96] (25+03/28) Accurately ripped
12 [a95a221b|a63b20cb] (24+03/27) Accurately ripped
13 [9a348df7|a727961a] (00+00/26) No match

Track Peak [ CRC32 ] [W/O NULL]
-- 100.0 [8AA47F2C] [33AFE4A4]
01 100.0 [8A76B48A] [07AF1899]
02 100.0 [CB4302D3] [A795B85D]
03 100.0 [4846CCC0] [CA291DE9]
04 99.9 [EAACE5C5] [6D145D55]
05 100.0 [800E9F13] [3DBCD818]
06 100.0 [62885B5C] [44FECE35]
07 100.0 [DE9C8A49] [3F149FE0]
08 100.0 [5E78D45D] [6DD6D8E7]
09 100.0 [2C14DAC6] [A1FAB7D8]
10 100.0 [F17B60E5] [6FB2ACF5]
11 100.0 [AF5734FC] [741D2828]
12 100.0 [86AE24B2] [67041A35]
13 100.0 [21C22BED] [92D9AC11]


--------------------
http://forum.dbpoweramp.com/showthread.php?t=21072
Go to the top of the page
+Quote Post
Gregory S. Chudo...
post Jul 3 2013, 15:59
Post #190





Group: Developer
Posts: 698
Joined: 2-October 08
From: Ottawa
Member No.: 59035



Just for this cd, or is repair generally broken in latest 2.1.5?


--------------------
CUETools 2.1.4
Go to the top of the page
+Quote Post
Eli
post Jul 3 2013, 16:01
Post #191





Group: Members
Posts: 1056
Joined: 16-October 03
Member No.: 9337



sorry, for some reason CT had switched from repair mode to encode mode...


--------------------
http://forum.dbpoweramp.com/showthread.php?t=21072
Go to the top of the page
+Quote Post
drfr
post Sep 24 2013, 12:52
Post #192





Group: Members
Posts: 12
Joined: 31-May 10
Member No.: 81034



Donīt know if I understand this log correctly.
CTDBID: what do the lines 4 and 5 with a comma mean? Rips with extra data track, I suppose?
ARID: how to interprete these? All submissions without extra data track?


CODE
[CUETools log; Date: 24. 9. 2013 12:38:54; Version: 2.1.5]
CD-Extra data track length 03:53:62.
[CTDB TOCID: psc7oJ_dm56UJM94MfL1VjlYeDQ-] found.
        [ CTDBID ] Status
        [65ee1459] (20/65) No match
        [6a30aaf3] (06/65) Has no data track, Accurately ripped
        [ef7f65fe] (02/65) Has no data track, No match
        [07899421] (35/65) , Accurately ripped
        [18363f86] (01/65) , No match
        [a83d9063] (01/65) No match
Track | CTDB Status
  1   | (42/65) Accurately ripped
  2   | (42/65) Accurately ripped
  3   | (42/65) Accurately ripped
  4   | (42/65) Accurately ripped
  5   | (42/65) Accurately ripped
  6   | (42/65) Accurately ripped
  7   | (42/65) Accurately ripped
  8   | (42/65) Accurately ripped
  9   | (42/65) Accurately ripped
10   | (42/65) Accurately ripped
11   | (42/65) Accurately ripped
12   | (42/65) Accurately ripped
13   | (42/65) Accurately ripped
14   | (42/65) Accurately ripped
15   | (42/65) Accurately ripped
16   | (42/65) Accurately ripped
17   | (42/65) Accurately ripped
18   | (41/65) Accurately ripped
[AccurateRip ID: 002bbebc-0237a41b-1c0f8c13] found.
Track   [  CRC   |   V2   ] Status
01     [b1c3c382|04b613f2] (000+000/152) No match
02     [fa14ab2d|669b86fd] (000+000/156) No match
03     [406c3308|efa31aeb] (000+000/156) No match
04     [8f884ad0|1c78ae74] (000+000/157) No match
05     [e9911840|61072316] (000+000/155) No match
06     [e6889373|12424fea] (000+000/154) No match
07     [6247eb3e|6f865449] (000+000/156) No match
08     [8b0f1141|17893bfc] (000+000/154) No match
09     [81aa71e9|8c52f988] (000+000/152) No match
10     [857fd4f2|11f7d852] (000+000/153) No match
11     [3263472c|381d6854] (000+000/154) No match
12     [d69566f0|906bbf64] (000+000/153) No match
13     [15cafdcf|c65782ad] (000+000/154) No match
14     [5902383a|740322e7] (000+000/155) No match
15     [2809b5e6|a62f53b9] (000+000/153) No match
16     [24e09729|51974ee5] (000+000/150) No match
17     [04ca1f8d|0ed1e000] (000+000/150) No match
18     [9acfa964|7f3e285f] (000+000/149) No match

Track Peak [ CRC32  ] [W/O NULL]
--   98,7 [8BA73C6D] [2854A0A6]          
01   98,7 [326B9AD4] [AF5D23A1]          
02   98,7 [EDD4F0E7] [A723FB04]          
03   98,7 [08DF454F] [68014E4C]          
04   98,7 [B5E13BE3] [0ADE82AD]          
05   98,7 [D4F6C0EC] [C3562EB0]          
06   98,7 [CAD27194] [DBCA2364]          
07   98,7 [F40D7FA4] [132460B7]          
08   98,7 [AE5A321A] [42BD4153]          
09   98,7 [36DB26F7] [AD622910]          
10   98,7 [5B331A41] [60657964]          
11   83,0 [B2C34CBA] [0AB523FD]          
12   98,7 [7CC3BA94] [81733D93]          
13   98,7 [E65885C1] [22A6551F]          
14   58,2 [4BA11EAA] [E1DED7BE]          
15   98,7 [304B19E2] [9402F6D0]          
16   98,7 [F5B3A86F] [A0F39AD9]          
17   98,7 [674BF278] [FD5B7723]          
18   78,2 [43727891] [E86C78A6]


This post has been edited by drfr: Sep 24 2013, 12:53
Go to the top of the page
+Quote Post
korth
post Sep 24 2013, 14:14
Post #193





Group: Members
Posts: 431
Joined: 13-March 11
Member No.: 88969



QUOTE
CTDBID: what do the lines 4 and 5 with a comma mean? Rips with extra data track, I suppose?

It's a known bug. It should tell you CD-Extra data track length 03:54:17 before the comma.

QUOTE
ARID: how to interprete these? All submissions without extra data track?

The records under this AccurateRip ID included the data track and length. Some reading about AccurateRip ID calculation [link] [link].
A few reasons for the lack of matches could be you have
  • a different release using the same layout that hasn't been submitted to the database.
  • a different pressing with an offset that's out of range of CUETool's cross-pressing 'Offsetted by' listing under this section.
  • manually entered the wrong CD-Extra data track length into CUETools.


This post has been edited by korth: Sep 24 2013, 14:42


--------------------
korth
Go to the top of the page
+Quote Post
drfr
post Sep 30 2013, 07:17
Post #194





Group: Members
Posts: 12
Joined: 31-May 10
Member No.: 81034



QUOTE (korth @ Sep 24 2013, 15:14) *
It should tell you CD-Extra data track length 03:54:17 before the comma.


Thanks, that is a correct track length. How did you know?

This post has been edited by drfr: Sep 30 2013, 07:17
Go to the top of the page
+Quote Post
korth
post Sep 30 2013, 13:29
Post #195





Group: Members
Posts: 431
Joined: 13-March 11
Member No.: 88969



CODE
[CUETools log; Date: 24. 9. 2013 12:38:54; Version: 2.1.5]
CD-Extra data track length 03:53:62.
[CTDB TOCID: psc7oJ_dm56UJM94MfL1VjlYeDQ-] found.
[ CTDBID ] Status
[65ee1459] (20/65) No match
[6a30aaf3] (06/65) Has no data track, Accurately ripped
[ef7f65fe] (02/65) Has no data track, No match
[07899421] (35/65) , Accurately ripped
[18363f86] (01/65) , No match
[a83d9063] (01/65) No match

It was in the database
CUETools Database TOCID: psc7oJ_dm56UJM94MfL1VjlYeDQ-
Click 07899421 or 18363f86 in the CTDB Id column. Look on 2nd page of the Track section.


--------------------
korth
Go to the top of the page
+Quote Post
drfr
post Sep 30 2013, 18:04
Post #196





Group: Members
Posts: 12
Joined: 31-May 10
Member No.: 81034



QUOTE (korth @ Sep 30 2013, 14:29) *


Actually I was looking for a way how to look up a CTDB TOCID in the database, didn īt know it was that easy. Is this documented somewhere? Not in the wiki AFAIK.
Go to the top of the page
+Quote Post
korth
post Sep 30 2013, 20:12
Post #197





Group: Members
Posts: 431
Joined: 13-March 11
Member No.: 88969



The wiki has a link to the database web page. I didn't plan to add documentation of this type to the wiki but I can. I'm so far behind updating pages already though.
Search by 'tocid' using db.cuetools.net/?tocid=
Search by 'artist' (most recent first) using db.cuetools.net/?artist=
Search by 'artist' (most popular first) using db.cuetools.net/top.php?artist=
of course you need to fill in missing data after the '=' such as db.cuetools.net/top.php?artist=adele

This post has been edited by korth: Sep 30 2013, 20:22


--------------------
korth
Go to the top of the page
+Quote Post
ebz777
post Nov 15 2013, 10:29
Post #198





Group: Members
Posts: 5
Joined: 27-November 12
Member No.: 104805



QUOTE (Gregory S. Chudov @ Jan 2 2013, 01:15) *
It doesn't seem very fair - people that would be wasting their CPU cycles to calculate those fingerprints would be helping a completely different category of users to identify random mp3s.

It is not for random mp3s actually. When I buy a compilation and when I rip it, I like to know to which original album releases the tracks correspond. Then I like also to be able to deconstruct that compilation and tag each individual tracks with the meta data of the original album releases, with a high certainty that these are the right albums.

Today I cannot do these if I donít also own the albums, because it is often not possible to find out that information through the compilation liner notes and CUETools DB track CRCs are no help because they are two precise. If tomorrow CUETools DB contained the AcoustID of all tracks, we could determine which tracks we are actually buying and ripping.

It's quite fast to calculate an AcoustID, but I understand that some persons, sensitive to the time their rip takes or to the number of CPU cycles are opposed to calculate and publish them. However this concern could be overcome by providing this calculation as an option. That way, those persons could keep the option disabled. This should not be a problem for the database. It is sufficient after all if for each Disc Id just one person is motivated enough to calculate the AcoustID once in order to have that information available in the database attached to every track.
Go to the top of the page
+Quote Post
bilbo
post Nov 15 2013, 15:27
Post #199





Group: Members
Posts: 190
Joined: 16-April 07
Member No.: 42593



@ebz777

There are already several programs out there that use the MusicBainz database to identify tracks. Picard is one of them. They put the acoustic id in the tags and give you all the tag info. IIRC, MP3Tag also uses MusicBainz for retrieving tags. Have you tried this route? If there are programs that do what you want, why reinvent the wheel here?


--------------------
Glass half full!
Go to the top of the page
+Quote Post
ebz777
post Nov 15 2013, 18:46
Post #200





Group: Members
Posts: 5
Joined: 27-November 12
Member No.: 104805



QUOTE (bilbo @ Nov 15 2013, 15:27) *
@ebz777

There are already several programs out there that use the MusicBainz database to identify tracks. Picard is one of them. They put the acoustic id in the tags and give you all the tag info. IIRC, MP3Tag also uses MusicBainz for retrieving tags. Have you tried this route? If there are programs that do what you want, why reinvent the wheel here?

Iím using MusicBrainz/AcoustID through Picard and Jaikoz. Unfortunately fingerprints in acoustid.org are linked to recordings in MusicBrainz not to Disc IDs. MusicBrainz/AcoustID rely on these current tagging softwares to calculate the fingerprints and associate them to recordings. Since these software work at the track level and not the disc level they have no better option.

And these tagging softwares canít also force any particular workflow. So you end up having users tagging a bunch of mp3ís and polluting the database by associating them with the wrong recordings. In the end itís a useless mess for the purpose I was describing.

Only a special ripping software like Cuetools could calculate a fingerprint for each track and ensure that they are associated together properly with a unique Disc ID.
Go to the top of the page
+Quote Post

9 Pages V  « < 6 7 8 9 >
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 29th August 2014 - 19:58