PlayCD, SB16CD and RippCD (Announce)
> ... but if you read sector by sector
> there is not quarranted that the new stream of data will start exactly one
> byte after previous sector. The laser may be not so accurate.
> So the common technique is to read at least two consequent sectors and to
> look for overlaps.
That sounds quite a bit like pure nonsense. Perhaps the term "jitter correction" isn't exactly hard science?
What I can say: long reads are used, that are 2352 bytes per sector ( 98 frames * 24 bytes ), ignoring the extra sub-channel byte - which is pretty useless for CDDA, since the 96 bits [12 bytes] of subchannel Q (the only one defined by the standard ) give no extra information. Reading error statistics ( which might give some info about the disk quality ) isn't implemented.
---
MS-DOS forever!
Complete thread:
- PlayCD, SB16CD and RippCD - Japheth, 30.07.2026, 07:41 (Announce)
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- PlayCD, SB16CD and RippCD - Laaca, 30.07.2026, 09:50
- PlayCD, SB16CD and RippCD - Japheth, 30.07.2026, 10:06
- PlayCD, SB16CD and RippCD - Laaca, 30.07.2026, 23:39
- PlayCD, SB16CD and RippCD - Japheth, 31.07.2026, 07:45
- PlayCD, SB16CD and RippCD - Laaca, 30.07.2026, 23:39
- PlayCD, SB16CD and RippCD - Japheth, 30.07.2026, 10:06
- PlayCD, SB16CD and RippCD - Laaca, 30.07.2026, 09:50
Mix view