Welcome Guest ( Log In | Register )

CUETools.. Couple Questions
post Feb 9 2013, 02:53
Post #1

Group: Members
Posts: 4
Joined: 11-May 07
Member No.: 43390

I recently discovered CUETools and decided to use it to verify a bunch of my old flac rips with AccurateRip. Seems to work great! So here is my first question..

The flac file names in most of these rips have been changed. They no longer match what is in the log and cue files. CUETools doesn't seem to mind at all. Works just fine... How is this possible? lol blink.gif. Not that im complaining. Im just really curious.

Question number two is...

I decided to try verifying a rip that already says ''Accurately ripped (confidence 9) [00D29D78] (AR v2)'' in the EAC log. However, when i run it though CUETools it says
[AccurateRip ID: 0011f546-008f3ae0-950aa30a] disk not present in database

The second disc of the same album gets ..
[AccurateRip ID: 0012977b-008905ae-7c0cae09] found.
Track   [  CRC   |   V2   ] Status
01     [c891f0fe|8a93a5cc] (13+09/22) Accurately ripped
02     [e45513dc|724fb581] (13+09/22) Accurately ripped
03     [0fcc2d63|8bdfdc70] (12+09/21) Accurately ripped
04     [0af943ec|9e9bcfb8] (12+09/21) Accurately ripped
05     [8bb8e016|0ccec669] (12+09/21) Accurately ripped
06     [437724b8|aab180eb] (12+09/21) Accurately ripped
07     [7dcf3c26|ae215ef7] (12+09/21) Accurately ripped
08     [ddba29dc|ca322744] (12+09/21) Accurately ripped
09     [544cda94|1e81f404] (12+09/21) Accurately ripped

Whats happening here? unsure.gif

Thanks for any help you can provide smile.gif

This post has been edited by fuctfuct: Feb 9 2013, 03:04
Go to the top of the page
+Quote Post
Start new topic
post Feb 9 2013, 15:49
Post #2

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

development thread.

CUETools behaves differently depending on input.
  • IF you selected the CUE file for input, CUETools would have attempted to use the 'correct filenames' feature internally to find the files then used the CUE+EAC LOG1+file lengths to check AccurateRip. If unable to use the CUE, CUETools would have thrown an 'unable to locate audio files' error message.
  • IF you selected the audio files for input, CUETools would have ignored the CUE and EAC LOG files and just used the file lengths to check AccurateRip.
  • IF you selected the folder2 for input, CUETools would have attempted to use the CUE and EAC LOG files first, then use only the file lengths to check AccurateRip.
1 If present. If the EAC LOG file was misnamed or there was more than one, a popup window would appear to let you select the correct EAC LOG file.
2 Selecting the whole folder for input is a 'batch' mode (as is any Multiselect or Drag'n'drop). For best results in 'batch' modes, all file names should be correct in the CUE file and the EAC LOG file should have the same name as the CUE (CDImage.CUE, CDImage.LOG). Popup windows are disabled. CUETools will first attempt to process the CUE and EAC LOG files. IF unsucessful, it will move on to using just the file lengths to check AccurateRip.

CDs in the AccurateRip database are identified by disc structure information located in TOC of the CD. If your LOG file contains a TOC section, this shows the original CD structure. If the first track doesn't start at zero, this indicates a disc PREGAP. If there are more tracks shown than audio tracks on the disc, this indicates the presence of a DATA track. Depending on what Input was used above and how CUETools reacted to that Input, information gathered was used to create a TOC structure of that Input. That TOC structure was then used to contact AccurateRip. If it differs from the original TOC structure, the disc isn't found.

This post has been edited by korth: Feb 9 2013, 16:31

Go to the top of the page
+Quote Post

Posts in this topic

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: 27th November 2015 - 04:06