Tweet
Re: How to rip thousands of cds?
LtData - I suspect this isn't the case, at least, not in a major way. The batch ripper itself does this, launching multiple cdgrab.exe processes, hidden from view, one per drive.
Manually running the cdgrab.exe's is almost the same but with less automation. You just have to watch to make sure that each cdgrab doesn't start looking at a different (wrong) drive on CD insert/eject, as they are wont to do. Or rather, when one does this, you must manually switching the drive letter back...and you will end up doing this a lot.
If you don't catch it, this can lead to two cdgrab.exe's trying to rip from the same CD drive at the same drive...if you aren't careful before you click the Rip button. That certainly would decrease throughput...
The batch ripper avoids this as it technically runs one cdgrab.exe per *CD*, each one told to exit after a CD finishes ripping, so it doesn't wait around, dejected, cd-less, looking for another CD friend to play with. Also, when the cdgrab.exe launched, the drive is already loaded with a spun up CD and the passed parameters force the cdgrab.exe to look at a specific drive. So, with the batch ripper, there's no chance of the cdgrab.exe getting distracted by other drives.
-brendan
LtData - I suspect this isn't the case, at least, not in a major way. The batch ripper itself does this, launching multiple cdgrab.exe processes, hidden from view, one per drive.
Manually running the cdgrab.exe's is almost the same but with less automation. You just have to watch to make sure that each cdgrab doesn't start looking at a different (wrong) drive on CD insert/eject, as they are wont to do. Or rather, when one does this, you must manually switching the drive letter back...and you will end up doing this a lot.
If you don't catch it, this can lead to two cdgrab.exe's trying to rip from the same CD drive at the same drive...if you aren't careful before you click the Rip button. That certainly would decrease throughput...
The batch ripper avoids this as it technically runs one cdgrab.exe per *CD*, each one told to exit after a CD finishes ripping, so it doesn't wait around, dejected, cd-less, looking for another CD friend to play with. Also, when the cdgrab.exe launched, the drive is already loaded with a spun up CD and the passed parameters force the cdgrab.exe to look at a specific drive. So, with the batch ripper, there's no chance of the cdgrab.exe getting distracted by other drives.
-brendan
Comment