However, there is no additional element of uncertainty like a database without original record checksum.ĬD extractor can begin to read information at maximal speed to save time. This method also doesn't guarantee 100% probability of audio stream integrity. But repeatable audio data reading from CD can cause different content in problematical places.įurther, the obtained data array is analyzed to additional ED. Re-reading from music data buffer have no sense, because there is same information for each re-reading. Re-reading performed several times.īuffering elimination is an attempt of forced cleaning of CD data buffer for each re-reading. Re-reading is repeated reading of CD track's fragment. But, I suppose, it is a matter of older drives. Probably, some drives can't calculate it. One error flag control audio data integrity of 1 byte of the raw audio information. The safe/secure compact disc ripper software may apply additional fault detection and correction algorithm under data, that was before checked and corrected into CD drive. In case of unsuccessful fault elimination, error flag (C2) mark a broken byte. If it is detected, the drive tries to restore music information. So compact disc drive try to detect faults inside. Ripper software's statistics collection by multiple re-readings of your optical disc.ĬD-drive can correct faults and restore (with some probability) valid audio information (Reed–Solomon coding). If a CD ripper (that is used for copying the majority) has a non-fixed bug, the same situation may happen too.Īlso, rare record or different optical disc versions (pressing, mastering?) issues may be there. We can hope (without 100% warranty), that the majority (of similar checksums for some CD in the database) is the same checksum of the CD's original record.īut, in instance, if some CD series was manufactured without 100% identity to original studio files (for unknown to us reasons), then we have non-correct majority. So ripped checksum compared with an array of uncertified checksums. The glass type (ripper software and optical drive) defines how exactly we can detect the ice cube size (byte value on CD) and restore the initial cube size into our box (byte value into ripped file).īut the database doesn't contain original record checksum. We can look at the cubes (bytes on CD) through different glass types (optical drive with CD ripping software). We can't distinguish corner (case 2) and part of the cube (case 1). It happens due to we know nothing about the cube size. If we have a corner instead full cube (unrecovered information), we can't restore the cube (byte) exactly. If the cube (byte) is lost its corner, we can create similar-size cube (restore information in byte) and put it in our box (ripped music file). When we study the cubes (read from CD), we can find 3 types of damaged cubes (wrong bytes): It's like, bytes are damaged in manufacturing or another way.ĬD ripping is like the creation of cubes into our own box (ripped sound files). Some of the cubes may be damaged when put in the box or during delivery. The real process is more sophisticated.Īt a factory, we should put several ice cubes (bytes) in a box (song on CD). Remark: It's only an approximate CD-ripping description. If a CD ripper can't exactly read values of the bytes, written at a recording studio, we get broken sound. If one or several bytes are broken, music can get audible distortions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |