Still waiting for Grigory to chime in for your first question.In the meantime, the config is in %appdata%\CUERipper\settings.txtDefault should be:DetectHDCD=1Wait750FramesForHDCD=1[edit: deleted much of requote]
CUERipper v2.1.4 Copyright (C) 2008-12 Grigory ChudovEAC extraction logfile from 3. July 2012, 10:07Hallows Eve / Tales of TerrorUsed drive : PLEXTOR CD-R PX-W8432T Adapter: 1 ID: 0Read mode : SecureUtilize accurate stream : YesDefeat audio cache : YesMake use of C2 pointers : NoRead offset correction : 355Overread into Lead-In and Lead-Out : NoFill up missing offset samples with silence : YesDelete leading and trailing silent blocks : NoNull samples used in CRC calculations : YesUsed interface : Native Win32 interface for Win NT & 2000Gap handling : Appended to previous track<snip>All tracks accurately rippedNo errors occurredEnd of status report
how to format the generated file names (don't want a period behind %tracknumber%).
I wonder why the working (!) C2 error correction on this drive is not recognized and ... this drive should be able to overread into Lead-In and Lead-Out.
When I open the output folder in Mp3tag then the tag shown is APEv2 (APEv2)
ALAC Input and 'repair' script.
Quote from: korth on 04 July, 2012, 07:07:34 PMALAC Input and 'repair' script.Thanks for reporting this. I made a small bugfix release to address this and 'Detailed log' problem. Didn't bump the version number, just overwrote the same download location.
So v2.1.4 is the new stable version now?
Do u have any plans on adding AccurateRip cross-pressing verification?
You of course meant ARv2 cross-pressing verification? CUETools already has ARv1 cross-pressing verification.I agree it should be added if possible. Perhaps even optional (can be turned on/off) or as a custom script if execution speed is still an issue.
Unhandled Exception: System.TypeLoadException: A type load exception has occurred.[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: A type load exception has occurred.
To be more specific about the problem with the genre: if I put %genre% in the path template it just outputs %genre%
I don't know whether it's relevant, but the metadata CueRipper found for the disc didn't list a genre; I put it in myself.
I ask about the new schema mostly for the ability to list other credited artists. In particular, a lot of my collection is classical music, so it's helpful to be able to list composer, performing group, and conductor.
[CUETools log; Date: 8/22/2012 7:57:01 PM; Version: 2.1.4][CTDB TOCID: hEht88BfBHFLCpTqcVzUc3NxeQM-] found.Track | CTDB Status 1 | (9/9) Accurately ripped 2 | (9/9) Accurately ripped 3 | (9/9) Accurately ripped 4 | (9/9) Accurately ripped 5 | (9/9) Accurately ripped 6 | (9/9) Accurately ripped 7 | (9/9) Accurately ripped 8 | (9/9) Accurately ripped 9 | (9/9) Accurately ripped 10 | (9/9) Accurately ripped 11 | (9/9) Accurately ripped 12 | (9/9) Accurately ripped 13 | (9/9) Accurately ripped 14 | (9/9) Accurately ripped 15 | (9/9) Accurately ripped 16 | (9/9) Accurately ripped 17 | (9/9) Accurately ripped[AccurateRip ID: 002de805-0246d414-f711d611] disk not present in database.Track Peak [ CRC32 ] [W/O NULL] [ LOG ] -- 100.0 [D78D3B12] [E33CA45B] W/O NULL 01 100.0 [5C6B629A] [2CEB2478] 02 100.0 [2143D219] [C1819E6C] 03 99.1 [131CA7DD] [8C89D7FA] 04 100.0 [11C6AFAB] [CDC171C9] 05 100.0 [63CFFACD] [9D25555F] 06 100.0 [E4806D30] [864D8C0F] 07 100.0 [CA68015C] [D2912A94] 08 100.0 [1205D4C4] [FD47E5D7] 09 100.0 [C45DCF3C] [FC743F84] 10 100.0 [E099EADD] [20AB6016] 11 100.0 [5EC526C6] [71A3F021] 12 100.0 [6957FB29] [4F4E0918] 13 100.0 [87E62411] [9108D17B] 14 100.0 [EF7D6B45] [C1037029] 15 100.0 [EF0A712C] [F8651FED] 16 100.0 [CEA38418] [05E7BE21] 17 100.0 [895E1F77] [E4BDFF83]
What does it mean?
Here's my CUETools Log (Verify Mode). What does it mean? Thanks in advance for the answer. Sorry for my bad English.
Quote from: nvrbckdwn on 22 August, 2012, 09:00:46 AMWhat does it mean?Short answer: That your rip is OK. It matches all of the CTDB's nine rips. CUETools finds no AccurateRip submission to compare with. The last section of the log is checksums.
the fact that the rip has 9 submissions in CTDB and none in AR is quite suspicious.