"Confidence:1" after _second_ submitted result, yes?

[Spoon]

Re: "Confidence:1" after _second_ submitted result, yes?

Scratches are removed from the database when two people verify the rip, the 3rd scratch result would not make to the database.

[Gew]

Re: "Confidence:1" after _second_ submitted result, yes?

First, thanks for all your answers.

And yes, Spoon has previously stated that AccurateRip database is in fact updated approx. once a month, therefor "..then rip it again tomorrow (or even next week), my initial rip would NOT yet be in the database.." is correct.

I think this cleared it though. When a track (of disc) is ripped for the first time, it gets Confidence:1 instantly (but added to database for search queries first in a month or so).

The only thing I find strange is, assuming there are lots of folks who rip scratched discs and get faulty CRCs; and then submit those, there would be tons of "garbage CRCs" with Confidence:1 of, well, lots of albums/pressings out there. Right? This is why I thought that a track/pressing is getting C:1 first after being "validated" by a second submission. But I take it this is not the case then. Hmm..

Oh, perhaps I got a clue after all.

Look, do you (Spoon) mean that the very first CRC submitter of a Cuesheet-->TrackNo gets added after only single submission, meanwhiles any submission (with different CRC) after this original one requires at least one subsequent validation to get Confidence:1? This would sort of narrow down the number of -- possible -- faulty scratch garbage CRCs to 1 for each pressing, correct?

In short:
A single submission of a new crc (pressing) on a cuesheet (album) is indeed (after ~a month) added with Confidence:1.
Second submission gets Confidence:2, etc, etc..
?

[garym]

Re: "Confidence:1" after _second_ submitted result, yes?

A confidence number of only 1 is not a guarantee of an accurate rip. Unless you have just purchased the disc and are ripping it for the very first time, it is possible that you are comparing with your own previous rip (and not someone else's).

Hmmm, there is quite a delay between ripping a disc, and my OWN results being added to the accuraterip database. For example, if I rip the disk, then rip it again tomorrow (or even next week), my initial rip would NOT yet be in the database. You are correct that if I ripped it, and then a year later I ripped it again, the accruaterip database might only contain my prior rip. For me this is not an issue, because I rip my discs only once (to FLAC) with very rare exceptions.

[eaglescout1998]

Re: "Confidence:1" after _second_ submitted result, yes?

A confidence number of only 1 is not a guarantee of an accurate rip. Unless you have just purchased the disc and are ripping it for the very first time, it is possible that you are comparing with your own previous rip (and not someone else's).

[garym]

Re: "Confidence:1" after _second_ submitted result, yes?

In terms of piece of mind, even the fact that one other user has ripped the CD on a different machine, different drive, different physical CD, and still produced the exact CRCs you are getting in your rip is still a good thing (and better than ripping twice on your own machine and comparing the results).

[Spoon]

Re: "Confidence:1" after _second_ submitted result, yes?

> "Confidence:1" it means that 2 unique users/computers has ripped the track in particular

Not always, if there is only one pressing of a CD then a single submission would be made available.

[Gew]

Hi!

Sorry to bother you guys again.
It's probably in some thread here but I'm so tired, and this is bugging me. I think I have all the pieces to the puzzle. Now, only this. As I've understood it, when there is no AccurateRip record for a track, when the very first user submits it, it doesn't get "confidence:1", due to the high level of uncertainty, plus the fact that all submitted misreads would be "strolling around" the database for no good at all. So, when a user submits a CRC for the first time, it gets sort of "in-pipeline-waiting-for-further-verifications", ie confidence:0.


In short:
When a ripped track gives me "Confidence:1" it means that 2 unique users/computers has ripped the track in particular, with the same checksum result. "Confidence:29" means 30 unique submitts for track, etc, etc, yes?


Like I said, sorry to bother you about this. The more I think about it, it seems like this is the only real answer to the question, cus otherwise it would - like I thought - lots of messy garbage CRC's in AccurateRip. Just need a tiny confirmation on this, hopefully from Spoon, so that I can find inner piece.

Regards~
And bigups for all the good work~