illustrate
Products            Buy            Support Forum            Registrations            About           
 

dBpoweramp Batch Ripper: Discussions

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    How did you set it to shutdown? Batch Ripper >> Profile Edit then set in profile?

    Leave a comment:


  • Paul_B
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Slight annoyance with the Batch process. If you set-off a Rip of severval hundred songs and then set the action on completion, i.e. shut-down. If you then cancel the rip (in my case returning to the laptop to dial into work) it is annoying that the batch programme then shutdowns the machine or any other action you selected on completion.

    Would it be possible that if the batch programme is cancelled interactively the action is ignored? Or a message is displayed?

    Paul

    Leave a comment:


  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Click the line again and it re-appears, it is a known refresh issue.

    Leave a comment:


  • EliC
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Bug: When editing a drive and setting to Unconfigured, the configure button does not re-appear next to the drive in the list of unconfigured drives.

    Leave a comment:


  • bhoar
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    A configuration convenience request:

    Instead of five fields:
    Code:
    Pre-Batch
    Load
    Unload
    Reject
    Post-Batch
    How about six fields:
    Code:
    *All*
    Pre-Batch
    Load
    Unload
    Reject
    Post-Batch
    Reason: I get tired of manually changing the --comport= and --comspeed= options thirty times for six drives. Six times is more manageable.

    If you do this, there should also be an All subdir in each loader directory (to allow the driver to set the default CLI parameters).

    -brendan

    Leave a comment:


  • bhoar
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Spoon -

    106x? That's nothing, I hit 108x a couple days ago!

    (on a thinkpad t60p...in burst mode of course...wait till the quad core arrives)

    -brendan

    Leave a comment:


  • Spies
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Spoon you were right, I made a mistake. :( In trying to get these drives to work with Batch Ripper I must have inadvertently turned off "Prevent auto-run on all CD drives" in CD Ripper. With that option on in CD Ripper I need to click the Retry button to load a new disc. With that option off CD Ripper does detect a new disc as well as Windows just as you expected. Turning that option off in the Batch Ripper Configuration did not allow Batch Ripper to sense a new disc however.

    So I guess I am requesting that Batch Ripper have the ability to sense a new disc using auto-run like CD Ripper can even though I know it puts my system at risk of root kits. Another option, however not very practical, would be to have a Retry button available in Batch Ripper like CD Ripper.

    Leave a comment:


  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    >Is this different from the standard ripper then?

    Actually the prevent auto run will not work on the very old plextors, it needs a modern MMC call, so you are still getting the auto-run (easy test, open explorer with no cd in drive, keep on my computer. Start CD Ripper, put cd in drive, look at explorer and press f5, if it shows the cd drive changes to 'audio cd' then preventing auto run is not working).

    None of the calls mentioned by breandon are handled by the px-40.

    Leave a comment:


  • Spies
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by Spoon
    As brendon said, CD ripper can use the Auto Insert Notification, by default batch ripper turns off this, to stop those Sony CDs taking over your system with root kits...
    I'm confused then. I have the "Prevent auto-run on all CD drives" enabled in CD Ripper and it senses disc changes just fine and I seem to remember toggling this option on and off in the Batch Ripper settings to no avail.

    Originally posted by Spoon
    We constantly poll the drive using calll 0x4a (get mediastatus), this is not supported in theolder plextors.
    Is this different from the standard ripper then?

    Leave a comment:


  • bhoar
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by Spoon
    >Is the code different for the Batch Ripper?

    As brendon said, CD ripper can use the Auto Insert Notification, by default batch ripper turns off this, to stop those Sony CDs taking over your system with root kits...

    We constantly poll the drive using calll 0x4a (get mediastatus), this is not supported in theolder plextors.
    Hmm...I wonder if they are new enough to support the tray status bit in Mechanism Status (0xBD) and/or the disc type byte in Get Configuration (0x46)? Or if there's a useful way to poll using Read Disc Information (0x51)?

    -brendan

    Leave a comment:


  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    >Is the code different for the Batch Ripper?

    As brendon said, CD ripper can use the Auto Insert Notification, by default batch ripper turns off this, to stop those Sony CDs taking over your system with root kits...

    We constantly poll the drive using calll 0x4a (get mediastatus), this is not supported in theolder plextors.

    Leave a comment:


  • Spies
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by bhoar
    Did you actually click the Rip button? The first screen is the job setup screen, you have to click Rip to go into the mode where it starts opening/closing the tray and looking for the disc...
    Thanks for the suggestion Brendan, yes I did click the Rip button In fact I have used the Batch Ripper on another system with fantastic results. It just does not seem to work with these drives.

    Originally posted by Spoon
    It could be our code to find if a CD is in the drive is not compatible with old non-mmc drives.
    That would be unfortunate, but I find it odd that the stand alone Ripper does detect CD changes. Is the code different for the Batch Ripper?

    Originally posted by bhoar
    I suppose one could fall back to enabling windows autoinsert notification. Ugh.
    If that would make it work with these drives I think it would be better then nothing.

    Leave a comment:


  • bhoar
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by Spoon
    It could be our code to find if a CD is in the drive is not compatible with old non-mmc drives.
    I suppose one could fall back to enabling windows autoinsert notification. Ugh. :(

    -brendan

    Leave a comment:


  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    It could be our code to find if a CD is in the drive is not compatible with old non-mmc drives.

    Leave a comment:


  • bhoar
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by Spies
    Does the Batch Ripper work with SCSI Pass Through(D8)? I can't seem to get it to work with my two Plextor PX-32TS drives that require the D8 mode to function. They work fine in CD Ripper but the batch ripper just stares at me after I start a batch and insert a disc. Any Ideas?
    Did you actually click the Rip button? The first screen is the job setup screen, you have to click Rip to go into the mode where it starts opening/closing the tray and looking for the disc...

    -brendan

    Leave a comment:

Working...