burst ripping = not mark track as error if insecure

[kiko]

Hi guys,

I just wanna know if:

1) Burst ripping is exactly the same as not checking the option "Mark Track As Error If Insecure" when an insecure rip has occured using Secure ripping?

2) Does Burst ripping use C2 error pointers?

3) Is there an interpolation happening in Burst ripping mode? If there is, is it from the drive itself or from dbpoweramp?

Thanks!

[Spoon]

Re: burst ripping = not mark track as error if insecure

1) No, secure tries to recover the data
2) No
3) Not from dbpoweramp (almost certainly yes from the drive if modern).

[kiko]

Re: burst ripping = not mark track as error if insecure

1) No, secure tries to recover the data
2) No
3) Not from dbpoweramp (almost certainly yes from the drive if modern).

1) What if secure ripping wasn't able to recover the data and ripped it anyway (cause "mark track as error if insecure" is unchecked) isn't the resulting file the same as when you just burst rip it?

[Spoon]

Re: burst ripping = not mark track as error if insecure

When a track has errors it typically has many errors, so in these cases the secure rip would have data recovered that a burst rip could not (even if the secure rip its self has error(s))

[kiko]

Re: burst ripping = not mark track as error if insecure

When a track has errors it typically has many errors, so in these cases the secure rip would have data recovered that a burst rip could not (even if the secure rip its self has error(s))

I see. So secure ripping is really the way to go. Thank you very much!!!:teufel8: