Tweet
Hi,
Thanks for your comments in the last thread - it's frustrating that disc drives sometimes set their own speeds (seemingly at random) while others almost always rip at high speed. But that's not what I'm here for this time. Let me describe my setup - I'm using 2 internal disc drives, and two external, USB disc drives. Of course, I'd like to use all 4 of these at once, but I'm finding problems with hotswitching CDs as other drives rip. I use secure ripping, though it doesn't really matter, this behavior happens with burst also. I'm not using the batch ripper, I'm using 4 open instances of the CD ripper. Here's what happens:
If a drive is finishing ripping a track, it will hang on CPU encoding for about 5 seconds, not start ripping the next track, and sometimes spin down if:
-I insert a CD into a different drive (while it's being identified any CPU encoding hangs)
-I eject a CD (from the moment I press the software eject button or hardware eject, until the drive ejects it)
The problem here is, if I'm constantly ejecting and inserting new discs in 4 different drives, this causes a lot of hanging behavior, and some of my drives will spin down during this brief hang and will not spin back up afterwards, causing rips going at 25x+ to slow down to 4-8x off of one of these. The solution might seem to be that I should load up 4 discs at once, rip them all and then load up 4 more each time. The problem is, my internal drives are significantly faster (not because they're rated better, but because they don't slow themselves down) and are often done much more quickly than my two externals.
Now, I suspect this is a problem relating to how Windows 7 (and likely all iterations) handle disc drives - that while a disc is being read or ejected, certain tasks hang. But has anyone dealt with this problem before and fixed it? I'm starting on a project here (6000+ disc collection to rip) and I'd love to know if there's a way around this problem.
Thanks for your comments in the last thread - it's frustrating that disc drives sometimes set their own speeds (seemingly at random) while others almost always rip at high speed. But that's not what I'm here for this time. Let me describe my setup - I'm using 2 internal disc drives, and two external, USB disc drives. Of course, I'd like to use all 4 of these at once, but I'm finding problems with hotswitching CDs as other drives rip. I use secure ripping, though it doesn't really matter, this behavior happens with burst also. I'm not using the batch ripper, I'm using 4 open instances of the CD ripper. Here's what happens:
If a drive is finishing ripping a track, it will hang on CPU encoding for about 5 seconds, not start ripping the next track, and sometimes spin down if:
-I insert a CD into a different drive (while it's being identified any CPU encoding hangs)
-I eject a CD (from the moment I press the software eject button or hardware eject, until the drive ejects it)
The problem here is, if I'm constantly ejecting and inserting new discs in 4 different drives, this causes a lot of hanging behavior, and some of my drives will spin down during this brief hang and will not spin back up afterwards, causing rips going at 25x+ to slow down to 4-8x off of one of these. The solution might seem to be that I should load up 4 discs at once, rip them all and then load up 4 more each time. The problem is, my internal drives are significantly faster (not because they're rated better, but because they don't slow themselves down) and are often done much more quickly than my two externals.
Now, I suspect this is a problem relating to how Windows 7 (and likely all iterations) handle disc drives - that while a disc is being read or ejected, certain tasks hang. But has anyone dealt with this problem before and fixed it? I'm starting on a project here (6000+ disc collection to rip) and I'd love to know if there's a way around this problem.
Comment