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 versions 1.9.5 through 2.1.6 (Read 1889561 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #100
I'm only worrying that soon that options window will be so huge it won't fit on screen

If you are going to add these specialized changes that may rarely be used, maybe you should have them enabled in a config file to keep the options window clean!
Glass half full!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #101
I had the same error as NachoMan77. In my case the CDs resulting in the "Database access error PartialContent" errors for every track were "Reba #1's" both CD 1 and 2. I thought that perhaps the '#' sign in the CD title might be causing a problem. ARCue says that all tracks for both CDs are all accurately ripped.

When I tried TripleFlac, I got the error "Error parsing the DB file, maybe it's corrupt..." in a pop-up window, but the text area says:

Contacting AccurateRip [LeadIn: 0] - http://www.accuraterip.com/accuraterip/F/3...70-080D7F11.bin
HTTP respone: OK - read 1783 bytes from server, contains 10 set(s)

I hope this helps.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #102
This is really cool:

$ mono ArCueDotNet.exe /tmp/Electric\ Light\ Orchestra\ -\ Discovery.flac.cue
[Disc ID: 00162eed-00ca7a8c-a70a3c0c]
Track  [ CRC    ] Status
01    [590412c6] (24/37) Accurately ripped as in pressing(s) #1
02    [b6aaf1ce] (24/39) Accurately ripped as in pressing(s) #1
03    [2ab63e0b] (24/39) Accurately ripped as in pressing(s) #1
04    [ca7539bf] (24/39) Accurately ripped as in pressing(s) #1
05    [f5392440] (24/40) Accurately ripped as in pressing(s) #1
06    [ec015f5b] (24/39) Accurately ripped as in pressing(s) #1
07    [a6d3e102] (24/40) Accurately ripped as in pressing(s) #1
08    [e9066146] (24/39) Accurately ripped as in pressing(s) #1
09    [3327a526] (24/40) Accurately ripped as in pressing(s) #1
10    [0577d3f2] (24/39) Accurately ripped as in pressing(s) #1
11    [941751ca] (24/40) Accurately ripped as in pressing(s) #1
12    [e5ea5616] (21/36) Accurately ripped as in pressing(s) #1
Offsetted by -664:
01    [463a552e] (00/37) No matches
02    [a5069b4e] (02/39) Accurately ripped as in pressing(s) #4
03    [2b39088b] (02/39) Accurately ripped as in pressing(s) #4
04    [d10455c7] (02/39) Accurately ripped as in pressing(s) #4
05    [28ffb5e8] (02/40) Accurately ripped as in pressing(s) #4
06    [5d5512c3] (02/39) Accurately ripped as in pressing(s) #4
07    [b5bfdc2a] (02/40) Accurately ripped as in pressing(s) #4
08    [a84bc556] (02/39) Accurately ripped as in pressing(s) #4
09    [0dd67f7e] (02/40) Accurately ripped as in pressing(s) #4
10    [c58da01a] (02/39) Accurately ripped as in pressing(s) #4
11    [a31e2442] (02/40) Accurately ripped as in pressing(s) #4
12    [894c08fe] (02/36) Accurately ripped as in pressing(s) #4

I believe there's a mkbundle command for mono that will embed all the DLL into a single Linux executable which is probably a good idea, these JIT languages are the software version of Humpty Dumpty in my opinion.

Anyone have a clue on this one?:
$ mono CUETools.exe

** (CUETools.exe:30985): WARNING **: The following assembly referenced from /home/michael/smb/cueTools-192/CUETools.exe could not be loaded:
    Assembly:  System.Windows.Forms    (assemblyref_index=0)
    Version:    2.0.0.0
    Public Key: b77a5c561934e089
The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/home/michael/smb/cueTools-192/).


** (CUETools.exe:30985): WARNING **: Could not load file or assembly 'System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.
File name: 'System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
michael@corwin:~/smb/cueTools-192$

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #103
Just wanted to let people know that the "CUE Tools has encountered a problem and needs to close." messages can be caused by running it over a (in my case Samba) network share. Copy it to the C drive to run it and it will work.

** (CUETools.exe:30985): WARNING **: The following assembly referenced from /home/michael/smb/cueTools-192/CUETools.exe could not be loaded:

Can it be that it's a samba problem again?
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #104

** (CUETools.exe:30985): WARNING **: The following assembly referenced from /home/michael/smb/cueTools-192/CUETools.exe could not be loaded:

Can it be that it's a samba problem again?


I can't accuse you of not being alert! No, that is a regular path, you are correct that the /home/michael/smb path is shared via samba for windows as z:, but I'm on the Linux side of things reading from a plain ext3 mount.

I figured out how to turn the .net CLI utility into a Linux excutable:

mkbundle2 ArCueDotNet.exe CUEToolsLib.dll FLACDotNet.dll WavPackDotNet.dll APEDotNet.dll -o ArCueTools

It works on wav files, and guaranteed to crash on Flac and Ape. I haven't tested Wavepack but I'd be shocked if it didn't crash too. In any case it's like an improved version of ARCue.pl

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #105
Does this make any sense?
Code: [Select]
Black Sabbath - Paranoid.flac: done
[Disc ID: 000d44e3-005781a4-6b09df08]
Track  [ CRC ] Status
 01 [4a3fc0dd] (00/118) No matches
 02 [a9382641] (00/118) No matches
 03 [ebf74add] (00/116) No matches
 04 [f3e09b5e] (00/117) No matches
 05 [388e462b] (00/119) No matches
 06 [b205e57f] (00/117) No matches
 07 [ec94db4d] (00/117) No matches
 08 [5592d775] (00/119) No matches
Offsetted by -2329:
 01 [8580c981] (14/118) Accurately ripped as in pressing(s) #3
 02 [b1ecbe18] (14/118) Accurately ripped as in pressing(s) #3
 03 [2272ffa6] (14/116) Accurately ripped as in pressing(s) #3
 04 [37a0223c] (14/117) Accurately ripped as in pressing(s) #3
 05 [d6ee91f1] (14/119) Accurately ripped as in pressing(s) #3
 06 [89f40115] (14/117) Accurately ripped as in pressing(s) #3
 07 [bdeba42a] (14/117) Accurately ripped as in pressing(s) #3
 08 [82fe2267] (00/119) No matches
Offsetted by -1757:
 01 [05e47e4d] (02/118) Accurately ripped as in pressing(s) #7
 02 [fac056ac] (02/118) Accurately ripped as in pressing(s) #7
 03 [1465de4e] (02/116) Accurately ripped as in pressing(s) #7
 04 [d51ce5bb] (02/117) Accurately ripped as in pressing(s) #7
 05 [c0777d9c] (02/119) Accurately ripped as in pressing(s) #7
 06 [6c90dafa] (02/117) Accurately ripped as in pressing(s) #7
 07 [9a8862fb] (02/117) Accurately ripped as in pressing(s) #7
 08 [b8b779c6] (00/119) No matches
Offsetted by -1665:
 01 [f579acad] (38/118) Accurately ripped as in pressing(s) #2
 02 [bbfa8a70] (37/118) Accurately ripped as in pressing(s) #2
 03 [060b706a] (36/116) Accurately ripped as in pressing(s) #2
 04 [2c3d5cf2] (36/117) Accurately ripped as in pressing(s) #2
 05 [d546b81d] (38/119) Accurately ripped as in pressing(s) #2
 06 [d69ab457] (36/117) Accurately ripped as in pressing(s) #2
 07 [983a88f2] (36/117) Accurately ripped as in pressing(s) #2
 08 [7788ae05] (00/119) No matches
Offsetted by -1010:
 01 [5ab5402a] (06/118) Accurately ripped as in pressing(s) #8
 02 [f80697e6] (06/118) Accurately ripped as in pressing(s) #8
 03 [89f871bd] (06/116) Accurately ripped as in pressing(s) #8
 04 [226b2799] (06/117) Accurately ripped as in pressing(s) #8
 05 [d8041e03] (06/119) Accurately ripped as in pressing(s) #8
 06 [64fee3c7] (06/117) Accurately ripped as in pressing(s) #8
 07 [45b7aa73] (06/117) Accurately ripped as in pressing(s) #8
 08 [9c76b54d] (00/119) No matches
Offsetted by -1008:
 01 [c8eb3075] (20/118) Accurately ripped as in pressing(s) #5
 02 [8cd80858] (21/118) Accurately ripped as in pressing(s) #5
 03 [9e2b9bda] (20/116) Accurately ripped as in pressing(s) #5
 04 [c4474076] (21/117) Accurately ripped as in pressing(s) #5
 05 [b5556d9b] (21/119) Accurately ripped as in pressing(s) #5
 06 [72191509] (21/117) Accurately ripped as in pressing(s) #5
 07 [069262e6] (21/117) Accurately ripped as in pressing(s) #5
 08 [cb790576] (00/119) No matches
Offsetted by -738:
 01 [fd79d20e] (08/118) Accurately ripped as in pressing(s) #1
 02 [a0b20dcc] (08/118) Accurately ripped as in pressing(s) #1
 03 [44bacfd7] (08/116) Accurately ripped as in pressing(s) #1
 04 [a5118088] (08/117) Accurately ripped as in pressing(s) #1
 05 [ca578bdb] (08/119) Accurately ripped as in pressing(s) #1
 06 [1526e2d9] (08/117) Accurately ripped as in pressing(s) #1
 07 [3ebffb8c] (08/117) Accurately ripped as in pressing(s) #1
 08 [4e464aa7] (00/119) No matches
Offsetted by -265:
 01 [b5d7e187] (05/118) Accurately ripped as in pressing(s) #4
 02 [29867165] (05/118) Accurately ripped as in pressing(s) #4
 03 [380c013d] (05/116) Accurately ripped as in pressing(s) #4
 04 [e79b9a92] (05/117) Accurately ripped as in pressing(s) #4
 05 [c687a648] (05/119) Accurately ripped as in pressing(s) #4
 06 [b67a397e] (05/117) Accurately ripped as in pressing(s) #4
 07 [5741e2f4] (05/117) Accurately ripped as in pressing(s) #4
 08 [f8c0d9b8] (05/119) Accurately ripped as in pressing(s) #4
for track 8, where are the missing 114 results?

[!--sizeo:1--][span style=\"font-size:8pt;line-height:100%\"][!--/sizeo--]Moderation: Please use codebox instead of code when posting logs, cues and other long items.[/size]

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #106
Yes, that makes sense.

Where were the missing 114 results?  Your track didn't match them and considering you're talking about the last track, this is really not all that unusual.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #107
Does this make any sense?
Black Sabbath - Paranoid.flac: done
08    [f8c0d9b8] (05/119) Accurately ripped as in pressing(s) #4
for track 8, where are the missing 114 results?


Hard to tell. Most probably there really are two pressings of this disc (if we forget about the pressings which differ only in offset) - e.g. european and us versions, or limited edition of some kind, which have different mixes of the last track - maybe a beep over the f* word or something?  You happen to have authentic, but less popular pressing.

It is also possible, that your pressing is just the most complete - all non-matching pressings have higher negative offsets, which means more data was cut from the end of the disc, which doesn't end on digital silence.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #108
Thanks for the responses to my previous post. I have one more and then I'll try to be quiet. I see the same pattern quite a bit which does look like a bug to me:

Code: [Select]
[Disc ID: 00238fef-01cb0e55-eb0df911]
Track  [ CRC    ] Status
 01    [128ece05] (18/37) Accurately ripped as in pressing(s) #1
 02    [713a3a33] (18/37) Accurately ripped as in pressing(s) #2
 03    [c2fa4daa] (17/36) Accurately ripped as in pressing(s) #2
 04    [df0ba459] (17/36) Accurately ripped as in pressing(s) #2
 05    [702d4208] (18/38) Accurately ripped as in pressing(s) #2
 06    [90bee105] (18/38) Accurately ripped as in pressing(s) #2
 07    [7f53316a] (18/37) Accurately ripped as in pressing(s) #2
 08    [2147ec0b] (17/34) Accurately ripped as in pressing(s) #2
 09    [0c448431] (18/37) Accurately ripped as in pressing(s) #2
 10    [d5fe57da] (18/35) Accurately ripped as in pressing(s) #2
 11    [289a02ad] (18/38) Accurately ripped as in pressing(s) #2
 12    [bca78ec8] (18/35) Accurately ripped as in pressing(s) #2
 13    [353445ae] (18/38) Accurately ripped as in pressing(s) #2
 14    [6250941a] (18/35) Accurately ripped as in pressing(s) #2
 15    [902d41a9] (17/36) Accurately ripped as in pressing(s) #2
 16    [2ec47b5f] (17/37) Accurately ripped as in pressing(s) #2
 17    [acc578c5] (16/35) Accurately ripped as in pressing(s) #1
Offsetted by 1162:
 01    [341c1a9d] (06/37) Accurately ripped as in pressing(s) #3
 02    [1c55188b] (07/37) Accurately ripped as in pressing(s) #1
 03    [33eca4cc] (07/36) Accurately ripped as in pressing(s) #1
 04    [aa247909] (07/36) Accurately ripped as in pressing(s) #1
 05    [17a35430] (07/38) Accurately ripped as in pressing(s) #1
 06    [05fec5c9] (07/38) Accurately ripped as in pressing(s) #1
 07    [ecd2f9b0] (07/37) Accurately ripped as in pressing(s) #1
 08    [7179ec0b] (07/34) Accurately ripped as in pressing(s) #1
 09    [88acbb8b] (07/37) Accurately ripped as in pressing(s) #1
 10    [0809327c] (07/35) Accurately ripped as in pressing(s) #1
 11    [cf5ea50d] (07/38) Accurately ripped as in pressing(s) #1
 12    [e2d18ec8] (05/35) Accurately ripped as in pressing(s) #1
 13    [d42be102] (07/38) Accurately ripped as in pressing(s) #1
 14    [27a89634] (07/35) Accurately ripped as in pressing(s) #1
 15    [1113a8d7] (07/36) Accurately ripped as in pressing(s) #1
 16    [57102c61] (07/37) Accurately ripped as in pressing(s) #1
 17    [24e778c5] (06/35) Accurately ripped as in pressing(s) #3
Offsetted by 1463:
 01    [b82ca849] (13/37) Accurately ripped as in pressing(s) #2
 02    [a219be17] (12/37) Accurately ripped as in pressing(s) #3
 03    [9fd50ea5] (12/36) Accurately ripped as in pressing(s) #3
 04    [a110b021] (12/36) Accurately ripped as in pressing(s) #3
 05    [9c7658e4] (13/38) Accurately ripped as in pressing(s) #3
 06    [2d9ebebb] (13/38) Accurately ripped as in pressing(s) #3
 07    [ed6de82b] (12/37) Accurately ripped as in pressing(s) #3
 08    [ca1aec0b] (10/34) Accurately ripped as in pressing(s) #3
 09    [faa2b760] (12/37) Accurately ripped as in pressing(s) #3
 10    [b0c1fc15] (10/35) Accurately ripped as in pressing(s) #3
 11    [8b8853bd] (13/38) Accurately ripped as in pressing(s) #3
 12    [274e8ec8] (12/35) Accurately ripped as in pressing(s) #3
 13    [58566d7c] (13/38) Accurately ripped as in pressing(s) #3
 14    [8c208a69] (10/35) Accurately ripped as in pressing(s) #3
 15    [1214bd66] (12/36) Accurately ripped as in pressing(s) #3
 16    [72770eaa] (13/37) Accurately ripped as in pressing(s) #3
 17    [034078c5] (13/35) Accurately ripped as in pressing(s) #2

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #109
How would this one be explained? Seems like a rounding error to me.

Code: [Select]
[Disc ID: 0018697f-00f80b89-b00c430d]
Track  [ CRC    ] Status
 01    [7ba570e8] (02/130) Accurately ripped as in pressing(s) #5
 02    [6d4e58f0] (02/128) Accurately ripped as in pressing(s) #5
 03    [08762704] (02/128) Accurately ripped as in pressing(s) #5
 04    [0cb12b93] (02/127) Accurately ripped as in pressing(s) #5
 05    [bbfd421f] (02/128) Accurately ripped as in pressing(s) #5
 06    [7e6ec07f] (02/130) Accurately ripped as in pressing(s) #5
 07    [adcac188] (02/128) Accurately ripped as in pressing(s) #5
 08    [33d4c182] (02/128) Accurately ripped as in pressing(s) #5
 09    [44aebab2] (02/127) Accurately ripped as in pressing(s) #5
 10    [5082a7b1] (02/127) Accurately ripped as in pressing(s) #5
 11    [7ce382a0] (02/125) Accurately ripped as in pressing(s) #5
 12    [52eb8127] (02/125) Accurately ripped as in pressing(s) #5
 13    [44a4affe] (02/125) Accurately ripped as in pressing(s) #5
Offsetted by -1417:
 01    [17a89335] (06/130) Partial match to pressing(s) #6
 02    [3e183147] (06/128) Accurately ripped as in pressing(s) #6
 03    [be29b067] (06/128) Accurately ripped as in pressing(s) #6
 04    [ed8f784e] (06/127) Accurately ripped as in pressing(s) #6
 05    [512077db] (06/128) Accurately ripped as in pressing(s) #6
 06    [26865a5d] (06/130) Accurately ripped as in pressing(s) #6
 07    [e3503627] (06/128) Accurately ripped as in pressing(s) #6
 08    [819e67dc] (00/128) No matches
 09    [d80fd4a8] (00/127) No matches
 10    [ed4df26b] (00/127) No matches
 11    [a8cbda8e] (00/125) No matches
 12    [5d6bf3a1] (00/125) No matches
 13    [e607484b] (00/125) No matches
Offsetted by -1416:
 01    [494c7fe5] (00/130) No matches
 02    [d8125ea3] (00/128) No matches
 03    [919767dc] (00/128) No matches
 04    [3976052b] (00/127) No matches
 05    [de1ea2ff] (00/128) No matches
 06    [733028ef] (00/130) No matches
 07    [517aef40] (00/128) No matches
 08    [270d30d2] (06/128) Accurately ripped as in pressing(s) #6
 09    [3688a4b1] (06/127) Accurately ripped as in pressing(s) #6
 10    [000fc312] (06/127) Accurately ripped as in pressing(s) #6
 11    [19dc4f90] (06/125) Accurately ripped as in pressing(s) #6
 12    [af413977] (06/125) Accurately ripped as in pressing(s) #6
 13    [845b38a6] (06/125) Accurately ripped as in pressing(s) #6
Offsetted by -1051:
 01    [03a500ad] (02/130) Accurately ripped as in pressing(s) #4
 02    [7ec0c413] (02/128) Accurately ripped as in pressing(s) #4
 03    [0505f9ad] (02/128) Accurately ripped as in pressing(s) #4
 04    [712cdc44] (02/127) Accurately ripped as in pressing(s) #4
 05    [e4822553] (02/128) Accurately ripped as in pressing(s) #4
 06    [c14baf19] (02/130) Accurately ripped as in pressing(s) #4
 07    [6464d7e5] (02/128) Accurately ripped as in pressing(s) #4
 08    [0601b790] (00/128) No matches
 09    [5d45e596] (00/127) No matches
 10    [80800c55] (00/127) No matches
 11    [4e53236a] (00/125) No matches
 12    [5c55cb95] (00/125) No matches
 13    [4208ea65] (00/125) No matches
Offsetted by -1050:
 01    [5b18e662] (00/130) No matches
 02    [b96053c6] (00/128) No matches
 03    [d873b122] (00/128) No matches
 04    [bd136921] (00/127) No matches
 05    [71805077] (00/128) No matches
 06    [0df57dab] (00/130) No matches
 07    [d28f90fe] (00/128) No matches
 08    [ab708086] (02/128) Accurately ripped as in pressing(s) #4
 09    [bc2cb610] (02/127) Accurately ripped as in pressing(s) #4
 10    [92d3dc8b] (02/127) Accurately ripped as in pressing(s) #4
 11    [bf63986c] (02/125) Accurately ripped as in pressing(s) #4
 12    [ae2b116b] (02/125) Accurately ripped as in pressing(s) #4
 13    [e05cdac0] (02/125) Accurately ripped as in pressing(s) #4
Offsetted by -753:
 01    [fdcb93f9] (42/130) Partial match to pressing(s) #1
 02    [baa97bc7] (40/128) Accurately ripped as in pressing(s) #1
 03    [22bd87df] (41/128) Accurately ripped as in pressing(s) #1
 04    [cb8cd586] (41/127) Accurately ripped as in pressing(s) #1
 05    [04605d3b] (43/128) Accurately ripped as in pressing(s) #1
 06    [fef6250d] (44/130) Accurately ripped as in pressing(s) #1
 07    [a2204eff] (42/128) Accurately ripped as in pressing(s) #1
 08    [98f7a5ec] (00/128) No matches
 09    [472af8f7] (00/127) No matches
 10    [b808fb54] (00/127) No matches
 11    [eb7b57be] (00/125) No matches
 12    [9e9916b1] (00/125) No matches
 13    [8fbeb453] (00/125) No matches
Offsetted by -752:
 01    [f8c8b890] (00/130) No matches
 02    [907038c4] (00/128) No matches
 03    [f62b3f54] (00/128) No matches
 04    [17736263] (00/127) No matches
 05    [915e885f] (00/128) No matches
 06    [4b9ff39f] (00/130) No matches
 07    [104b0818] (00/128) No matches
 08    [3e666ee2] (41/128) Accurately ripped as in pressing(s) #1
 09    [a5b8c8f9] (41/127) Accurately ripped as in pressing(s) #1
 10    [ca2ccaba] (41/127) Accurately ripped as in pressing(s) #1
 11    [5c8bccc0] (40/125) Accurately ripped as in pressing(s) #1
 12    [f06e5c87] (41/125) Accurately ripped as in pressing(s) #1
 13    [2e12a4ae] (42/125) Accurately ripped as in pressing(s) #1
Offsetted by -475:
 01    [aa7b3f6e] (17/130) Accurately ripped as in pressing(s) #2
 02    [1c8d5b9e] (16/128) Accurately ripped as in pressing(s) #2
 03    [bbe2c0ed] (16/128) Accurately ripped as in pressing(s) #2
 04    [37e9cd84] (16/127) Accurately ripped as in pressing(s) #2
 05    [20633653] (16/128) Accurately ripped as in pressing(s) #2
 06    [3f5c7799] (16/130) Accurately ripped as in pressing(s) #2
 07    [44855025] (16/128) Accurately ripped as in pressing(s) #2
 08    [3f45e110] (16/128) Accurately ripped as in pressing(s) #2
 09    [fea8cb2a] (16/127) Accurately ripped as in pressing(s) #2
 10    [55b7ca99] (16/127) Accurately ripped as in pressing(s) #2
 11    [b35a67ea] (16/125) Accurately ripped as in pressing(s) #2
 12    [7c32ed15] (16/125) Accurately ripped as in pressing(s) #2
 13    [7ee5b725] (17/125) Accurately ripped as in pressing(s) #2
Offsetted by -390:
 01    [d4a59c7e] (61/130) Accurately ripped as in pressing(s) #3
 02    [223b106e] (62/128) Accurately ripped as in pressing(s) #3
 03    [ef50aac6] (61/128) Accurately ripped as in pressing(s) #3
 04    [6b7692e5] (60/127) Accurately ripped as in pressing(s) #3
 05    [f0c78947] (59/128) Accurately ripped as in pressing(s) #3
 06    [b3be0e13] (60/130) Accurately ripped as in pressing(s) #3
 07    [d8b4c572] (60/128) Accurately ripped as in pressing(s) #3
 08    [2d0e9abe] (00/128) No matches
 09    [9817822d] (00/127) No matches
 10    [49386e06] (00/127) No matches
 11    [3dd14194] (00/125) No matches
 12    [a8031d23] (00/125) No matches
 13    [10c4855c] (00/125) No matches
Offsetted by -389:
 01    [e5d269df] (00/130) No matches
 02    [c8a448d9] (00/128) No matches
 03    [c2be623b] (00/128) No matches
 04    [b75d1fc2] (00/127) No matches
 05    [7dc5b46b] (00/128) No matches
 06    [0067dca5] (00/130) No matches
 07    [46df7e8b] (00/128) No matches
 08    [d27d63b4] (61/128) Accurately ripped as in pressing(s) #3
 09    [f6245424] (60/127) Accurately ripped as in pressing(s) #3
 10    [5b1e3cbf] (60/127) Accurately ripped as in pressing(s) #3
 11    [aee1b696] (59/125) Accurately ripped as in pressing(s) #3
 12    [f9d862f9] (58/125) Accurately ripped as in pressing(s) #3
 13    [af1875b7] (56/125) Accurately ripped as in pressing(s) #3

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #110
Well, that's how they are in the database... not sure i can quite explain it, it's more of a question for mr Spoon  It seems to me that when the database is updated, a set of CRCs not necceceraly lands on one pressing. For each track AR database searches for a CRC match, if there is - just increases the count, if there isn't - creates a new pressing or puts it in the first pressing which has zero count for this disc.

So if the first person, who ripped this disc, only ripped the first and the last track, or the other way around - he failed to rip the first and the last track - and the next person had a different pressing, so they got tangled.

As for the second example, there can be no rounding error, because there's no rounding  Everything is computed in integers, nothing is divided. Probably this disc just has two versions, one has that extra sample between the 7th and the 8th track.

That's why for me the only reliable part of AR verification is ACCURATERIPCOUNTALLOFFSETS, i.e. sum of all the matches with all offsetted pressings. ACCURATERIPCOUNTALLOFFSETS should be very high for all tracks in both examples.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #111
I have decided to check up some rips by which did itself by Exact Audio Copy from firm disks. I converting my rips by foobar2000 into flac image with embedded cuesheet. Any has coincided on base accuraterip though broad gulls EAC suggest otherwise. After careful searches I have detected such thing. It appears at converting with parametre "convert to album images with cuesheets or chapters", foobar removes pregaps from cue of an image and the copy of the compressed image turns out not ideal. Somehow it is possible to solve this problem?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #112
I have decided to check up some rips by which did itself by Exact Audio Copy from firm disks. I converting my rips by foobar2000 into flac image with embedded cuesheet. Any has coincided on base accuraterip though broad gulls EAC suggest otherwise. After careful searches I have detected such thing. It appears at converting with parametre "convert to album images with cuesheets or chapters", foobar removes pregaps from cue of an image and the copy of the compressed image turns out not ideal. Somehow it is possible to solve this problem?

Did you keep the logs at least?
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #113
Log created by Exact Audio Copy after ripping:
Code: [Select]
Exact Audio Copy V0.99 prebeta 4 from 23. January 2008

EAC extraction logfile from 13. November 2008, 9:01

Infinite Scale / Sound Sensor

Used drive  : ASUS    DRW-1814BL   Adapter: 1  ID: 0

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

Read offset correction                      : 6
Overread into Lead-In and Lead-Out          : Yes
Fill up missing offset samples with silence : Yes
Delete leading and trailing silent blocks   : No
Null samples used in CRC calculations       : No
Used interface                              : Installed external ASPI interface

Used output format : Internal WAV Routines
Sample format      : 44.100 Hz; 16 Bit; Stereo


TOC of the extracted CD

     Track |   Start  |  Length  | Start sector | End sector
    ---------------------------------------------------------
        1  |  0:00.00 |  6:51.04 |         0    |    30828  
        2  |  6:51.04 |  4:43.62 |     30829    |    52115  
        3  | 11:34.66 |  3:42.38 |     52116    |    68803  
        4  | 15:17.29 |  5:31.05 |     68804    |    93633  
        5  | 20:48.34 |  4:32.00 |     93634    |   114033  
        6  | 25:20.34 |  4:00.64 |    114034    |   132097  


Range status and errors

Selected range

     Filename E:\Infinite Scale - Sound Sensor.wav

     Peak level 99.4 %
     Range quality 99.9 %
     Copy CRC 0A86164B
     Copy OK

No errors occurred


AccurateRip summary

Track  1  accurately ripped (confidence 7)  [CBC5D176]
Track  2  accurately ripped (confidence 7)  [B4CD2CEF]
Track  3  accurately ripped (confidence 7)  [CAD85BCE]
Track  4  accurately ripped (confidence 7)  [1C1CB6B9]
Track  5  accurately ripped (confidence 7)  [2A525140]
Track  6  accurately ripped (confidence 7)  [26CCA201]

All tracks accurately ripped

End of status report

Log created by Cue Tools after verifying ripped wav image:
Code: [Select]
[Disc ID: 00077ffb-0027382b-4406e106]
Track    [ CRC    ] Status
01    [cbc5d176] (07/07) Accurately ripped as in pressing(s) #1
02    [b4cd2cef] (07/07) Accurately ripped as in pressing(s) #1
03    [cad85bce] (07/07) Accurately ripped as in pressing(s) #1
04    [1c1cb6b9] (07/07) Accurately ripped as in pressing(s) #1
05    [2a525140] (07/07) Accurately ripped as in pressing(s) #1
06    [26cca201] (07/07) Accurately ripped as in pressing(s) #1

And Cue Tools log after verifying flac image converted by foobar2000 (flac 1.2.1):
Code: [Select]
[Disc ID: 00077ffb-0027382b-4406e106]
Track    [ CRC    ] Status
01    [aafd8969] (00/07) No matches
02    [79f51a60] (00/07) No matches
03    [871e02e3] (00/07) No matches
04    [6617fc8a] (00/07) No matches
05    [6cdfe457] (00/07) No matches
06    [cc1b094c] (00/07) No matches

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #114
Log created by Exact Audio Copy after ripping:

Very strange. Foobar usualy just looses the disc pregap, which leads to a different disc id, but the CRCs remain the same. Your logs show that the disc id is the same (there was no pregap in the original disc, so there was nothing to loose), but the CRCs are different. I don't understand what's going on. Broken flac encoder? Did you try to bit-compare the tracks? Please also check your converter settings in foobar, make sure that FLAC is configured right: prefered bit depth 16, keep lossless sources at original bit depth, and most importantly, dither: never.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #115
::

"Null samples used in CRC calculations" should be "Yes".

::


CUETools versions 1.9.5 through 2.1.5 (current)

Reply #117
My problem was because I enabled dithering in preferences of foobar2000, now it's ok. Thanks Gregory for solution.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #118
Thanks for this great program. Very handy. After testing this program for a while now, I have a feature request:

I would like a drag and drop system on the Cue sheet creator (or at least that it remembers the last used directory).

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #119
Thanks for this great program. Very handy. After testing this program for a while now, I have a feature request:

I would like a drag and drop system on the Cue sheet creator (or at least that it remembers the last used directory).

Will probably look into it a bit later.

Please, check out the new version and feel free to add some documentation at project's Wiki page.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #120
Quote
I would like a drag and drop system on the Cue sheet creator (or at least that it remembers the last used directory).

Will probably look into it a bit later.


For me is it not necessary any more. This:


Quote
* input can be a directory with audio files and no cue sheet


has made the need for making a cue sheet in a quick way obsolete (at least for me) 

Thanks for all other improvements also!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #121
Gregory,

thanks a lot for the "encode if zero offset" option.

All your hard work in 1.9.3 is really apreciated. I'm gonna test it as soon as I get home.

nitpick: the truncate 4206 samples tooltip text is in russian.

Thanks,

N.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #122
Hmm... Looks like no one else find handling of audio CDs with pre emphased tracks useful.
I think it can be usefull because this info is lost when you spilt a CD image into seperate tracks.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #123
Hi Gregory,

while testing enhanced data track rips I found the following minor issue.

With 1.9.3u1, if you specify a data track length it doesn't add the REM DATATRACKLENGTH tag to the cue file. I know that it uses the log file as default to get the data track length, and even if you had to input manually, the discID gets cached so further AR queries resolve correctly, BUT, I think that the DATATRACKLENGTH should be added anyway, for the following reasons:

1) correct me if i'm wrong, but CUETools can't pick up the data length from previous versions of EAC.

2) A user may change it's computer, thus loosing all the cached info. Then the rip won't verify unless the data track length is manually inputed. Please correct me on this, since I haven't spent much time figuring out how it works.

3) I believe that the CUE sheet is the logical place for all file related info to be. IMHO, if it's a disc attribute, it should live on the cue sheet.


Thanks for all the hard work !

N.

PS: please reconsider adding a file overwrite switch for batch jobs. It can even show a warning when the job starts, so that everybody knows its enabled.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #124
I use this tool since Moitah released it and I would like to thank Gregory for his great approvements.

At now one thing to mention: I use custom format %0\cdimage.cue as naming scheme. If nesessary (by double CDs) I change it to cdimage1.cue or cdimage2.cue.

In CUE Tools 1.9.1 I could also change the name of the resulting WAV file, in recent version its name remains always cdimage.wav.

I think it would be better to have the resulting file (in case of single file+cue) named equal to cue file.

Another question is CUE Sheet Creator: when I click the button and select the folder with audio files nothing happens.