Skip to main content

Topic: CTDB question: Repair function (Read 14652 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • greynol
  • [*][*][*][*][*]
  • Global Moderator
CTDB question: Repair function
Reply #50
Yes, the problem is that an AR1 rip is in fact not accurate if it's your own submission.
The fact that someone submits something to the database and it comes back later as a match means the rip was not accurate?

Well then this is a flaw of CTDB, I thought Greg wouldn't have made this misstake.
No, the mistake was clearly yours.  Unfortunately you seem to be unable to admit it.

Keeping those AR1 rips which may not be accurate is not the behavior I would have expected from CTDB, it only creates noise.
I find this somewhat ironic since there has been a lot of noise in this discussion.
13 February 2016: The world was blessed with the passing of a truly vile and wretched person.

Your eyes cannot hear.

  • sauvage78
  • [*][*][*][*][*]
CTDB question: Repair function
Reply #51
I like the idea I will use AR(2) from now on.

Edit:
Quote
The fact that someone submits something to the database and it comes back later as a match means the rip was not accurate? wacko.gif

well you know nothing except that your submission matches your submission, you don't know if it's accurate.

Quote
Unfortunately you seem to be unable to admit it.

Well I never said I was right so why would I admit that I was wrong ? I used plenty "maybe" "it seems" " "I think" ... I even used "warning" ... I would rather say that you always try to be right & have the last word ... this is a very inquisitive & annoying behavior of yours ... but I get used to it because I usually learn from discussion with you. All I tried to do was to help the topic starter to the best of my knowledge, as imperfect as it might be.

Sorry Skybrowser,
I was asked in pm by Greynol to quit this discussion because I was spreading missinformation. Having already been almost banned by Greynol I know that this means that if I keep answering I will get warned.

I don't want to upset him so I quit.
  • Last Edit: 26 May, 2010, 06:59:35 PM by sauvage78
Rip & Check: EAC Secure [Low/C2]+CUETools [AR Confidence 2+]
Desktop: Flac -4 (for Speed) | CDImage+CUE with F2K
DAP (Android): Opus 128Kbps | Tracks with AIMP
Video: Opus 128Kbps (2.1) | VP10 (2160p60) Asap !!! | Matroska

  • Skybrowser
  • [*][*]
CTDB question: Repair function
Reply #52
Greynol, I wasn't attempting to fabricate any facts. I was merely stating observations and asking questions so that I can learn. It was not my intent to annoy anyone, and I do my best to look up information on my own, but if i don't know where it is..... i don't know where it is.

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
CTDB question: Repair function
Reply #53
My comment wasn't directed at you.  It was at sauvage78 and then Teknojnky (though it seems he's just guilty of not following along very closely).
13 February 2016: The world was blessed with the passing of a truly vile and wretched person.

Your eyes cannot hear.

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
CTDB question: Repair function
Reply #54
well you know nothing except that your submission matches your submission, you don't know if it's accurate.
That's a whole lot different than saying it's not accurate, now isn't it?

Quote
I used plenty "maybe" "it seems" " "I think" ... I even used "warning"
Please don't make me count the number of times you failed to qualify your "facts" as being less than factual.  I would not appear to need to get the last word in if you would stop making stuff up and then presenting it as fact.  Once called out you turn around and blame the developer of making a mistake!

While this probably makes pretty good reading for those on the sidelines, we could have avoided this whole mess if you wouldn't make stuff up with what is practically every new post.
  • Last Edit: 26 May, 2010, 07:19:35 PM by greynol
13 February 2016: The world was blessed with the passing of a truly vile and wretched person.

Your eyes cannot hear.

CTDB question: Repair function
Reply #55
Back to original topic:

Some of the albums I want to repair are showing up in the CTDB but when I attempt to verify them, it says for example " AR: offset 112, rip not accurate (0/116), CTDB: could not be verified ".


Your rip isn't accurate according to AR database. No matter what offset do you apply, it will still be inaccurate, so there's no point in it. It could be repairable with CTDB if there were less errors. Offset doesn't matter for CTDB either.

The log that you quoted shows errors in almost all tracks, that's the reason CTDB can't identify it. As explained in http://db.cuetools.net/about.php, CTDB can fix only up to 40 damaged sectors, and sometimes can fail to fix even 4 damaged sectors.
CUETools 2.1.4