It doesn't submit in Burst mode or when there were suspicious positions with many retries.
It seems that it means that you possibly admit entries to CDTB that might be damaged.
I don't like idea that such non accurate CTDB entries will appear in my .accurip.
I don't understand the logic of being AR(2) dependent if the rip comes from EAC or dbpoweramp & in the same time not dependent of the accuracy at all if the rip comes from cueripper.
Have you stored any additionnal informations that would allow you to re-check the accuracy of these suspicious submissions later ? (& purge them ...)
Sorry but as there are no real FAQ or tutorial for AR & CTDB, the information is splitted everywhere.Even if I am faulty, it is hard to follow all AR & CTDB subtilities. Sorry if I made you waste some time, but it was once again usefull to me to have an "unfriendly" discussion with you
By the way, another reason to trust CUETools submissions less than CUERipper submissions is that there's no way i can find out drive model and ripper version (at least if there's no EAC log).
even as someone suggested, a rip that doesn't pass AR check, but has a log and matches CRCs from that log. I still hesitate whether i should do this or not.
In ideal world CTDB shouldn't depend on AR at all
maybe cuetools / cueripper have grown, or about to grow, to the point of having a dedicated subforum rather than to try to keep questions etc relegated to ever growing threads.
Greg:QuoteIn ideal world CTDB shouldn't depend on AR at allI understand that you trust your own software & that you want to be independent from Spoon.
Logs are too easy to edit to be reliable, this is the exact reason why I delete logs.
The only logs you can trust are your own, & most of the time (if perfect) your own logs are useless to you (except for enhanced CD).
[ CTDBID ] Status [9ee07e8b] (20/20) Has no data track, No match
CD-Extra data track length 02:13:73 - 02:14:72.
Hopefully you have them organized by some other means.
Unfortunately a percentage (around 5% of virtual drive users) set the virtual drive name to a real drive name...
More seriously if this is an old EAC rip of yours without TOC in the log, you can try to manually add the data length in order to find it in the AR database. Try all length between 02:13:73 & 02:14:72, good luck.
Even if very thanksfull to Andree, I am slowly leaving the EAC sect & their log fanatism.
because your TOC says it is an enhanced CD
Quote from: sauvage78 on 27 May, 2010, 05:08:02 PMEven if very thanksfull to Andree, I am slowly leaving the EAC sect & their log fanatism.I totally agree ! Also, EAC has too much options that could f*** up your rip. I'm also VERY thankful to that German guy since we won't be at this point in accurate rip without him, but I think CUERipper is the future