Source: "cdda://0134978A" / index: 1
AccurateRip status: Not accurate - partial matches with offsets: 0(19), 6(38), 122(44).
What does this mean particullarly Not accurate - partial matches with offsets: 0(19), 6(38), 122(44).
This Just means whatever you ripped was ripped using a different drive offset doesn't really mean anything is wrong the only time it matters is if you see CRC mismatch then you have to re rip
ah, ok, ty.
Partial match with offset 0? Doesn't that mean there is something wrong?
Source: "cdda://0134978A" / index: 1
AccurateRip status: Not accurate - partial matches with offsets: 0(19), 6(38), 122(44).
What does this mean particullarly Not accurate - partial matches with offsets: 0(19), 6(38), 122(44).
This Just means whatever you ripped was ripped using a different drive offset doesn't really mean anything is wrong the only time it matters is if you see CRC mismatch then you have to re rip
I had some CRC events today in a few rips. I played those tracks and didnt hear any audibly detected errors. What is CRC actually? I searched through the previous posts with keyword CRC and found no info on what im asking
Errors may be inaudible and still exist. I learned to disregard inaudible errors, even if they are fact. I listen to the music, not "bitperfect rips".
CRC stands for Cyclic Redundancy Check - it's a checksum/hash/fingerprint of a file. Two files are identical if their checksums are the same. CRC mismatch means that others who ripped this CD got in their files different data than you have. However "partial matches" mean that there were people who get exactly yours results, but they used read offsets different than you used. Which may both mean that their or your CD drive is set incorrectly (uses incorrect read offset). Read offset is a correction, counted in samples, that needs to be applied due to fact that none of the CD drives work perfectly and/or they read data in finite blocks, that may not match actual track boundaries - so they read little bit too much or too little, so programs like XLD, EAC or foobar had to correct data stream coming from CD drive.
Errors may be inaudible and still exist. I learned to disregard inaudible errors, even if they are fact. I listen to the music, not "bitperfect rips".
CRC stands for Cyclic Redundancy Check - it's a checksum/hash/fingerprint of a file. Two files are identical if their checksums are the same. CRC mismatch means that others who ripped this CD got in their files different data than you have. However "partial matches" mean that there were people who get exactly yours results, but they used read offsets different than you used. Which may both mean that their or your CD drive is set incorrectly (uses incorrect read offset). Read offset is a correction, counted in samples, that needs to be applied due to fact that none of the CD drives work perfectly and/or they read data in finite blocks, that may not match actual track boundaries - so they read little bit too much or too little, so programs like XLD, EAC or foobar had to correct data stream coming from CD drive.
Ok ty. How do i know if my DVD drive settings are set correctly? My drive settings are as follows...read offset correction 0 and auto, Pipping security Paranoid, Limit drive speed while reading is checked. Rip Actions verify with accurateRip.
Converter setup...FLAC level5, output 24bit, Processing None.
Check your drive offset against this database:
http://www.accuraterip.com/driveoffsets.htm
In case of further problems just use EAC (Exact Audio Copy). This app is intended only for ripping tracks and makes this perfectly.
read offset correction 0 and auto
Should it show 0 for auto? Anyone? (Too lazy to fire up a computer with a CD drive.)
Paranoid, Limit drive speed while reading is checked. Rip Actions verify with accurateRip.
You can consider burst rips first; if it verifies AccurateRip, it should be OK.
Converter setup...FLAC level5, output 24bit, Processing None.
Output 16 bits. There is no more on the CD. (That said, FLAC will detect that there is nothing in the last eight bits, but there is no use in pretending that you got 24.)
I also use FLAC level 8. Takes more time, but encoding is done once and for all, and decoding speed is virtually the same with level 8.
By the way, I use foobar2000 for nearly everything playback-ish, but it would probably only be my fourth choice for CD ripping. (After dBpoweramp, EAC and CUERipper from CUETools - not necessarily in that order. CUETools can also sometimes repair rips.)
ok most things are ok but
Drive offset is almost never 0 hit the auto button next to the 0 to automatically get the required number or use the drive chart here http://www.accuraterip.com/driveoffsets.htm and copy the number in the Correction Offset column
and flac output should nor be 24 it should be auto cds do not use 24 bits set output to auto
also i could have sworn i offered my help before if you have questions I would gladly help
ok most things are ok but
Drive offset is almost never 0 hit the auto button next to the 0 to automatically get the required number or use the drive chart here http://www.accuraterip.com/driveoffsets.htm and copy the number in the Correction Offset column
and flac output should nor be 24 it should be auto cds do not use 24 bits set output to auto
also i could have sworn i offered my help before if you have questions I would gladly help
yes you did offer and i took you up on it, I appreciate it. but i didnt think you wanted to be bothered every time i had a question or problem. I'm new to Fb2K so there are soooo many questions Lol.
no problem anything else let me know