dBpoweramp Batch Ripper: Discussions

[sredmyer]

Re: dBpoweramp Batch Ripper: Discussions

As I said there are none of the Manual Input options checked. Unless I am miss understanding what you are talking about

On further inspection I have the option labeled "Force Manual Input and Review" > "For CDs With Less Than" set to (never)

All other option under this Manual input heading are unchecked

[sredmyer]

Re: dBpoweramp Batch Ripper: Discussions

In the batch ripper, Click on the Meta-Data button and UNCHECK manual input and review

As I said there are none of the Manual Input options checked. Unless I am miss understanding what you are talking about

[EliC]

Re: dBpoweramp Batch Ripper: Discussions

In the batch ripper, Click on the Meta-Data button and UNCHECK manual input and review

[sredmyer]

Re: dBpoweramp Batch Ripper: Discussions

Spoon,

I sent you my email addresss but I never did recieve a copy of the Powerfile driver code to work on. If you are just busy and have not gotten to it yet I completely understand (been pretty busy myself). But maybe your message got eaten by my spam blocker could you send it to:
steve at RipIt Digital dot com (format as email address of coarse)

Thanks,
Steve

[sredmyer]

Re: dBpoweramp Batch Ripper: Discussions

Ok can somebody tell me what I may have done to cause this. I have been away from using the Batch Ripper for a few days and got back to it this evening. When I started a new batch the Batch Ripper is stopping after fetching Meta data on each disc and showing me the Perfect Match screen. I am fairly certain that I did not change any settings but I must have because this didnot used to happen. I have looked at the Manual Match settings and none are checked so I do not know how to make this thing not stop after each disc. Also for the first time this evening I got a message asking if I wanted to submit data to Accurate Rip. I do of coarse but I do not want to have a batch interupted and require me to answer the question. Is there a setting some where to turn this off until after a batch.

Thanks
Steve

[EliC]

Re: dBpoweramp Batch Ripper: Discussions

I have 4gigs of RAM (3.5 usable in XP)

I rebooted the system and the robot, so I dont know if the drives crashed.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

I have just had one of the cdrippers crash while using the batch ripper. Is there anyway to get more info to give to you spoon? I am using the composer max. 1 drive is stuck permanently loading, and right clicking on it and choosing show ripper does not work, canceling the disc does not work. I was able to show one of the other rippers, but it has quite ripping and one track that was ripped is stalled at 0% on encoding. R13.1.

Interestingly, Ctl-Alt-Del is not working during this crash. Everything else with the computer seems to be fine.

Is the drive still showing up in my computer? In this condition, can you operate it manually (e.g. put a cd-rom in and explore it)?

If the drive or bridge itself crashed not much can be done.

Also, how much RAM? Any of the discs have "large" tracks?

-brendan

[EliC]

Re: dBpoweramp Batch Ripper: Discussions

I have just had one of the cdrippers crash while using the batch ripper. Is there anyway to get more info to give to you spoon? I am using the composer max. 1 drive is stuck permanently loading, and right clicking on it and choosing show ripper does not work, canceling the disc does not work. I was able to show one of the other rippers, but it has quite ripping and one track that was ripped is stalled at 0% on encoding. R13.1.

Interestingly, Ctl-Alt-Del is not working during this crash. Everything else with the computer seems to be fine.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

If this message is in response to my requests for the Powerfile device...I do indeed have Visual Studio 2005 and would be happy to work on the driver for these devices. Please send me a PM with the details.

That's awesome guys. Hope this works out!

-brendan

[sredmyer]

Re: dBpoweramp Batch Ripper: Discussions

If you have Visual Studio 2005 I would be willing to share that driver for fixing.

If this message is in response to my requests for the Powerfile device...I do indeed have Visual Studio 2005 and would be happy to work on the driver for these devices. Please send me a PM with the details.

Thanks,
Steve

[EliC]

Re: Some additional suggestions.

Spoon,

Eli and I were discussing some issues in dealing with his large collection.

Brendan, things for bringing these issues up again. I know I have pushed for some of these features. I hope I am not the only one that would find some of them useful.

I know when we were speaking you very much wanted dynamic output directories for secure/accurate/inaccurate rips for example.

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

If you have Visual Studio 2005 I would be willing to share that driver for fixing.

[sredmyer]

Re: dBpoweramp Batch Ripper: Discussions

Spoon,

Is there any chance that you will be doing any more development on the support for the Powerfile devices? If so I have few requests.

1) Allow for the use of both drives in a single Powerfile unit.

2) Along with the use of both drives, if the mounting of disc could be sequential by slot position not slot number, the load time could be reduced to the absolute minimum.

3) And finally allow for the use of more than one Powerfile unit within the same batch.

If these features were implemented these inexpensive Powerfile devices could compete (on disc throughput) with the most expensive robots out there.

Thanks for an excellent product,
Steve

[bhoar]

Some additional suggestions.

Spoon,

Eli and I were discussing some issues in dealing with his large collection. I think I can condense it down to two or three requests:

1. A "Reject discs already ripped Accurately (only for this batch name)" checkbox.

Enabling would cause the batch ripper to store the ARID of each disc at the end of the ripping process when ripped Accurately. It could then automatically reject CDs that have already been accurately ripped the next time they are encountered (before the metadata lookup).

The ARIDs would be stored locally and associated with the batch name (I assume this would be preferable for most users - unless batch names are not reusable). I suggest a sorted flat file for this read at start of batch and checkpointed every xx minutes during a batch (unless you already have a local database structure that is more appropriate). Keeping it per-batch allows a flat file to be an appropriate solution as it wouldn't cause problems with commercial operations except in rare cases.

2. A "Reject non-pressed discs (CD-Rs, etc.)" checkbox. It would-auto-reject CD-Rs, etc.

3. Perhaps a variant of #1 for Secure-no-warning rips.

-brendan

[bhoar]

Re: Observations/Issues

Yep that is exactly how it looks. Also remember that each drive ripps perfectly when used individually via CD Ripper.

Note that these commands aren't used at all by the CD Ripper. It has no concept of automation. It just talks to the drive.

Again works ok in CD Ripper so I suspect that the commands are correct.

As above.

That is infact where I got turned on to this device in the first place. There is indeed a fairly powerful driver which provides command line control of virtually all features.

No, that's not a driver in the context of the batch ripper. It's a command line client, yes. But it does not fit the driver model of the batch ripper.

It is supported by a user there (on AVSForum) using the name MediaDog. He has also written a GUI if anyone is interested. It is called gui-057x.exe just search the forum you'll find several posts pointing to how to download it.

I was actually thinking that I might be able to write some VB code to automate the commands exposed by that driver. The problem I have is how then do I get Batch Ripper to call my app(s)?

You must have missed my link to the post where spoon describes the calling convention four the five actions and command line options they should expect to be passed. I'll post it again: http://forum.dbpoweramp.com/showpost...85&postcount=8

That's all you need. If you write something that can be called that way, then you are golden.

-brendan

PS - if you want to see how the Medium Changer driver is called, I recommend installing Process Explorer, enabling the column that shows the entire command line and make it wide, enabling the start time column and then sorting by start time. You'll see the load.exe (etc.) process launched and can see exactly what command line options are passed. It should match what is specified in the link above.