Ty again, so very much!
I think I finally got the entire concept, brick by brick. The way you describe a track's sudden bump from "Track not found in database" (eg. what you refer to as 'conf:0')...
Type: Posts; User: Gew
Ty again, so very much!
I think I finally got the entire concept, brick by brick. The way you describe a track's sudden bump from "Track not found in database" (eg. what you refer to as 'conf:0')...
Ty alot pjc2, very good explanation.
The part about "..(which is why conf:1 is useful and why it gets published).." was indeed developing my perspective. I was just too narrow-headed to see, I...
Please if you have just a few minutes (and have understood what Spoon means) could you please elaborate on the routine at its whole..? 'cuz his one-liners aren't really cutting the deal to me....
Hehe. Well, those examples (see question a+b) were actually just posted to shed some light on how the AR routines really work. To be sure I have accuraterip, I would prolly just re-rip locally and...
I have this CD. I ripped it and got "Could not be verified [CRC], AccurateRip returned [CRC_in_db]" on all tracks. So, I assume that my pressing was simply not in database. Anyways, after ripping all...
So is this obsolute information?
And btw, is confidence:number to be considered always reflect the actual number of submissions, eg. no offset +/- 1 so that initial submission is "hang-loose" and...
Oh, I see.
So..
That would then have been the past behaviour.
Whereas now the (1st) ripped crc would go into raw db with..
I hate inconsistency/paradoxes.
They keep me up sleepless nights etc ;(
Right now this statement (quoted above) is what bugs me. I can't seem to mix it with the fact that each track crc...
Marvelous! I think what made me confuzed earlier was how I read in some thread that "tracks that give C:1 cannot be trusted, since it could pretty much just be your own rip that has entered db". Then...
In short:
Is it -- without exception? -- so that a track is required to have more than one submission to move from raw db to published db?
Aaah. That explains a lot. So, it is also so that ripped track results are never displayed as Confidence:1 (in published database) until they are verified by at least one other (so that given...
Perhaps not completely out in the blue.
Is it so that AccurateRip somehow "remembers" no. 1 & 3 (eg. the fact that they have been submitted one time each), so that they won't have to appear in...
But it is there, somwhere in db, although it doesn't appear. It just waits for a second submitter, right?
However, I've ripped some disc that gave me only "Track ripped OK! [CRC] (Condience:1"....
This will -- seriously -- be the last piece of this -- much neurotic (I know) -- "scenario puzzle" that has been bugging me. Your process rendering above is very good. However, you verified that C:1...
Nice!
So, you could say that, not only that it's not of very high reliability, but tracks you get "Confidence:1" on is always in sort of a "hang-loose state", meaning they could be wiped at...
Okey!
It appears with Confidence:1 then? Or does it somehow go directly from complete db absence to Confidence:2?
Also, just so that I've gotten it right.
Assuming complete blank sheet...
I'm reading the line over and over, trying to visualize the process. I think I may be complicating it to myself. Examples are nice though, so here goes.
I rip a track from a disc, EAC gives me the...
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...
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,...
Hiya!
I've been thinking on AccurateRip a lot lately. So, now, I simply need a boolean (true or false) on the following statement:
The risk of getting a "false positive" on a ripped track (eg....
Thanks for your answers. To avoid being repudiated as a retard, I shall throw in that I'm having some personal issues that I'm taking "workflow-suppressing" medication for. However, yesterday night I...
Aaah, I see.
So, basically, when I've ripped a track and sends AccurateRip an instruction to verify, it will only search its database for matches in discs of correspondent length as the one I've...
True. But just so I'm clear, the track entries in db are still based upon pressings track lenght(s), right? I mean, say track no. 9 on a disc (let's call it "A") are 3:35m long. There would be...
Also, how often is AR db updated? It's not in real-time mode, right? There's some sort of manual phase of confirming all newly-gotten submits?
The reason that I ask is because I ripped a disc that...
Thank you for you answer.
So, only one confidence crc, never several. But any? You mean it's all by random? Or ie. by first confidence match found -- in alphabetical order -- in db?
Copyright © illustrate 2024, All rights reserved