Well I have finally managed to get all of my R200s (that is four of them) working from a single Host PC
. The host PC is a Dell Precision Wotk Station 470. It has dual 3.4GHZ hyper-threaded processors (single core though) with 4GB of RAM and is running Windows XP Pro SP3. Three of the four Power file units are connected to a single PCI Firewire card and the fourth is connected to the FireWire to the Firewire port of the OEM sound card. All changers work well and are managed well by Spoons CLI drivers.
However there is a problem. When I load up all changers and start a batch I tell the Batch Ripper that there are 800 discs in the batch. The Batch Ripper just blindly runs 800 discs. If some of the changers finish before the others they will just continue to rip discs just restarting at slot zero. This means that some discs (from the changers that finished first) will be ripped twice while others (those in the slower changers) wont get ripped at all.
As I have stated before I had planned to re-write the CLI's used by the Batch Ripper, I mistakenly thought they did not handle multiple drives and changers. I did in fact write my own changer control application in VB (version 6) and it works quite well. However after thinking about the problem (mentioned above) I do not see how this can be corrected by the CLI. What I need is a way to tell the Batch Ripper how many discs should be handled by each pair of drives (each changer has two drives). In this way the Batch Ripper would stop trying to use drives 'G;' and 'H:' (for instance) when the 200 discs in the changer which holds those drives have been ripped.
Spoon, is there any way, via the CLIs, to tell the batch Ripper to stop using certain drives without stopping the whole process?
Thanks,
Steve
![thumpup](https://forum.dbpoweramp.com/core//images/smilies/thumbup.gif)
However there is a problem. When I load up all changers and start a batch I tell the Batch Ripper that there are 800 discs in the batch. The Batch Ripper just blindly runs 800 discs. If some of the changers finish before the others they will just continue to rip discs just restarting at slot zero. This means that some discs (from the changers that finished first) will be ripped twice while others (those in the slower changers) wont get ripped at all.
As I have stated before I had planned to re-write the CLI's used by the Batch Ripper, I mistakenly thought they did not handle multiple drives and changers. I did in fact write my own changer control application in VB (version 6) and it works quite well. However after thinking about the problem (mentioned above) I do not see how this can be corrected by the CLI. What I need is a way to tell the Batch Ripper how many discs should be handled by each pair of drives (each changer has two drives). In this way the Batch Ripper would stop trying to use drives 'G;' and 'H:' (for instance) when the 200 discs in the changer which holds those drives have been ripped.
Spoon, is there any way, via the CLIs, to tell the batch Ripper to stop using certain drives without stopping the whole process?
Thanks,
Steve
Comment