Re: Dfference in Confidence
Yup. Look at the track lengths and the location of the "bad" frame in every example. Interesting, is it not?
Looks like with that drive connected via IDE and not constrained to 8KB reads (or whatever constraint the effective default is for USB), dbpoweramp is reporting that the final frame in the read buffer of each of those problem tracks sometimes contains C2 pointer flags which indicate potential errors, even though it's likely they are due to a firmware or software issue somewhere in the chain. It happens repeatably in the same place too.
Or potentially even garbled audio data? I can't recall of the larger frame size with C2 flags has the flags before or after the audio data. If before, it's more possible the audio data could be corrupted.
Is it the drive? Maybe.
Constraining the read size to 8KB seems to work around the issue, whether it's a drive, interface, OS or ripper issue. So, I recommend you do that.
Brendan
Yup. Look at the track lengths and the location of the "bad" frame in every example. Interesting, is it not?
Looks like with that drive connected via IDE and not constrained to 8KB reads (or whatever constraint the effective default is for USB), dbpoweramp is reporting that the final frame in the read buffer of each of those problem tracks sometimes contains C2 pointer flags which indicate potential errors, even though it's likely they are due to a firmware or software issue somewhere in the chain. It happens repeatably in the same place too.
Or potentially even garbled audio data? I can't recall of the larger frame size with C2 flags has the flags before or after the audio data. If before, it's more possible the audio data could be corrupted.
Is it the drive? Maybe.
Constraining the read size to 8KB seems to work around the issue, whether it's a drive, interface, OS or ripper issue. So, I recommend you do that.
Brendan
Comment