I believe that if you have the ability to correct the errors on a given CD (to minimize size of the DB) it may be possible to address the individual tracks as a subset and correct only those tracks that need to be.
The key question is what to do with the info and how do I address the ones that could not be verified?
I would like to help with this software but I need to be sure that it isn't going to damage my tags or files before I run it again.
I don't see an advanced or write accurate rip tags option in 2.1.1.
One thing that would be really helpful is to have a field in the tag that states if it has been verified or not. There could be several different codes to define the status of the album.
Strangely enough, constantly updating this counter was taking too much of servers resources, so i had to partially disable it. It will update about once per day now.By the way, congratulations everyone on reaching 50k CDs in database!I moved CTDB to a new hosting to prepare for further database growth, and am working on providing musicbrainz NGS metadata via CTDB. Here's an example: http://db.cuetools.net/lookup2.php?toc=32:...z=1&fuzzy=0
Great news everyone: EAC V1.0 beta 2 is out, and it supports plugins. You can download it here: http://www.exactaudiocopy.de/en/index.php/...urces/download/And CTDB plugin here: http://db.cuetools.net/downloads/CUETools.CTDB.EACPlugin.rar
Track 31 accurately ripped (confidence 6) [1278B705] (AR v2)Track 32 accurately ripped (confidence 6)  (AR v2) All tracks accurately rippedEnd of status report---- CUETools DB Plugin V2.1.2[CTDB TOCID: 17ng1NaZY3cpgsNWrDCX5d2xFZM-] found.[98d58d47] (3/3) Differs in 20 samples @37:51:39,58:44:55-58:44:56You can use CUETools to repair this rip.==== Log checksum CC0459D22AA62E8188551B97513046D1FE68D69AD04EEF36AA7B60991B2BB0BE ====
Gregory, would you consider adding support for the CDTOC in meta-data. To many of my discs are not recognized when I try to verify and submit. I have over 5000 securely ripped CDs that I would like to submit to the DB.The TOC is stored in the meta-data per these specs:http://forum.dbpoweramp.com/showthread.php?t=16705