Hi all,
I have a system with 1 BD and two DVD drives. I have a batch script running that works pretty well and allows me to put three DVD's in the computer and rip all three to hard drive in about 15 minutes.
However I have to put in a three minute pause between each instance of Dvdfab is started because of one major problem.
Even though the batch files tells Dvdfab to use D, E, or F drives, Dvdfab appears to ignore this and it always attempts to use a different drive. This is a bit of a problem because the 2nd instance of Dvdfab will then interfere with the first drive copying and almost stop the 1st instance. Dvdfab seems to ignore the drive directive in the command line and just tries to work out if there is activity on a earlier drive.
For example I start a rip on drive D. The batch file waits three minutes then starts a second instance instructed to rip from drive E, however when it starts it attempts to access drive D again, when it finally works out it can't it access drive D it reverts to E and gets on with the rip. When the third instance opens it tries to rip from drive E until it realises... you get the picture. The pause is necessary to ensure the drive gets up to optimum rip speed as to not completely stop the process. I would like to get rid of the pause and..
If this was fixed it would be very simple to create an autorun handler and we would not need a batch file to kick of the ripping process. It could just be completely automated at each individual drive level.
Apart from this nagging issue the application is fantastic and worth every penny.
Thanks.
I have a system with 1 BD and two DVD drives. I have a batch script running that works pretty well and allows me to put three DVD's in the computer and rip all three to hard drive in about 15 minutes.
However I have to put in a three minute pause between each instance of Dvdfab is started because of one major problem.
Even though the batch files tells Dvdfab to use D, E, or F drives, Dvdfab appears to ignore this and it always attempts to use a different drive. This is a bit of a problem because the 2nd instance of Dvdfab will then interfere with the first drive copying and almost stop the 1st instance. Dvdfab seems to ignore the drive directive in the command line and just tries to work out if there is activity on a earlier drive.
For example I start a rip on drive D. The batch file waits three minutes then starts a second instance instructed to rip from drive E, however when it starts it attempts to access drive D again, when it finally works out it can't it access drive D it reverts to E and gets on with the rip. When the third instance opens it tries to rip from drive E until it realises... you get the picture. The pause is necessary to ensure the drive gets up to optimum rip speed as to not completely stop the process. I would like to get rid of the pause and..
If this was fixed it would be very simple to create an autorun handler and we would not need a batch file to kick of the ripping process. It could just be completely automated at each individual drive level.
Apart from this nagging issue the application is fantastic and worth every penny.
Thanks.
- Benjamin Franklin 1706-1790
Comment