Batch Ripper Assistance Needed!

[ghibliss]

I finally have my Microtech Xpress XL machine operating using dbpoweramp Batch Ripper. The problem is it is only "loading", "unloading", and placing the cd's in the output spindle. For some unknown reason after the "unload" is completed the drive drawer closes when it should stay open and continue loading another cd. After the first cd is completed and placed on the output spindle batch ripper displays that the "batch is completed"! All functions in the loading instructions appear to work perfectly. There is nothing in the ULCLI documentation regarding having a specific command to use to allow the ripper to run continuously.

The machine is now able to batch rip using all (12) twelve drives with this one issue needing to be resolved to make it 100% functional.

Does anyone have any idea what is wrong?

[Spoon]

Try setting 'end after' to the exact cd count you rip.

[ghibliss]

I tried setting it to "End After" 100 " Discs Ripped". All that this does is display what disc is being ripped ie 9 of 100. It does not have any effect on the loading function of the cd's. Such a shame that we are so close to having this machine operate 100% with batch ripper!

[Spoon]

The loader / unloader is able to signal to batch ripper it has completed (spindle empty),

--passerrorsback="x:\filename1.tmp" requests any errors from loader to this temp file, should be saved as Unicode plain text, if contains [cancel batch] (all lower case) then batch rip is ended

[ghibliss]

Spoon,

The ULCLI loader has no commands to manage what takes place after all commands have been completed from the individual folders ie. Load, Unload, Reject. What we require to allow the batch ripper to be placed in a continuous loop cycle of ripping is something that must be under the control of the batch ripper "configuration". The configuration most likely is what instructs what happens when all commands have been completed in "Load" and is told to continue to run in "Unload". There are no commands in any of the provided examples which are available that tell the batch ripper when to stop or to continue after ripping.

If you could please tell us how the dbpoweramp provided batch ripper files are being instructed by the "configuration" utility we could complete our project. It would be quite easy to complete other brands of automated rippers with this additional information which is the critical missing link from the documentation.

[Spoon]

In the batch help file is a technical document about writing your own loaders, to see batch ripper running normally set the drive to manual load - auto eject, and manually load a few disks in the drive.

[ghibliss]

I have no issues with the batch ripper program running in the manual load - auto eject mode! Running batch ripper using the loader which we have built using the instructions and the ULCLI documentation has provided us with a functional ripping machine that will load only one cd to each of the(12) drives and unload them to the output spindle. Ultimately it should be reloading each drive following an "unload". Since the ULCLI does not provide any commands instructing the machine what to do following "Load" or "Unload" the "configuration Utility/batch ripper" must control what takes place. The configuration/batch ripper must see that once all the commands have been successfully completed in "Load" that it instructs it to proceed with "Unload". When "Unload" has been completed the "Configuration/batch ripper" should be instructing the machine to loop back to "Load" and continue this process for each drive until the machine either runs out of discs or the user manually stops it.

I am assuming that you wrote the "configuration/batch ripper" interface to dbpoweramp and BHoar simply wrote the ULCLI loader documentation and loaders for the machines which you support on the website. Can you please advise regarding how to enable this functionality?

The issue we have is not unique to the machine we are using since none of the loaders which you provide the commands for are using commands which differ in any way from what we are using.

[Spoon]

You would like we can upload a complete source loader in c++ such as the Nimbie driver

[ghibliss]

I would like to see the source loader in C++ please. Could you provide the C++ for the Amtren loader as that is the model I patterned my current loader with which works albeit not automated reloading. If the only method for me to have my machine operate with dbpoweramp is to write a custom application then this might help.

[ghibliss]

Is my assumption correct regarding how the"Configuration" in Batchripper handles the iteration of the"Load" command?

[ghibliss]

Spoon,
The Acronova Nimbie uses a USB interface so the C++ code which you are offering to upload would not support a ripstation utilizing a serial connection to communicate with the arm. The Sata commands to open and close the drive would have to be in the C++ which we presently have performed from the ULCLI.

Is there any way that you could provide either an API or a way to access dbpoweramp via a command line? It seems unfortunate that you are unable to provide us with the ability to simply use the "configuration"in dbpoweramp to have the "Unload" loop back to the "Load". This would make the current loader 100% functional.

[Spoon]

Our metadata licenses forbid normal CD ripper being used as a batch ripper.

[ghibliss]

How about a command line interface to batch-ripper? Just thinking of a way to provide the batch ripper with continuous "Load" "Unload" capability.

[Spoon]

Batch Ripper has a command line interface for running loaders:

https://dbpoweramp.com/help/batchrip...g_drivers.html