illustrate
Products            Buy            Support Forum            Registrations            Professional            About           
 

Discussion of Automated CD Loaders

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    Originally posted by EliC
    Have they provided an SDK or any additional info for the composer max? After getting a new PC I need to see about getting a new motherboard for mine - I think the serial chip? is dead :-(
    The current Primera low-level SDK (PTRobot) documentation doesn't explicitly say the ComposerMax is supported, however, it does have defines related to this unit:

    Code:
    4.4 Robot Type
    #define ROBOT_DISCPUBLISHER 0 // Disc Publisher I
    #define ROBOT_DISCPUBLISHERII 1 // Disc Publisher II
    #define ROBOT_DISCPUBLISHERPRO 2 // Disc Publisher PRO
    #define ROBOT_COMPOSERMAX 3 // ComposerMAX
    #define ROBOT_RACKMOUNT_DPII 4 // Disc Publisher XR
    #define ROBOT_DISCPUBLISHER_XRP 5 // Disc Publisher XRP
    #define ROBOT_DISCPUBLISHER_SE 6 // Disc Publisher SE
    In addition, there are concepts of drive "row" and "column" listed in the API which, in my book, only apply to the ComposerMax units.

    So, yes it looks like the PTRobot SDK should support the hardware.

    In addition, you may also want to try the beta ULCLI drivers that I sent to you, if and when the machine is working again. Since the ComposerMax was one of the last serial-based robots in their lineup, before the Bravo (read "Disc Publisher") series was released, it can be supported via the ULCLI.

    -brendan

    Leave a comment:


  • EliC
    replied
    Re: Discussion of Automated CD Loaders

    Have they provided an SDK or any additional info for the composer max? After getting a new PC I need to see about getting a new motherboard for mine - I think the serial chip? is dead :-(

    Leave a comment:


  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    Originally posted by Spoon
    We have the SDK so can create a driver in the next 4 weeks, please email:

    http://www.dbpoweramp.com/email.htm
    Cool, I've got a Bravo (I) to test too.

    -brendan

    Leave a comment:


  • Spoon
    replied
    Re: Discussion of Automated CD Loaders

    We have the SDK so can create a driver in the next 4 weeks, please email:

    Leave a comment:


  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    I don't think there is (yet) support for the Bravo line - those require use of the Primera SDK to operate via their proprietary USB driver. Perhaps you can ask spoon to look into what it would require to support the units?

    -brendan

    Leave a comment:


  • jredmond
    replied
    Re: Discussion of Automated CD Loaders

    I have an older Primera Bravo and can not get the program to operate the loader.

    Any plans for the older models?

    BTW, I think this will be a great program!

    Thanks!!! James

    Leave a comment:


  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    Originally posted by dastrix
    I am looking to do large scale ripping with some software just like this, in terms of change/auto loader support which hardware device would be best for use here? Assuming I use the batch ripper software
    kris,

    Sorry, I missed your post last month.

    I think for large scale ripping, the contemporary MF-Digital and Mediatechnics 250 to 900 disc robots (see their sites) work very well. For reliable secure ripping, it may be necessary to change the connectivity arrangements from their typical method of firewire to SATA or IDE (which may interfere with the primary purpose of the robot).

    Note that they both do sell their robots not just as duplicators but also with third party software (from ripfactory, GD3 and one other source) that can also be used for ripping. I'd call them up and find out their current hardware specs and package prices.

    All,

    I've been testing the dbpa batch ripper with several of the Mediatechnics multi-drive robots and the driver I worked on is now rock solid.

    If anyone out there would like to test a pre-release of the second revision of the mf-digital or mediatechnics drivers, please drop me a PM (or email me brendandothoar@gmailDOTcom replacing "dot" with a period symbol) and let me know which hardware you have of the three listed on this page:



    If your hardware is under another brand name, but looks like one of those, please feel free to contact me about that as well.

    -brendan
    Last edited by LtData; April 29, 2008, 10:46 PM. Reason: edited e-mail to avoid spam bots

    Leave a comment:


  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    An update on robotics...

    At the moment I have three cd/dvd robots sitting on my desk right now, performing exercises of the the ULCLI scripts all called by one instance of the batch ripper, testing the new ULCLI features and the scripts that implement them. All three robots (A discmakers micro ultra, a kodak kiosk unit and a Primera Composer Pro) use different command sets, yet are working under one instance of the batch ripper...

    I feel a bit like Zorg, heh: "...look at all these little things, so busy now..."

    (referring to this scene: http://youtube.com/watch?v=krcNIWPkNzA )

    I should probably watch what I eat tonight.

    Off to the treadmill and, later, BSG!

    -brendan

    Leave a comment:


  • dastrix
    replied
    Re: Discussion of Automated CD Loaders

    Hi Guys

    I am looking to do large scale ripping with some software just like this, in terms of change/auto loader support which hardware device would be best for use here? Assuming I use the batch ripper software

    Thanks
    kris

    Leave a comment:


  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    Originally posted by EliC
    Brendan,

    Just wondering if you have any status updates on ulcli 1.0?
    Getting there, up to internal release v0.92.

    In general work has been progressing, but I've done no coding work in the last eight or nine days for several reasons. Some of them are general day to day stuff (work and family obligations), but others are related to prepping my home office for heavy duty testing of the ULCLI with large capacity robots. In other words, things that need to be done in order for code testing before release.

    -brendan.

    Leave a comment:


  • EliC
    replied
    Re: Discussion of Automated CD Loaders

    Brendan,

    Just wondering if you have any status updates on ulcli 1.0?

    Leave a comment:


  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    Originally posted by Spoon
    I will have to add to the wishlist for R2 of Batch Ripper, that section of the code has been frozen for full release (in a couple of weeks).
    Ok, I understand. If you want to get together to reexamine (here or via email) at a later time, just let me know.

    I'll continue on my ulcli coding concentrating on the areas of more sane pre-batch and post-batch behavior, plus better device error handling.

    -brendan

    Leave a comment:


  • Spoon
    replied
    Re: Discussion of Automated CD Loaders

    I will have to add to the wishlist for R2 of Batch Ripper, that section of the code has been frozen for full release (in a couple of weeks).

    Leave a comment:


  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    Originally posted by bhoar
    I'd like to see something like one of the following three approaches implemented...
    Or, if you have a better idea, let us know.

    -brendan

    Leave a comment:


  • bhoar
    replied
    Re: Discussion of Automated CD Loaders

    Spoon,

    Eli has been interested in having the batch ripper support more than just a binary (accepted/rejected) output decision via unload/reject.

    I can foresee ways that I could handle that directly in the ULCLI for certain loaders. e.g., if the disc's metadata, accuraterip and secure "status" information is passed via flags, I've got some ideas on how to use that information for rip result specific filing of discs in some of the robotic loaders that allow for explicit stack addressing.

    e.g., I'd like to see something like one of the following three approaches implemented:

    Code:
    Idea #1:
    --metadatafound=true/false	true if match was found and used
    --accurateripfound=true/false	true if disc was found in accuraterip
      --accuratelyripped=true/false	true if all tracks were AR verified
      --securelyripped=true/false	true if all tracks were AR verified *or* if none were, all were securely ripped.
    				alternately to deal with a result where it's Ok if 8 of 10 were AR and 2 were secure...
    				true if all tracks were either AR verified *or* were securely ripped.
    Idea #2:
    --metadatafound=true/false
    --accurateripfound=true/false
      --accurateripstatus=all/some/none
      --secureripstatus=all/some/none
    
    Idea #3:
    --metadatafound=true/false
    --accurateripfound=true/false
      --totaltracks=#
      --accuratetracks=#
      --securetracks=#
    -brendan

    Leave a comment:

Working...