dBpoweramp Batch Ripper: Discussions

[LtData]

Re: Album art

Check dBpoweramp Configuration (see "Need to find your version?" below), it will tell you the status. You should have at least a 30-day trial if you activated it and it has not yet expired.

[sredmyer]

Re: Album art

Do you have an active PerfectMeta (r13) or AMG (r12) subscription?

Yes I have r13 not sure if the PerfectMeta feature is turned on or not...How do I tell?

No I have not yet subscribed to AMG (plan to in the future but I haven't yet)..will need instructions on how to go about signing up for that service in the near future

[LtData]

Re: Album art

Do you have an active PerfectMeta (r13) or AMG (r12) subscription?

[sredmyer]

Album art

I am sure I am just not doing it correctly but I can not get the Batch Ripper to save the Album Art. I have it set so that it is retrieved and saved when using CD Ripper. Is there some other place it must be set for the Batch Ripper to use it?

Thanks,
Steve

[MrBuBBLs]

Re: dBpoweramp Batch Ripper: Discussions

Okay, hi everyone. My company just got it's hands on a licence of dbpoweramp and I'm actually testing the batch ripper.

There are a few "glitches" in it.

First, there is no scrollbars on the right side of the CD-ROM list when you rip.
So I have a machine here with 9 Plextors with the batch ripper running and I can't see all of the 9 drives at the same time. Could there be scroll bars in future batch ripper release ?
(Reducing batch ripper's windows size doesn't either solve that problem... There aren't no scrollbars appearing)

Sorry for my bad english guys, I'm a frenchy.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

So then it should be possible for me to call those executables directly from my own batch file and use another program to image the DVDs? Even just having that would be enough to make it worth buying dBpoweramp.

See "Loader CLI Switches" in this thread for more info: http://forum.dbpoweramp.com/showthread.php?t=13597

Again, I doubt you're going to get any support doing something like that, and probably risking a moderator stop the discussion if it goes into any further specifics.

-brendan

[Donovan]

Re: dBpoweramp Batch Ripper: Discussions

Spoon has stated in that past that his baxter "drivers" (in the batch ripper, not windows sense: load.exe, unload.exe, reject.exe, pre-batch.exe, post-batch.exe) should work for all varieties of these devices regardless of whether the device reports itself as a baxter or something else.

So then it should be possible for me to call those executables directly from my own batch file and use another program to image the DVDs? Even just having that would be enough to make it worth buying dBpoweramp.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

Is it possible to do something other than audio ripping with the batch ripper? I'd like to use it with an MF Digital Baxter to rip DVDs to .iso, and I was hoping there was a way I could configure it to run a command-line disc imaging program that works with DVDs instead of attempting to rip CD audio tracks. I don't mind writing some external scripts on my own.

Also, the Baxter I ordered will probably not come with any software (repackaged under another name with unknown control software)...does the batch ripper need any drivers that come with the unit or does it just need its own?

No, at the moment dbpoweramp only handles audio CDs. I suspect that for the foreseeable future, Illustrate will stay away from DVD ripping (for legal/liability reasons) though only Spoon can say for sure.

The Baxter-type (baxter, minicubis, dupliq, etc.) units all use the same windows driver (the driver proper is a renamed copy of microsoft's bulkusb.sys), though often the .inf file packaged with the units differ because of branding and/or the PID/VID combination that the USB device reports itself as. In other words, other than the paint and print on the outside of the units, they only differ in the device (product/vendor) ID that they report. In the past, I've modified the inf file to masquerade a dupliq as a baxter, etc.

Spoon has stated in that past that his baxter "drivers" (in the batch ripper, not windows sense: load.exe, unload.exe, reject.exe, pre-batch.exe, post-batch.exe) should work for all varieties of these devices regardless of whether the device reports itself as a baxter or something else.

-brendan

[Donovan]

Re: dBpoweramp Batch Ripper: Discussions

Is it possible to do something other than audio ripping with the batch ripper? I'd like to use it with an MF Digital Baxter to rip DVDs to .iso, and I was hoping there was a way I could configure it to run a command-line disc imaging program that works with DVDs instead of attempting to rip CD audio tracks. I don't mind writing some external scripts on my own.

Also, the Baxter I ordered will probably not come with any software (repackaged under another name with unknown control software)...does the batch ripper need any drivers that come with the unit or does it just need its own?

Thank you in advance.

[EliC]

Re: dBpoweramp Batch Ripper: Discussions

I have 2 things I would really like to see soon in the batch ripper:

1) Automatically save the highest resolution album art from BOTH AMG and GD3. You are paying for them, and if one is wrong or poor quality the other will be their without paying for another lookup

2) PerfectMeta Quality Meter
http://forum.dbpoweramp.com/showthre...9113#post79113
-use spell checker, grammer, artist lists, previous manual edits in PMdb, agreement between sources, etc to come up with some sort of measurement of the meta data quality. Prompt users to manually examine the metadata if the quality measurement is below a certain value (and of course upload any manual edits to the PMdb)

[bhoar]

Re: Batch Ripper and external loader commands

The drive handle might be left open, nothing should be accessing the drive from our end on a load.exe

Ok. Thanks, that helps.

I'm working out some issues with Jason regarding IDE drive access (trays on connected-via-IDE PX-708 drives were only opening halfway, etc. with the current ULCLI drivers, when there wasn't a problem over USB/Firewire which I've done 90% of my testing with).

For now, I've added a switch to bypass my own SPTI calls and use some more everyday calls instead...that seems to have worked for him, but you give up a bit of throughput if you uses that flag (better than a stopped process though!).

In the future, I might try to either grab an exclusive (non-shared) write handle to the device for SPTI use before using SPTI calls...or fall through to non-SPTI calls if the handle-request fails (which I suspect it will if you have a handle open).

EDIT: there's also a chance that my SPTI calls are in some way malformed from the perspective of a raw ATAPI device (one that isn't bridged via another protocol...) or at least a raw ATAPI PX-708 device.

I don't have any PX-708s to test here, but the workaround I gave to Jason lowers the issue priority for me.

Thanks again.

-brendan

[Spoon]

Re: Batch Ripper and external loader commands

The drive handle might be left open, nothing should be accessing the drive from our end on a load.exe

[bhoar]

Batch Ripper and external loader commands

Spoon -

When the BatchRipper.exe is waiting for the external commands (load.exe, unload.exe, reject.exe, pre-batch.exe, post-batch.exe) commands to exit and return control of the drive to itself...does it continue to poll the drives or does it ignore them completely until the driver commands exit?

In addition, does it continue to hold handles to the drives during that time and, if so, what share flags are used to create the handles it created and continues to have during the external loader command run events?

-brendan

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

If you set the 'secure settings' to mark any unsecure tracks as an error, the batch ripper will put any insecure discs in the reject pile which is easier for sorting.

[RipTheWorld]

Re: dBpoweramp Batch Ripper: Discussions

Haven't posted in a while so thought I would catch up with whats going on as I have been using Batch Ripper fairly happily for a while now.

I'm pretty happy with most of the features, but one thing I would really like to see is better handling of tracks that have errors. Currently the only way there seems to be of removing all tracks that haven't ripped properly is removing the tracks that haven't been tagged properly. If there is another way then Please do correct me.

In my ideal setup all CDs would be ripped on separate machines to those that do the error correction. The machine re-ripping the bad tracks would recognise that the disc has been ripped on another machine running the same job and try to re-rip just the bad tracks. If it can't re-rip them to your specified accuracy level then you are given the choice to delete the files. Having a network batch would also allow discs that have already been ripped successfully on one machine to be rejected from all others. I have recently done a few jobs where I have had multiples of the same CD and the last one to get ripped was the only one with errors so it overwrote the existing good tracks!

My current setup involves ripping on several machines and then combining all of the files onto a single hard drive before bad tracks are re-ripped and the ones that can't be recovered are removed. Keeping an error log and only re-ripping bad tracks would certainly save me a lot of time.

Also anyway to generate error reports would be useful. I have a script that scans for the rip logs and outputs what I need, but it would be much easier if all of this information was stored in a single place.