Tweet
Good morning to all. I have a question please I am hoping someone can shed some light on. I bought a re-conditioned copy of Infected Mushroom, Legend of the Black Shawarma, I got accurate rips on all but tracks 1, 5 and 8. I then managed to get a factory sealed copy of the same album, ripped it, and got the same result as before, inaccurate but "Secure" on the same tracks 1,5 and 8. Then I bought an ASUS Zen optical drive, I had been using Apple USB Superdrive until now. So I popped the new disc in to the ASUS to re-rip tracks 1,5 and 8. The ASUS is reported in some forums as being able to recover some data that other drives wont. I got the same result, inaccurate but "Secure" on the same tracks. As a brand new disc out of factory packaging, and the second copy that I have, getting the same rip inaccurate results on the same tracks on different discs and different drives leaves me wondering, what can be wrong? Could it be a "Pressing" issue? Any ideas? Thanks in advance.
-
-
I've not heard of this album. Is it somewhat obscure? I suspect that there are very few AccurateRip matches in the database, and mixed information on tracks 1,5,8. Thus not enough consistency to report Accuraterip match. But if they are secure, and playing them produces no audible problems, I'd say you have a good rip. -
Could be a different pressing in the database, or if the confidences are just 1 then the other persons rip was wrong.Comment
-
heya,
not sure if it's good etiquitte to jump on an existing thread but i think soon i'll be facing the same challenges. as in, got my discogs collection update & am gonna re-rip everything i can. however. i tried a sampling of some of the less common releases and only around 15% came back with accuraterip results. to make it even more interesting is that some music is already almost pure noise, so figuring out if a pop or click is part of it nor not can be a challenge.
since this is my first time using accureaterip tried to find out how it worked, which as i understand is making hash that takes into account the offset & such. it's a neat idea, so i was planning to bypass accuraterip (in a way, will still be autosending back the hashes) and just get me a bunch of drives, rip unknown albums in each drive, compare the hashes. if all match it's verified for me, and depending on the amount of rips that agree i'm sure enough for myself that it's valid.
right now have 11 drives, all in an old school heavy tower to make vibrations a non issue. then they all hook up to a sas expander via external sas to my pc. made sure all drives are different models, but almost all have an offset of +6, so might replace a few.
is this a valid path or is my logic or understanding flawed?
thxComment
-
yes, your logic makes sense. comparing hashes from multiple rips on different drives is sort of a 'poor man's' AccurateRip. AccurateRip is of course much better because it is comparing the hashes of other people ON DIFFERENT DRIVES and DIFFERENT COPIES OF THE CD. But your approach is essentially the next best thing. (although your approach is not much better than SECURE rip with dbpa, where it does multiples passes of the CD when ripping and then compares the hashes and if they match then your rip is SECURE. But your approach is slightly better as you are comparing the hashes on rips of CDs using DIFFERENT drives.Comment
Comment