Answers.Body: <p>I'm quoting this from <a href="http://wiki.hydrogenaudio.org/index.php?title=AccurateRip#Drive_read_offsets" rel="nofollow noreferrer">here:</a></p>
  <p>Drive read offsets</p>
  <p>Very few CD drives actually start reading data from audio CDs exactly at the sector requested by DAE software. There are drives that are off by over 1 sector (1/75th of a second), but most are off by much less (1/250 to 1/350 second). Most modern CD drives have &quot;Accurate Stream&quot; technology, so there's no &quot;jitter&quot;, meaning in this case that the variance is consistent from read to read, and will tend to be the same for all drives of a certain make &amp; model.</p>
  <p>The AccurateRip database allows one to find out the read offset, which is normally constant for given make &amp; model of CD drive. This number can then be used by DAE software to ensure that each track is ripped from its exact start to its exact finish.</p>
  <p>The offset is given in samples. One &quot;sample&quot; on an audio CD is 4 bytes, consisting of a 2-byte left-channel value and a 2-byte right-channel value. There are 2352 bytes, or 588 samples, in each sector of an audio CD, corresponding to 1/75th of a second of sound. Therefore, an AccurateRip offset of +134 means the drive consistently delivers data from 536 bytes behind (earlier than) where it was asked to read from, so the DAE software needs to look that far ahead (hence the positive offset) in order to get the right data.</p>
  <p>When offsets are taken into account, the DAE software might have to ask the drive to &quot;overread&quot; into the lead-in or lead-out portions of the disc, where there's no audio data. Some drives can't be asked to do it, some drives will try to do it and fail, and some will just return null samples (a stream of &quot;0&quot; bytes, a.k.a. digital silence).</p>
  <p>If the drive can't overread, then there will be samples missing from the extracted track. The DAE software can correct for this by padding the track with digital silence so it's the correct length.</p>
  <p>Soooooooooooooooooooooooooooooooooo...</p>
  <p>Basically both rips are accurate, since the DAE software should correct the situation</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2012-02-14T15:04:35.477Z
Answers.LastActivityDate: 2012-02-14T15:04:35.477Z
Answers.LastEditDate: 2020-06-17T09:53:03.607Z
Answers.UserDisplayName: Johnny Bigoode
Body: <p>Does anyone know why are there different results in accuraterip database? For example:</p>
  
  <p>When finish with ripping an audio CD, the results might look like:</p>
  
  <pre><code>Track 1 (98/120) Accurately ripped
  Track 2 (98/120) Accurately ripped
  Track 3 (98/120) Accurately ripped
  Track 4 (98/120) Accurately ripped
  Track 5 (98/120) Accurately ripped
  Track 6 (98/120) Accurately ripped
  
  Offsetted by -6
  Track 1 (22/120) Accurately ripped
  Track 2 (22/120) Accurately ripped
  Track 3 (22/120) Accurately ripped
  Track 4 (22/120) Accurately ripped
  Track 5 (22/120) Accurately ripped
  Track 6 (22/120) Accurately ripped
  </code></pre>
  
  <p>What is the offset? are they both correct?</p>
  
Tags: <audio-cd>
Title: Audio cd ripping with AccurateRip
UserDisplayName: Kappri
ThreadText: # Audio cd ripping with AccurateRip
  
  (Asked by: username_0 on 2012-02-14)
  
  Does anyone know why are there different results in accuraterip database? For example:
  
  When finish with ripping an audio CD, the results might look like:
  
  ```
  Track 1 (98/120) Accurately ripped
  Track 2 (98/120) Accurately ripped
  Track 3 (98/120) Accurately ripped
  Track 4 (98/120) Accurately ripped
  Track 5 (98/120) Accurately ripped
  Track 6 (98/120) Accurately ripped
  
  Offsetted by -6
  Track 1 (22/120) Accurately ripped
  Track 2 (22/120) Accurately ripped
  Track 3 (22/120) Accurately ripped
  Track 4 (22/120) Accurately ripped
  Track 5 (22/120) Accurately ripped
  Track 6 (22/120) Accurately ripped
  
  ```
  
  What is the offset? are they both correct?
  
  **Tags:** audio-cd
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2012-02-14. Score: 1 | Accepted answer
  
  I'm quoting this from [here:](http://wiki.hydrogenaudio.org/index.php?title=AccurateRip#Drive_read_offsets)
  
  Drive read offsets
  
  Very few CD drives actually start reading data from audio CDs exactly at the sector requested by DAE software. There are drives that are off by over 1 sector (1/75th of a second), but most are off by much less (1/250 to 1/350 second). Most modern CD drives have "Accurate Stream" technology, so there's no "jitter", meaning in this case that the variance is consistent from read to read, and will tend to be the same for all drives of a certain make & model.
  
  The AccurateRip database allows one to find out the read offset, which is normally constant for given make & model of CD drive. This number can then be used by DAE software to ensure that each track is ripped from its exact start to its exact finish.
  
  The offset is given in samples. One "sample" on an audio CD is 4 bytes, consisting of a 2-byte left-channel value and a 2-byte right-channel value. There are 2352 bytes, or 588 samples, in each sector of an audio CD, corresponding to 1/75th of a second of sound. Therefore, an AccurateRip offset of +134 means the drive consistently delivers data from 536 bytes behind (earlier than) where it was asked to read from, so the DAE software needs to look that far ahead (hence the positive offset) in order to get the right data.
  
  When offsets are taken into account, the DAE software might have to ask the drive to "overread" into the lead-in or lead-out portions of the disc, where there's no audio data. Some drives can't be asked to do it, some drives will try to do it and fail, and some will just return null samples (a stream of "0" bytes, a.k.a. digital silence).
  
  If the drive can't overread, then there will be samples missing from the extracted track. The DAE software can correct for this by padding the track with digital silence so it's the correct length.
  
  Soooooooooooooooooooooooooooooooooo...
  
  Basically both rips are accurate, since the DAE software should correct the situation
  
  
  ---
  
  