Hi - really niche situation so really appreciate advice of Spoon or Pioneer PureRead drive users. I have dBmpower 16.1.
I have Pioneer BDR-S09J-X drive with PureRead 3 feature.
My understanding is PureRead is designed to accurately rip via their firmware & solid anti-vibration hardware.
My primary goal is to achieve bit by bit perfect rip and time taken is low priority. Error correction is OK as long as my primary goal is met i.e. interpolation/approximated correction is a big no. I want to also make sure PureRead and setting on dBmpower Ripping Method options don't conflict.
Questions:
-Should I choose Ripping Method = BURST or will SECURE still achieve bit by bit accuracy with error recovery?
-No harm in turning ON all AccurateRip options?
-Drive Read Cache - if test/detection shows I can set them, better to set or better not use them?
-I only see Maximum or X40 speed choices; no way of getting something in between for lower RPM rip?
Side comment - unconfirmed but I have a feeling this PureRead drives implement C2 Error Pointers at firmware level. Could be wrong.
Many thanks in advance.
NoMusicNoLife
I have Pioneer BDR-S09J-X drive with PureRead 3 feature.
My understanding is PureRead is designed to accurately rip via their firmware & solid anti-vibration hardware.
My primary goal is to achieve bit by bit perfect rip and time taken is low priority. Error correction is OK as long as my primary goal is met i.e. interpolation/approximated correction is a big no. I want to also make sure PureRead and setting on dBmpower Ripping Method options don't conflict.
Questions:
-Should I choose Ripping Method = BURST or will SECURE still achieve bit by bit accuracy with error recovery?
-No harm in turning ON all AccurateRip options?
-Drive Read Cache - if test/detection shows I can set them, better to set or better not use them?
-I only see Maximum or X40 speed choices; no way of getting something in between for lower RPM rip?
Side comment - unconfirmed but I have a feeling this PureRead drives implement C2 Error Pointers at firmware level. Could be wrong.
Many thanks in advance.
NoMusicNoLife
Comment