CUETools versions 1.9.5 through 2.1.4 (current), AccurateRip support & more |
CUETools versions 1.9.5 through 2.1.4 (current), AccurateRip support & more |
 Oct 2 2008, 12:26
Post
#1
|
|
 Group: Developer Posts: 648 Joined: 2-October 08 From: Ottawa Member No.: 59035  |
Please welcome, CUETools v2.1.4. (CUETools download page) or direct link: http://www.cuetools.net/install/CUETools_2.1.4.rar
16.04.2012: CUETools 2.1.4: * CTDB 2.0: now ignoring pregap in parity calculations * CTDB 2.0: popular CDs can have twice larger correction files * CTDB 2.0: confidence values no longer include AccurateRip data * CTDB 2.0: simplified (per-track) verification log * CTDB 2.0: faster verification process with less network traffic * CUERipper: support for some older drives, like PLEXTOR W1210A * CUERipper: support for cover art * CUERipper: main window resizable * CUERipper: real test© mode * CUERipper: options dialog * Tagging: support for release date, release country, disc subtitle, label, catalog number, comment * Local DB: can now refresh folder, removing missing files from database and adding new files. * Codecs: LAME encoder updated to use libmp3lame.dll, which is now included in CUETools download (version 3.98.4) * Various bug fixes 14.06.2011: CUETools 2.1.2: * AccurateRip v2 support (without cross-pressing verification) * EAC CTDB plugin * CTDB now supports musicbrainz Next Generation Schema (NGS) metadata. Old musicbrainz library removed. New musicbrainz NGS metadata can now be used in filename templates, including %discname%, %label%, %releasedate%, %country%, %releasedateandlabel%, %discnumberandname% * CTDB submissions are now based on the same data that was used when verifying, so 'submit' script was removed, and data is submitted after verification, after showing confirmation dialog * CTDB verification is now much faster * Local DB: option to purge records * Local DB: now shown in the same window as folder browser * metadata editing window size is now saved in settings * CUERipper now sends CD barcode and rip quality when submitting * support for wierd CDs with two data tracks before audio IMPORTANT: .NET Framework 2.0 (SP2) required. If you get a "could not load file or assembly" error message for CUETools.Codecs.TTA/APE/WavPack/FLAC, make sure the recent version of Visual C++ 2008 runtime files (x86,x64) is installed. You can always download the latest source code from project's SVN repository at SourceForge. Instructions for svn access can be found here. This post has been edited by Gregory S. Chudov: Apr 17 2012, 03:55 -------------------- CUETools 2.1.4
|
 |
 
|
 |
|
Oct 10 2008, 10:32
Post
#2
|
|
|
troll / ban evasion Group: Banned Posts: 244 Joined: 22-April 08 Member No.: 52991 |
Oh, that's too bad : I have manually splitted hidden tracks in maybe 10 albums over more than 1000, and this seems to be one of them. Apologies ! I have tried rejoining tracks 13 and 14 using foobar, tested again, and the problem remains the same. Maybe I've manually removed the silence between both tracks, so I'd better pick another album.
However, what would be great would be if CUETools could still be able to give an AccurateRip confidence score for tracks 01-12 that have been perfectly ripped...  Ideally it should skip track 14, say that tracks 01-12 are accurate, track 13 isn't (since it has been splitted), and track 14 is unknown for this album.Let's give it another try with "The Eminem Show", with an AR score of 131 a year ago. The good news is that CUETools works.  Now here are the results :CODE [Disc ID: 0037a240-033958f4-f2122a14] Track [ CRC ] Status 01 [4e72a4c7] (200/229) Accurately ripped as in pressing(s) #1 02 [5067c665] (200/231) Accurately ripped as in pressing(s) #2 03 [743e0797] (200/230) Accurately ripped as in pressing(s) #2 04 [6458502e] (200/230) Accurately ripped as in pressing(s) #2 05 [a64967d7] (200/234) Accurately ripped as in pressing(s) #2 06 [51eb46fb] (200/231) Accurately ripped as in pressing(s) #2 07 [8d2df3dc] (200/230) Accurately ripped as in pressing(s) #2 08 [c352fc4e] (200/230) Accurately ripped as in pressing(s) #2 09 [85d7fd90] (200/230) Accurately ripped as in pressing(s) #2 10 [4ad9cfcf] (200/230) Accurately ripped as in pressing(s) #2 11 [deaa2b28] (200/229) Accurately ripped as in pressing(s) #2 12 [c33c9809] (200/228) Accurately ripped as in pressing(s) #2 13 [dc2adb6d] (200/231) Accurately ripped as in pressing(s) #2 14 [a08ecb26] (200/227) Accurately ripped as in pressing(s) #2 15 [6058d3ad] (200/227) Accurately ripped as in pressing(s) #2 16 [3679cc8b] (200/230) Accurately ripped as in pressing(s) #2 17 [de921b13] (200/233) Accurately ripped as in pressing(s) #2 18 [cdf03864] (200/229) Accurately ripped as in pressing(s) #2 19 [182e9e00] (200/227) Accurately ripped as in pressing(s) #2 20 [1472b5f2] (200/228) Accurately ripped as in pressing(s) #1 Offsetted by -1292: 01 [2283a122] (02/229) Accurately ripped as in pressing(s) #7 02 [748b9a16] (03/231) Accurately ripped as in pressing(s) #4 03 [3a302f22] (03/230) Accurately ripped as in pressing(s) #4 04 [fbb556ee] (03/230) Accurately ripped as in pressing(s) #4 05 [4ab21fa9] (03/234) Accurately ripped as in pressing(s) #4 06 [6eaee4a0] (02/231) Accurately ripped as in pressing(s) #7 07 [c499eb91] (03/230) Accurately ripped as in pressing(s) #4 08 [bc923bf3] (03/230) Accurately ripped as in pressing(s) #4 09 [84092bf7] (03/230) Accurately ripped as in pressing(s) #4 10 [69ffc4dc] (03/230) Accurately ripped as in pressing(s) #4 11 [82c7ac88] (03/229) Accurately ripped as in pressing(s) #4 12 [842870f4] (03/228) Accurately ripped as in pressing(s) #4 13 [c35d77a7] (03/231) Accurately ripped as in pressing(s) #4 14 [34039f7d] (03/227) Accurately ripped as in pressing(s) #4 15 [e9637259] (03/227) Accurately ripped as in pressing(s) #4 16 [ceb12b4c] (03/230) Accurately ripped as in pressing(s) #4 17 [60502ae4] (03/233) Accurately ripped as in pressing(s) #4 18 [16d8d257] (03/229) Accurately ripped as in pressing(s) #4 19 [b934d324] (02/227) Accurately ripped as in pressing(s) #4 20 [66cdcc1c] (02/228) Accurately ripped as in pressing(s) #8 Offsetted by -667: 01 [f519d188] (05/229) Accurately ripped as in pressing(s) #3 02 [41146252] (05/231) Accurately ripped as in pressing(s) #5 03 [c9fc9127] (04/230) Accurately ripped as in pressing(s) #6 04 [cb5d04e0] (04/230) Accurately ripped as in pressing(s) #6 05 [9a4f6e7c] (05/234) Accurately ripped as in pressing(s) #5 06 [35a24389] (05/231) Accurately ripped as in pressing(s) #4 07 [02b217ec] (04/230) Accurately ripped as in pressing(s) #6 08 [94f81271] (04/230) Accurately ripped as in pressing(s) #6 09 [958cdce8] (04/230) Accurately ripped as in pressing(s) #6 10 [47cb5cbf] (05/230) Accurately ripped as in pressing(s) #5 11 [2dc2b084] (04/229) Accurately ripped as in pressing(s) #6 12 [8410aceb] (03/228) Accurately ripped as in pressing(s) #6 13 [fb401505] (04/231) Accurately ripped as in pressing(s) #6 14 [e38bf06e] (04/227) Accurately ripped as in pressing(s) #5 15 [366e1bb3] (04/227) Accurately ripped as in pressing(s) #5 16 [44c2823a] (03/230) Accurately ripped as in pressing(s) #6 17 [2e26ab5f] (04/233) Accurately ripped as in pressing(s) #6 18 [a290ace0] (04/229) Accurately ripped as in pressing(s) #6 19 [eff146b7] (04/227) Accurately ripped as in pressing(s) #7 20 [0083aa32] (04/228) Accurately ripped as in pressing(s) #6 Offsetted by -649: 01 [4f5f41ac] (02/229) Accurately ripped as in pressing(s) #8 02 [197ea526] (02/231) Accurately ripped as in pressing(s) #8 03 [bea615d7] (02/230) Accurately ripped as in pressing(s) #8 04 [a846eab4] (02/230) Accurately ripped as in pressing(s) #8 05 [83d32d84] (02/234) Accurately ripped as in pressing(s) #8 06 [c8c2430d] (02/231) Accurately ripped as in pressing(s) #8 07 [b3a571ba] (02/230) Accurately ripped as in pressing(s) #8 08 [57352b0d] (02/230) Accurately ripped as in pressing(s) #8 09 [62e23292] (02/230) Accurately ripped as in pressing(s) #8 10 [495fbab0] (02/230) Accurately ripped as in pressing(s) #8 11 [5243aba8] (02/229) Accurately ripped as in pressing(s) #8 12 [f36e39d1] (02/228) Accurately ripped as in pressing(s) #8 13 [20f36626] (02/231) Accurately ripped as in pressing(s) #8 14 [da74e8d9] (02/227) Accurately ripped as in pressing(s) #7 15 [c4da15bb] (02/227) Accurately ripped as in pressing(s) #7 16 [1e00f9c6] (02/230) Accurately ripped as in pressing(s) #8 17 [f496b548] (02/233) Accurately ripped as in pressing(s) #8 18 [3b62ba40] (02/229) Accurately ripped as in pressing(s) #8 19 [7bd1fc66] (02/227) Accurately ripped as in pressing(s) #9 20 [6e60667f] (02/228) Accurately ripped as in pressing(s) #9 Offsetted by -646: 01 [0e792b20] (08/229) Accurately ripped as in pressing(s) #2 02 [6fa42e5d] (08/231) Accurately ripped as in pressing(s) #3 03 [1ccb28d1] (08/230) Accurately ripped as in pressing(s) #3 04 [c919bdc0] (08/230) Accurately ripped as in pressing(s) #3 05 [80567094] (08/234) Accurately ripped as in pressing(s) #3 06 [38cda00b] (08/231) Accurately ripped as in pressing(s) #3 07 [4fd11505] (08/230) Accurately ripped as in pressing(s) #3 08 [f794af27] (08/230) Accurately ripped as in pressing(s) #3 09 [dea7732b] (08/230) Accurately ripped as in pressing(s) #3 10 [82266a65] (07/230) Accurately ripped as in pressing(s) #3 11 [30436600] (07/229) Accurately ripped as in pressing(s) #3 12 [eccef0d0] (07/228) Accurately ripped as in pressing(s) #3 13 [20934d20] (08/231) Accurately ripped as in pressing(s) #3 14 [e531d34e] (08/227) Accurately ripped as in pressing(s) #3 15 [d93100dd] (08/227) Accurately ripped as in pressing(s) #3 16 [e7fc0e4f] (08/230) Accurately ripped as in pressing(s) #3 17 [9ffe1eec] (08/233) Accurately ripped as in pressing(s) #3 18 [06cf2f55] (07/229) Accurately ripped as in pressing(s) #3 19 [fc46b55b] (07/227) Accurately ripped as in pressing(s) #3 20 [d54c073b] (08/228) Accurately ripped as in pressing(s) #2 Offsetted by -6: 01 [3edb878e] (04/229) Accurately ripped as in pressing(s) #5 02 [75f100e6] (03/231) Accurately ripped as in pressing(s) #7 03 [8ab2054e] (03/230) Accurately ripped as in pressing(s) #7 04 [14e58fcc] (03/230) Accurately ripped as in pressing(s) #7 05 [7f7fdf2b] (03/234) Accurately ripped as in pressing(s) #7 06 [3007a36e] (03/231) Accurately ripped as in pressing(s) #6 07 [6422e15b] (03/230) Accurately ripped as in pressing(s) #7 08 [eee6b1e6] (03/230) Accurately ripped as in pressing(s) #7 09 [67264ec9] (03/230) Accurately ripped as in pressing(s) #7 10 [615600f2] (03/230) Accurately ripped as in pressing(s) #7 11 [5489d199] (03/229) Accurately ripped as in pressing(s) #7 12 [54b78349] (03/228) Accurately ripped as in pressing(s) #7 13 [0e07c10c] (03/231) Accurately ripped as in pressing(s) #7 14 [67225b15] (03/227) Accurately ripped as in pressing(s) #6 15 [573e8824] (03/227) Accurately ripped as in pressing(s) #6 16 [5d764362] (03/230) Accurately ripped as in pressing(s) #7 17 [91274e2d] (03/233) Accurately ripped as in pressing(s) #7 18 [210ea414] (03/229) Accurately ripped as in pressing(s) #7 19 [de49a93c] (03/227) Accurately ripped as in pressing(s) #8 20 [ddd6f7a9] (03/228) Accurately ripped as in pressing(s) #7 Offsetted by 6: 01 [287a0269] (04/229) Accurately ripped as in pressing(s) #6 02 [bf762232] (06/231) Accurately ripped as in pressing(s) #1 03 [b5e2f1e2] (06/230) Accurately ripped as in pressing(s) #1 04 [b11510f1] (06/230) Accurately ripped as in pressing(s) #1 05 [ceb49c26] (07/234) Accurately ripped as in pressing(s) #1 06 [57c9ad9d] (07/231) Accurately ripped as in pressing(s) #1 07 [dc195675] (06/230) Accurately ripped as in pressing(s) #1 08 [6bb00e8c] (06/230) Accurately ripped as in pressing(s) #1 09 [d712cbd5] (06/230) Accurately ripped as in pressing(s) #1 10 [57b131bc] (06/230) Accurately ripped as in pressing(s) #1 11 [ab12c627] (06/229) Accurately ripped as in pressing(s) #1 12 [7ab1d63f] (06/228) Accurately ripped as in pressing(s) #1 13 [43e9ba7a] (07/231) Accurately ripped as in pressing(s) #1 14 [41eca653] (07/227) Accurately ripped as in pressing(s) #1 15 [946d2300] (07/227) Accurately ripped as in pressing(s) #1 16 [6043b398] (07/230) Accurately ripped as in pressing(s) #1 17 [1cdab6df] (07/233) Accurately ripped as in pressing(s) #1 18 [cafa20fd] (06/229) Accurately ripped as in pressing(s) #1 19 [34923213] (03/227) Accurately ripped as in pressing(s) #5 20 [9985a391] (00/228) No matches However, forgive me but I'm not sure to understand the results. E.g. : "01 [4e72a4c7] (200/229) Accurately ripped as in pressing(s) #1" - What does the "200/229" mean ? - What does the "#1" mean ? And one last thing : how can we make the results to be written directly into the file tags ? (e.g. one tag for the CRC, one tag for the "200/229", one tag for the "Accurately ripped as in pressing(s) #1", and so on... Thank you again Gregory for this promising software.  Moderation: Code changed to codebox (again). This post has been edited by greynol: Oct 14 2008, 03:32 |
|
|
|
|
Oct 10 2008, 11:14
Post
#3
|
|
|
Group: Developer Posts: 648 Joined: 2-October 08 From: Ottawa Member No.: 59035 |
QUOTE (foorious @ Oct 10 2008, 12:32)  However, what would be great would be if CUETools could still be able to give an AccurateRip confidence score for tracks 01-12 that have been perfectly ripped... Ideally it should skip track 14, say that tracks 01-12 are accurate, track 13 isn't (since it has been splitted), and track 14 is unknown for this album.Unfortunately, this is impossible. You have to know the id of the disk to be able to compare it to the database, and diskId depends on the number and length of the tracks. So if you split a track, cut out silence - there's no way to tell which disk it is that you have. This post has been edited by Gregory S. Chudov: Oct 10 2008, 11:15 -------------------- CUETools 2.1.4
|
|
|
|
|
Oct 16 2008, 19:14
Post
#4
|
|
 Group: Members Posts: 1468 Joined: 30-November 06 Member No.: 38207 |
QUOTE (Gregory S. Chudov @ Oct 10 2008, 12:14) QUOTE (foorious @ Oct 10 2008, 12:32) However, what would be great would be if CUETools could still be able to give an AccurateRip confidence score for tracks 01-12 that have been perfectly ripped... Ideally it should skip track 14, say that tracks 01-12 are accurate, track 13 isn't (since it has been splitted), and track 14 is unknown for this album.Unfortunately, this is impossible. You have to know the id of the disk to be able to compare it to the database, and diskId depends on the number and length of the tracks. So if you split a track, cut out silence - there's no way to tell which disk it is that you have. Oh well, it might be: (1) If you use one-folder-per-album and the files are tagged with original tracknumber, then they may be concatenated to a single file and cue sheet generated. Since AccurateRip is tracks based, it would of course be much easier to scan folder for .flac (or .ape or whatever), extract from the metadata the information you would usually extract from the cue sheet, and contact the AR base. Even if there is no tracknumber tag (they sometimes appear as "4/14" or just "4"), it should be easy to specify a en extraction of number from a filename pattern, like implemented in some tag-from-filename features. So if one track is split into two files, what you need is to have a Totaltracks tag equal to the original total tracks of the CD. With 14 enumerated files of an original Totaltracks=13, the "fourteenth file" could be track 1 split in 1&2, 2 split in 2&3 etc., 13 possibilities. If you encounter such a folder, prompt the user to specify which files to join. (Are there other uses for the Totaltracks tag? Will an audio player object if you add a file with Tracknumber = 14 and Totaltracks = 13?) (2) dBpoweramp writes the AccurateRipDiscID as a Vorbis comment in my flac files. Don't know about other file formats though. -------------------- geocities.com/hydrogenaudio: http://goo.gl/tqYZj
|
|
|
|
|
Oct 16 2008, 20:47
Post
#5
|
|
|
Group: Developer Posts: 648 Joined: 2-October 08 From: Ottawa Member No.: 59035 |
QUOTE (Porcus @ Oct 16 2008, 21:14) (1) If you use one-folder-per-album and the files are tagged with original tracknumber, then they may be concatenated to a single file and cue sheet generated. Since AccurateRip is tracks based, it would of course be much easier to scan folder for .flac (or .ape or whatever), extract from the metadata the information you would usually extract from the cue sheet, and contact the AR base. Even if there is no tracknumber tag (they sometimes appear as "4/14" or just "4"), it should be easy to specify a en extraction of number from a filename pattern, like implemented in some tag-from-filename features. So if one track is split into two files, what you need is to have a Totaltracks tag equal to the original total tracks of the CD. With 14 enumerated files of an original Totaltracks=13, the "fourteenth file" could be track 1 split in 1&2, 2 split in 2&3 etc., 13 possibilities. If you encounter such a folder, prompt the user to specify which files to join. (Are there other uses for the Totaltracks tag? Will an audio player object if you add a file with Tracknumber = 14 and Totaltracks = 13?) (2) dBpoweramp writes the AccurateRipDiscID as a Vorbis comment in my flac files. Don't know about other file formats though. (1) Thanks for interstring thoughts on the matter. There are no other uses for totaltracks, but this tag is often absent. Luckily enough, total number of tracks can be also extracted from cddb DISCID tag. But i'm still quite pessimistic about the possibility of recovering an album structure, when tracks were split. Ok, we can sacrifice that split track and focus on verifying other tracks, but for that we have to know for sure it's length. And it will not be a sum of it's parts in most cases. The silent gaps would most probably be left out - for example, in the mentioned case the track was split because in contained a 'hidden' track. 'Hidden' means there was probably some lengthy silence before it, and i doubt that people would keep that silent gap when editing the track. And even if they did, most audio software would not try to preserve CD sector boundaries when splitting - it would be split in arbitary point, and padded for encoding. Summarising, i doubt any such algorithm would be able to verify the majority of disc images after such treatment. And most people don't do such things to their rips, so i'm probably not going to invest too much time in further studies of this problem. (2) Oops. I didn't know that. CueTools uses "ACCURATERIPID" tag. I guess i'll have to rename it to make it compatible. Is "AccurateRipDiscID" the exact name of the tag? This post has been edited by Gregory S. Chudov: Oct 16 2008, 20:49 -------------------- CUETools 2.1.4
|
|
|
|
|
Oct 17 2008, 01:06
Post
#6
|
|
|
Group: Members Posts: 1468 Joined: 30-November 06 Member No.: 38207 |
QUOTE (Gregory S. Chudov @ Oct 16 2008, 21:47) (2) Oops. I didn't know that. CueTools uses "ACCURATERIPID" tag. I guess i'll have to rename it to make it compatible. Is "AccurateRipDiscID" the exact name of the tag? Yep: dBpoweramp provides tags like the following (cut and pasted from metaflac output of two tracks from two different CDs): AccurateRipResult=AccurateRip: Not in database Secure: Yes [3B3B1D60] AccurateRipDiscID=002-0000bd74-0001fa28-0901b202-1 (track 1 of 2) AccurateRipDiscID=018-0034a011-02b34812-18120f12-15 AccurateRipResult=AccurateRip: Accurate (confidence 10) [BFD8DBAE] (track 15 of 18). As for (1), it is of course more important to have an application working for those of us who use one-file-per-track than for user-created splits. This post has been edited by Porcus: Oct 17 2008, 01:07 -------------------- geocities.com/hydrogenaudio: http://goo.gl/tqYZj
|
|
|
|
|
Oct 20 2008, 06:42
Post
#7
|
|
|
Group: Developer Posts: 648 Joined: 2-October 08 From: Ottawa Member No.: 59035 |
QUOTE (Porcus @ Oct 17 2008, 03:06) AccurateRipDiscID=018-0034a011-02b34812-18120f12-15 AccurateRipResult=AccurateRip: Accurate (confidence 10) [BFD8DBAE] (track 15 of 18). That's wierd. So dbpoweramp puts the track number and total number of tracks in this tag. I was thinking it's not neccecary, because the total number of tracks is stored in this ID anyway - in the last byte of cddb-id part. But in this case the cddb-id part shows there were 12 tracks: 018-0034a011-02b34812-18120f12-15 And dbpoweramp says there's 18. What could this mean? Is this a two-disc release, with 6 tracks on disc 1 and 12 tracks on disc two? This post has been edited by Gregory S. Chudov: Oct 20 2008, 06:43 -------------------- CUETools 2.1.4
|
|
|
|
Gregory S. Chudov CUETools versions 1.9.5 through 2.1.4 (current) Oct 2 2008, 12:26
Fandango WAV output is greyed out<edit>
Ah I didn... Oct 3 2008, 17:11
Gregory S. Chudov QUOTE (Fandango @ Oct 3 2008, 19:11) WAV ... Oct 4 2008, 02:48 Fandango QUOTE (Gregory S. Chudov @ Oct 4 2008, 03... Oct 4 2008, 14:53 foorious QUOTE (Gregory S. Chudov @ Oct 3 2008, 19... Oct 5 2008, 21:58 No Fun Strange...
Can it be that CUE Tools cannot find ri... Oct 6 2008, 00:53 Gregory S. Chudov QUOTE (No Fun @ Oct 6 2008, 02:53) Strang... Oct 6 2008, 15:40 No Fun QUOTE (Gregory S. Chudov @ Oct 6 2008, 18... Oct 7 2008, 00:15 Gregory S. Chudov QUOTE (No Fun @ Oct 7 2008, 02:15) So why... Oct 7 2008, 23:10 No Fun QUOTE (Gregory S. Chudov @ Oct 8 2008, 02... Oct 8 2008, 00:32 foorious Hi, Gregory sent me to this thread from this one :... Oct 3 2008, 18:17 Gregory S. Chudov I encountered some very strange logs:
CODE[Dis... Oct 4 2008, 22:53 No Fun Gregory S. Chudov
Thanks for nice new features... Oct 4 2008, 23:49 Raiden This is a great tool! I'm using it to batc... Oct 5 2008, 00:34 Gregory S. Chudov QUOTE (Raiden @ Oct 5 2008, 02:34) This i... Oct 5 2008, 14:57 Raiden It now says (excerpt):
CODE 19 [8c2ca83c... Oct 5 2008, 20:39 greynol Maybe 1501 is beyond the window being used. The A... Oct 7 2008, 04:12 No Fun QUOTE (greynol @ Oct 7 2008, 07:12) Maybe... Oct 7 2008, 07:07 Moitah It should be able to find offsets within +/- 2939.... Oct 7 2008, 05:48 Gregory S. Chudov QUOTE (greynol @ Oct 7 2008, 06:12) The l... Oct 7 2008, 18:25 Gregory S. Chudov QUOTE (Moitah @ Oct 7 2008, 07:48) By the... Oct 7 2008, 19:51 Gregory S. Chudov Well, in this case there is no bug. Either your co... Oct 8 2008, 01:47 No Fun QUOTE (Gregory S. Chudov @ Oct 8 2008, 04... Oct 8 2008, 08:58 foorious QUOTE (No Fun @ Oct 8 2008, 01:58) Creati... Oct 8 2008, 14:49 yury_usa Ok, how is this possible, then?
CODEEAC extractio... Oct 14 2008, 03:25 greynol QUOTE (yury_usa @ Oct 13 2008, 19:25) Now... Oct 14 2008, 03:29 Gregory S. Chudov QUOTE (No Fun @ Oct 8 2008, 10:58) Maybe ... Oct 9 2008, 20:35 greynol QUOTE (Gregory S. Chudov @ Oct 7 2008, 17... Oct 8 2008, 16:04 Gregory S. Chudov QUOTE (greynol @ Oct 8 2008, 18:04) QUOTE... Oct 8 2008, 17:00 NachoMan77 Hi Gregory !
thanks a lot for jumpstarting CU... Oct 8 2008, 13:56 spoon Correct AR has 2 CRCs one for the track, the other... Oct 8 2008, 16:31 Moitah @spoon: Is there a way to query the AccurateRip da... Oct 8 2008, 17:34 foorious I think I have the same problem as "No Fun... Oct 10 2008, 01:24 Gregory S. Chudov QUOTE (foorious @ Oct 10 2008, 03:24) Gre... Oct 10 2008, 11:00 Moitah @foorious: I checked freedb/Amazon and it looks l... Oct 10 2008, 04:01 foorious QUOTE (Gregory S. Chudov @ Oct 10 2008, 04... Oct 10 2008, 12:57 Gregory S. Chudov QUOTE (foorious @ Oct 10 2008, 14:57) I d... Oct 10 2008, 13:31 Porcus QUOTE (Gregory S. Chudov @ Oct 20 2008, 07... Oct 20 2008, 10:38 Gregory S. Chudov QUOTE (Porcus @ Oct 20 2008, 12:38) First... Oct 20 2008, 11:44 Porcus QUOTE (Gregory S. Chudov @ Oct 20 2008, 12... Oct 20 2008, 15:17 NachoMan77 Gregory,
I can't make the "encode if % o... Oct 11 2008, 00:29 Gregory S. Chudov QUOTE (NachoMan77 @ Oct 11 2008, 02:29) G... Oct 11 2008, 12:39 Gregory S. Chudov QUOTE (NachoMan77 @ Oct 11 2008, 02:29) W... Oct 12 2008, 15:29 NachoMan77 QUOTE (Gregory S. Chudov @ Oct 12 2008, 08... Oct 12 2008, 16:33 Alex B Thank you for the excellent new CUEtools features.... Oct 11 2008, 13:06 yury_usa Question:
Original Log
CODEExact Audio Copy V0.99... Oct 11 2008, 22:59 Fandango QUOTE (yury_usa @ Oct 11 2008, 23:59) How... Oct 11 2008, 23:41 yury_usa Fandango
So this pressing is different by an offse... Oct 12 2008, 00:42 Fandango QUOTE (yury_usa @ Oct 12 2008, 01:42) Fan... Oct 12 2008, 00:45 Alex B I created a mockup to demonstrate my suggestion:
... Oct 12 2008, 15:54 Moitah I thought this was pretty cool, it runs fine with ... Oct 12 2008, 19:47 Gregory S. Chudov QUOTE (Moitah @ Oct 12 2008, 21:47) I tho... Oct 12 2008, 23:32 NachoMan77 QUOTE (Gregory S. Chudov @ Oct 12 2008, 16... Oct 12 2008, 23:45 Corwin QUOTE (Moitah @ Oct 12 2008, 10:47) I tho... Oct 19 2008, 11:45 Gregory S. Chudov Update: some bugs were fixed, fresher build can be... Oct 13 2008, 05:03 Alex B QUOTE (Gregory S. Chudov @ Oct 13 2008, 07... Oct 13 2008, 16:39 NachoMan77 Gregory, when converting from single APE to single... Oct 13 2008, 12:30 Gregory S. Chudov QUOTE (NachoMan77 @ Oct 13 2008, 14:30) G... Oct 13 2008, 13:51 NachoMan77 Also I see that you're embedding the LOG file ... Oct 13 2008, 12:54 Caleb Hey,
Great job on a great utility!
Does th... Oct 13 2008, 14:54 Gregory S. Chudov QUOTE (Caleb @ Oct 13 2008, 16:54) Hey,
... Oct 13 2008, 17:42 Alex B I converted a "tagged APE disc image + CUE... Oct 13 2008, 15:18 Gregory S. Chudov QUOTE (Alex B @ Oct 13 2008, 17:18) I con... Oct 13 2008, 17:23 yury_usa Would it be possible to generate AccurateRip repor... Oct 14 2008, 18:47 Gregory S. Chudov QUOTE (yury_usa @ Oct 14 2008, 20:47) Wou... Oct 14 2008, 19:30 naturfreak Thanks for this useful tool.
A small feature requ... Oct 14 2008, 22:07 NachoMan77 Gregory,
Update5 is working fine. Got a couple of... Oct 15 2008, 06:06 Gregory S. Chudov QUOTE (NachoMan77 @ Oct 15 2008, 08:06) 1... Oct 16 2008, 21:30 Caleb QUOTE (Gregory S. Chudov @ Oct 13 2008, 18... Oct 15 2008, 09:58 Gregory S. Chudov QUOTE (Caleb @ Oct 15 2008, 11:58) Hi Gre... Oct 17 2008, 19:13 NachoMan77 Hi Gregory !
here's my report on Update 6... Oct 18 2008, 01:43 NachoMan77 QUOTE (NachoMan77 @ Oct 17 2008, 18:43) H... Oct 19 2008, 00:29 Gregory S. Chudov QUOTE (NachoMan77 @ Oct 19 2008, 02:29) O... Oct 19 2008, 03:02 Porcus Feature request: duplicates detection. For "d... Oct 18 2008, 15:20 Corwin Just wanted to let people know that the "CUE ... Oct 19 2008, 09:41 Corwin Accurite rip reports the offset is wrong. I found ... Oct 19 2008, 09:53 Gregory S. Chudov QUOTE (Corwin @ Oct 19 2008, 11:53) Accur... Oct 19 2008, 12:44 Caleb QUOTE (Gregory S. Chudov @ Oct 17 2008, 20... Oct 19 2008, 12:28 Gregory S. Chudov QUOTE (Caleb @ Oct 19 2008, 14:28) I trie... Oct 19 2008, 14:02 mhudson7 I love this tool! Thanks to everybody for the... Oct 19 2008, 16:43 Corwin QUOTE (Caleb @ Oct 19 2008, 03:28) Well I... Oct 20 2008, 08:25 Gregory S. Chudov QUOTE (Caleb @ Oct 19 2008, 14:28) I trie... Oct 22 2008, 12:55 NachoMan77 Gregory,
I can confirm that Update7 is now workin... Oct 19 2008, 14:50 fredhammersmith I have a question: can CueTools process hi-rez fil... Oct 19 2008, 15:34 Moitah @Corwin: I will see about posting a WAV-only build... Oct 19 2008, 19:09 NightOwl Moitah and Gregory, thank you so much for CUE Tool... Oct 22 2008, 21:56 NightOwl I started using the latest Update 8 (after replaci... Oct 23 2008, 01:03 Gregory S. Chudov QUOTE (NightOwl @ Oct 23 2008, 03:03) I s... Oct 23 2008, 08:13 NightOwl OK, thanks for the explanation, Gregory. The toolt... Oct 23 2008, 17:15 Moitah IMHO even if the modified times are preserved, wri... Oct 23 2008, 19:12 NachoMan77 QUOTE (Moitah @ Oct 23 2008, 12:12) IMHO ... Oct 23 2008, 21:20 NachoMan77 Gregory,
while using the "Verify, then encod... Oct 25 2008, 21:14 Gregory S. Chudov QUOTE (NachoMan77 @ Oct 25 2008, 23:14) G... Oct 26 2008, 09:31 NachoMan77 QUOTE (Gregory S. Chudov @ Oct 26 2008, 02... Oct 26 2008, 14:32 |
|
Lo-Fi Version | Time is now: 23rd May 2013 - 01:19 |
