Automation

Colby,

I’ve sent a few requests and comments to the BBS and to you directly regarding the automation interface. Among them was a request to be able to add to the playlist by disk number in the database (rather than CDJID), a request to allow us to delete playlist items by the disk ID and, my most recent post which I’ve attached below.

I realize you’re probably very busy with the new DXS controller (which I’m VERY anxious to purchase). But, I never get a response from you on my comments, either through the help email address or those posted on the BBS. I’m not sure if you’re not receiving them, or for some reason don’t find them of any interest. In any case, I’m beginning to get a complex! Once again, I realize you’re very busy and might not have time to respond to all comments and postings.

Thanks for listening,
Jim

Here is the latest one I posted.:
Currently, the CDJ automation interface only reports back to the sending program if it encounters an error. For example, if I send an invalid command or disk id to add to the playlist, it reports back "error[playlist_insert]". My program code tests for any error code, but it would be better if there was a command that we could have to turn on a confirmation that CDJ indeed did receive a valid command. Perhaps the command to turn it on could be called "confirm[on|off]". Then CDJ could report back error[none], or error[OK] (or whatever you want to call it) everytime it received a valid command.
The absence of an error does not always mean success!
Lots of fun playing with this interface!