dBpoweramp Batch Ripper: Discussions

[EliC]

Re: dBpoweramp Batch Ripper: Discussions

Just out of interest, what is your current recommended CD Drive for best ripping results ?

Any real plextor (not 230a). My best performer is my 712 single layer dvd burner.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

1. Rip As One:

Are you working to integrate this into the batch ripper?

2. Reject threshold:

Some thoughts on the best way to differentiate a good rip vs. a bad rip in the Batch Ripper...

This comes into play if you've got several hundred CDs queued up in a machine and a tiny (say, 10 disc) reject bin. Processing is going to stop on a regular basis for clearing the reject bin *especially* due to the use of either accuraterip or secure ripping. There are some physical workarounds (e.g. construct a felt-covered ramp over the reject spindle/location), but...some fine tuning of the reject logic is still useful based on the kind of job you are running.

So...I would suggest something along the lines of both Basic vs. Advanced Reject handler settings.

A. For Basic, it would be three radio buttons and a checkbox (the latter you already have) :

(o) Strict: reject if not a secure rip ("secure" is inclusive of accuraterip verified burst rips)
( ) Balanced: reject if damage may be audible as a click or worse
( ) Lax: reject only if damage is severe

[X] Reject CD if no Meta Data

Plus, I'd also add an explicit

[X] Reject CD if it does not contain audio.

The last bit for times when you need to avoid using the reject capability altogether.

B. For Advanced, I get a little fuzzy. The three basic settings above would map to certain presets in the advanced dialog... some combinations of the settings below or whatever you work out. Perhaps settings could include some of the following:

- Multiple metadata matches found: Yes/No
- Detected >= [ ] tracks not in accuraterip (only works if drive is accuraterip configured)
- Detected >= [ ] insecure tracks
- Detected >= [ ] correctable suspicious positions (non-audible)
- Detected >= [ ] non-correctable suspicious positions (audible)

There's some redundancy there...so just take them as suggestions since I'm not deeply familar with the error detection/correction/hiding abilities of the drives and the software.

-brendan

Edit: perhaps also a paranoid (hmm, someone already used that...) level if discs aren't fully accuraterip verified.

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

Rip as one will be done differently for image + cue sheet ripping, it should work through batch ripper.

Regarding rejects, commercial houses sometimes like to run unattended out of office hours, so for those they need to not use the reject spindle, but one of the loading spindles.

Currently you can reject an inaccurate track, it is set in CD Ripper >> Secure, mark the track as an error if insecure.

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

>support the WAV metadata standard that is read by Tag&Rename

Looking at T&R it is writing an id3v2 tag to an id3 riff chunk, we are currently doing this for the AIFF beta, not currently the wave codec (we follow the wave list chunk tagging standard which is used by such programs are soundforge, etc), but e can easily add this.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

1. Regarding rejects, commercial houses sometimes like to run unattended out of office hours, so for those they need to not use the reject spindle, but one of the loading spindles.

2. Currently you can reject an inaccurate track, it is set in CD Ripper >> Secure, mark the track as an error if insecure.

Regarding your comments above:

1. It occurred to me that if you ever add support for a "multiple jobs in one load of the input spindles" feature, say, using key discs between jobs (useful for overnight ripping on a 1000-disc/8-drive robot)...you'd want to avoid the reject spindle altogether in such circumstances. In addition to avoiding work stoppage, this is so that it would not be a mystery from which customer the rejected discs on the reject spindle came from.

The feature would also need to change some of the cli calls: unload would always be used instead of reject, both with those discs that are recognized but fail due to no-metadata/disc damage...as well as those discs that would be rejected due to being unrecognized by the drive.

2. Some sort of profile system should still be considered in the batcher for the threshold used for rejecting CDs, as this could be vastly different from one batch job to another.

...

I just installed alpha5 of the batch ripper, and...:

1. The drive configuration screen still assumes the escape key should be processed as an unconfigure drive command. I'm no longer frustrated by this since I'm used to it (as a loader driver developer, I learned quickly to always hit configure drive even when just checking settings), but end users may still be surprised by the result of having your drive unconfigured when dismissing the dialog in what would seem to be a normal way.

2. The ability to set the communications type *per drive* would come in handy. As you've seen, the USB bridge chip in the minicubis derivatives is craptastic and fares better with the windows internal communications setting instead of spti. But why limit all of your ripping drives to the lowest common drive feature set if you have a baxter?

3. It would still be nice if the End After/Spindle Change settings could also be set on a drive by drive basis. Otherwise, it is difficult to use a combination of robotic and manual load drives on the same machine. We shouldn't be surprised, in this age of dual/quad core home computers, that consumer-level users (e.g. dt minicubis/baxter owners) would want to use their robot plus a couple of extra manual-load drives to increase throughput when they've got desk-jocky in addition to the 25-disc at a time unattended ripping of the robot when they walk away.

-brendan

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

RE 3: Can you not run multiple batch rippers?

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

RE 3: Can you not run multiple batch rippers?

Good point! It does put make them into different batches, but it'll work.

On a semi-related note, in your loader support documentation, you said:

--logfile="X:\filename.tmp" requests any debugging details be written by loader to this temp file, should be saved as Unicode plain text
--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

Apparently, there are several ways to represent unicode (UTF8, UTF16, UTF32, and endian issues). My tools can generate UTF8, UTF16 little endian and UTF16 big endian. Which should I use?

-brendan

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

UTF-16 little endian, that is common for Windows.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

UTF-16 little endian, that is common for Windows.

Thanks, that worked fine.

Examining the output it sent to the Notes functionality, I have three (well, four) suggestions:

1. For each called executable can you add the process ID between the date/time stamp and the "Running ..." text?

2. Your time/date stamp in the logfile returns data only on the first line, which ends up breaking the continuity of the log a bit, since more than one line returned ends up breaking the left-side date/time stamp format. Less important, but perhaps nice.

3. Can you add the process ID after the date on the logfile output lines as well?

If you can't add the process ID of the logging executable to the log file output lines, then perhaps some other way of relating them via a unique ID (such as the log file name?).

Since I've got robots with multiple drives active, the "Running..." lines and logfile returned data are interleaved and it is difficult to trace which data belongs to which calling line.

4. A horizontal scrollbar at the bottom of the notes section would be useful as well.

Sample output to show what I am referring to...

10/31/2007  12:49:39  dBpoweramp Batch Ripper
Batch Name: 
Batch ID: 50094
Using Profile: AAC-High Test
Batch Rip Started: 10/31/2007 12:49:39

10/31/2007  12:49:39  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Pre-Batch\Pre-Batch.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="F" --bindresetall --rejectsreset --closeall --drivebank=1 --sleep=3 --bindtodrive  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1EA.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1EE.tmp"
10/31/2007  12:49:39  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Pre-Batch\Pre-Batch.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="H" --bindresetall --rejectsreset --closeall --drivebank=1 --sleep=3 --bindtodrive  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1EC.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1F0.tmp"
10/31/2007  12:49:39  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Pre-Batch\Pre-Batch.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="E" --bindresetall --rejectsreset --closeall --drivebank=1 --sleep=3 --bindtodrive  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1EB.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1EF.tmp"
10/31/2007  12:49:39  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Pre-Batch\Pre-Batch.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="G" --bindresetall --rejectsreset --closeall --drivebank=1 --sleep=3 --bindtodrive  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1ED.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1F1.tmp"
10/31/2007  12:49:45  
10/31/2007  12:49:45  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Load\Load.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="F" --drivebank=1 --close --command=MIH\M:CC --open --command=MHO\M::10:10 --close --ondiscnotreadyskip=3 --unbindtodrive --sleep=1 --exit --rejectsmax=10 --rejectsiterate --open --command=MOH\M::10:10 --close --command=MHR\M:CC:::DF --onfailure=notify:"Reject Drawer Full"  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1F6.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1F7.tmp"
10/31/2007  12:49:50  
10/31/2007  12:49:50  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Load\Load.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="H" --drivebank=1 --close --command=MIH\M:CC --open --command=MHO\M::10:10 --close --ondiscnotreadyskip=3 --unbindtodrive --sleep=1 --exit --rejectsmax=10 --rejectsiterate --open --command=MOH\M::10:10 --close --command=MHR\M:CC:::DF --onfailure=notify:"Reject Drawer Full"  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1F9.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1FA.tmp"
10/31/2007  12:49:55  
10/31/2007  12:49:55  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Load\Load.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="E" --drivebank=1 --close --command=MIH\M:CC --open --command=MHO\M::10:10 --close --ondiscnotreadyskip=3 --unbindtodrive --sleep=1 --exit --rejectsmax=10 --rejectsiterate --open --command=MOH\M::10:10 --close --command=MHR\M:CC:::DF --onfailure=notify:"Reject Drawer Full"  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1FC.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1FD.tmp"
10/31/2007  12:50:41  MIH
CC
MHO
Checking drive status...
Not skipping 3 commands...

10/31/2007  12:50:41  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Reject\Reject.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="H" --drivebank=1 --rejectsmax=5 --bindtodrive --rejectsiterate --open --command=MOH\M::10:10 --close --command=MHR\M:CC:::DF --onfailure=notify:"Reject Drawer Full"  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB1FF.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB200.tmp"
10/31/2007  12:51:25  MIH
CC
MHO
Checking drive status...
Not skipping 3 commands...

10/31/2007  12:51:25  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Reject\Reject.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="E" --drivebank=1 --rejectsmax=5 --bindtodrive --rejectsiterate --open --command=MOH\M::10:10 --close --command=MHR\M:CC:::DF --onfailure=notify:"Reject Drawer Full"  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB202.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB203.tmp"
10/31/2007  12:51:29  
10/31/2007  12:51:29  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Load\Load.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="G" --drivebank=1 --close --command=MIH\M:CC --open --command=MHO\M::10:10 --close --ondiscnotreadyskip=3 --unbindtodrive --sleep=1 --exit --rejectsmax=10 --rejectsiterate --open --command=MOH\M::10:10 --close --command=MHR\M:CC:::DF --onfailure=notify:"Reject Drawer Full"  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB205.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB206.tmp"
10/31/2007  12:52:13  MIH
CC
MHO
Checking drive status...
Not skipping 3 commands...

10/31/2007  12:52:13  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Reject\Reject.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="G" --drivebank=1 --rejectsmax=5 --bindtodrive --rejectsiterate --open --command=MOH\M::10:10 --close --command=MHR\M:CC:::DF --onfailure=notify:"Reject Drawer Full"  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB208.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB209.tmp"
10/31/2007  12:52:37  MOH
MHR
CC

10/31/2007  12:52:37  
Disc 3: Reject 3: Not Audio CD   Reject 3: Not Audio CD
10/31/2007  12:52:37  Running Loader: "C:\Program Files\Illustrate\dBpoweramp\BatchRipper\Loaders\__RImage DTP-x000 (Serial)\Load\Load.exe" --comport=COM2 --comspeed=19200 --olddrives --drive="G" --drivebank=1 --close --command=MIH\M:CC --open --command=MHO\M::10:10 --close --ondiscnotreadyskip=3 --unbindtodrive --sleep=1 --exit --rejectsmax=10 --rejectsiterate --open --command=MOH\M::10:10 --close --command=MHR\M:CC:::DF --onfailure=notify:"Reject Drawer Full"  --logfile="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB20C.tmp"  --passerrorsback="C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\dBB20D.tmp"
10/31/2007  12:54:17  MIH
CC
IC
MHO
Checking drive status...
Skipping 3 commands...
MOH
CC
MHR
MN
CC

-brendan

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

What's the maximum size of the Notes section? I've got a job running (with lots of debug output) and it seems to have last updated the Notes panel about an hour and a half ago...

-brendan

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

If you copy the text to notepad and save the text, how large is the file?

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

30000 bytes, according to notepad plus.

-brendan

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

Which Windows Version?

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

Which Windows Version?

XP Pro (2002 SP2)

-brendan

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

It is possibly limiting at 32KB, will look, and see if I can put process id for the robot bit.