Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cryst]

If you are using secure mode for ripping, is there any reason to not use maximum speed?  Obviously, if you encounter errors, you may need to back it off, but if it comes out OK, it's all good, right?

Then again, couldn't secure mode read the same data the same way more than once, but incorrectly?

[Sauzee]

Interesting point.

Given that it's secure mode it shouldn't matter what speed you choose - you'll end up with the same result.

[cryst]

I figured I'd bump this even though no one seems to know the answer.

[MarSies]

Logically speaking it shouldn't matter for the end result.

Maybe there's a difference in the total amount of time it takes to do the job. This is just a thought:

At maximum speed the system might try to start fast and then has to reduce speed when it encounters errors. This speed change might take some extra time compared to a slow(er) start.

MarSies .....

[cryst]

Thanks for the replies, both.

My thought was that maybe high speeds could induce an error, and that a re-read could reproduce the same error, again due to speed.  I assume this is probably unlikely.

In lieu of input to the contrary from John or Matt, I guess I'll just continue to rip with the setting on 4x (which turns out to be a pretty agonizing ~1.5x on my system for some god-forsaken reason).

[Sauzee]

Given what you have said I don't see why you don't just rip at max.  

Speed of rip is really only going to be relevant if you were using a non-error correcting method.

[Matt]

The secure rip log will always be accurate regardless of the ripping speed you use.  So, there's no compelling reason to reduce the speed unless you have very unique hardware that fails to rip at its highest speed. (and in that case, the secure rip log would let you know that something wasn't working)