IPB

Welcome Guest ( Log In | Register )

CUETools.. Couple Questions
fuctfuct
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
CODE
[AccurateRip ID: 0011f546-008f3ae0-950aa30a] disk not present in database

The second disc of the same album gets ..
CODE
[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
Replies
korth
post Feb 9 2013, 22:20
Post #2





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



I know you're new to the forum. Please avoid unnecessary full quoting.
QUOTE
Is there something in the flac container its looking at?
CUETools can read the metatags (if any).
QUOTE
I Still think its weird that it's "Accurately ripped (confidence 9)" according to the log but not CUETools
I imagine it's possible the AccuratRip record was somehow lost. If I did my math correctly, the TOC in the EAC LOG you provided calculates out to the same AccurateRip ID: 0011f546-008f3ae0-950aa30a. You can verify that the TOC calculated by CUETools matches the one in the log by setting 'Create TOC files = True'. If you verify the files again, a .TOC file will be created (readable in notepad). The location of the file depends on your settings. If 'In source folder' is checked, the file will be written to the source folder. If not checked, it will be written to the Output location.


--------------------
korth
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: 17th September 2014 - 15:37