I initially thought this program screwed up some my tracks cover art. I've discovered it has deleted my tags. Not on all my files but mostly 1-3 tracks on an album and up to 10 on a given album. Out of 29,000 plus tracks I have to repopulate over 3,500 tracks. Thankfully, I use JRiver Media Center and all the info is stored in an independent database. Because of the cover art problem I have to album by album. This is not good.

USE THIS SOFTWARE WITH GREAT CAUTION!!!!

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. It would also be nice if there was a report or log generated after a run with everything organized by Category (see previous post) and artist. At that point I can at least update my database files to indicate all those that are accurate. This program has tremendous potential. It might be nice if the tags themselves could be updated to indicate that they have been verified by creating a field within the tags.

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.

You mean without reencoding the rest of the tracks? In theory that could be done, but i don't think that it would be a very important feature.But you will still need to read all the other tracks to be able to use the recovery record.

It was suggested several times to make per-track recovery records, but that's impractical, because the size of the database would be multiplied by the number of tracks. Smaller recovery records won't work. And if we could afford to have tens of terabytes of data in the database, i'd prefer to use this space for larger whole-disc recovery records.

The key question is what to do with the info and how do I address the ones that could not be verified?

AccurateRip: disk not present in database, will not submit.There are two possibilities here:1) When a popular CD that should be in AR isn't found, that means that CUETools wasn't able to determine AR disc id, because of the missing pregap or changed order of tracks. Most likely that's because you didn't keep the cue sheet.There's no general way to fix it. To avoid this problem in the future, you should preserve the cue sheet.2) CD is ok but not yet in AR database.You can either wait for it to appear there and resubmit with CUETools, or use a ripper which can submit directly to CTDB without AR verification.

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.

CUETools doesn't modify tags by default. And nothing like this have happened before.You either have turned on the option "Write AccurateRip tags" on verify in advanced settings, or it wasn't CUETools that ate your tags.If you did turn on this option, and it did screw up your tags, please send me a sample file for which this happens.

I have selected verify from the drop down menu. Under action I selected verify and submit. Mode all three are checked. I am using flac files. I don't see an advanced or write accurate rip tags option in 2.1.1.

I have been repairing all my tags from JRiver Media Center where all the tag info is stored independently. I assume I can send you info to the address listed on your website. It will take me awhile to sort through my file to see what hasn't been fixed. I think the only thing left is cover art problems.

I am willing to do some testing on a smaller scale. When I first ran this I used a few artist and then ran it on my whole rock database of 2200+ CD's. 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.

Advanced settings are opened when you click a gray cogwheel button in the top-left corner. If you didn't change those settings, then by default tag writing should be off and CUETools just couldn't have eaten your tags.

QUOTE (tunetyme @ Apr 27 2011, 19:52)

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.

CUETools saves this info in it's local database, which is a better way IMHO than modifying the files.

Speaking of resources, I recently discovered CTDB and decided to check all my rips against AR/CTDB then submit all [AR-reported] error-free ones to CTDB... (that was about ~1000 new discs in a row, ouch). I noticed afterwards that the uploading step failed for about ~5 rips (they did not appear online at db.cuetools.net). Had to do a new submission and it worked. Server overload?

Thanks. Most probably it was caused by me doing some maintainance and development in the background. But it could be server overload.I guess i will have to set up a dedicated server at some point. The good thing about VDS is that it's cheap

Great news But what are we supposed to do with this CTDB plugin?For instance I extracted the archive contents to my main Cuetools directory (overwriting files from a fresh 2.1.1), yet when verifying any file I get the error message: Exception: Method not found : 'Void CUETools.CTDB.CUEToolsDB.ContactDB(System.String)'

If you had trouble accessing the database for the past hour, that's because i was moving it to a new hosting. CUETools DB is now hosted on Amazon Cloud Services. Database runs on EC2 instance, and parity files are stored in S3. This should guarantee fast access and practically zero downtime.

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.

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.