When MP3 metadata not available - reject causes batch to suspend

[BriGood]

I thought I had this working during the trial period, but after registering dbpoweramp reference I find that when a CD is rejected for unavailable metadata (or other problems), batch processing is suspended waiting for a keyboard response to the Abort/Retry/Ignore dialog.

Is there a configuration setting which allows batch processing to continue without manual intervention?

Thanks!

[Spoon]

Re: When MP3 metadata not available - reject causes batch to suspend

Batch Ripper configuration >> uncheck the option 'reject cd if no metadata'

[BriGood]

Re: When MP3 metadata not available - reject causes batch to suspend

Batch Ripper configuration >> uncheck the option 'reject cd if no metadata'

Yes, this will prevent the CD from being rejected but dbpa will rip the CD content to an 'Unknown Artist' (or optionally a more uniquely-named folder) and the robot will discard the source CD with the fully processed source CDs. In the context of dozens or hundreds of processed CDs, this makes it very difficult to isolate those CDs which require operator intervention to manually enter MP3 metadata.

I wish I could remember the process I used before which consisted of two profiles: 1) which would reject CDs with no metadata and continue batch processing; and 2) a second profile for the pile of rejected CDs which enabled manual entry of CD metadata prior to finalizing each rip. I see where the 2nd profile is handled by checking the 'Forced review' checkbox, but I can't seem to get around the 1st profile's batch suspension at the Abort/Retry/Ignore dialog triggered by a rejected CD.

Any ideas for how to continue batch processing and effectively force a 'Retry' at the Abort/Retry/Ignore dialog when there is no metadata? (Or avoid the dialog entirely?)

[Spoon]

Re: When MP3 metadata not available - reject causes batch to suspend

What is the exact wording on this Abort / Retry / Ignore dialog?

[BriGood]

Re: When MP3 metadata not available - reject causes batch to suspend

What is the exact wording on this Abort / Retry / Ignore dialog?

Here is a screenshot of the error dialog...

[Spoon]

Re: When MP3 metadata not available - reject causes batch to suspend

What is your autoloader? (robot)

[BriGood]

Re: When MP3 metadata not available - reject causes batch to suspend

What is your autoloader? (robot)

Primera Composer XL

[Spoon]

Re: When MP3 metadata not available - reject causes batch to suspend

This is the loader routine which shows this message, not batch ripper. Illustrate did not write this loader so we are not able to advise, and the individual who did is no longer around.

[BriGood]

Re: When MP3 metadata not available - reject causes batch to suspend

Thanks for the error diagnosis, Spoon. From the documentation at http://www.dbpoweramp.com/Help/Batch...g_drivers.html I looked at the contents of my Primera Composer folder under \dBpoweramp\BatchRipper\Loaders\ and found the information there somewhat cryptic.

Can you suggest any resources for additional understanding and perhaps tweaking of my loader's Reject behavior?

Thanks.

[Spoon]

Re: When MP3 metadata not available - reject causes batch to suspend

If you look at the file:

DefaultCmdLine (human readable).txt

then try to edit the command line, it does not make much sense to me either...