First of all, hello everybody and thanks for being there ! And especially to Damien Z., Robin, and Takashi S. for getting a driver together.
I have just been given a digidesign 003 Factory, the one with a control surface. I have my audio inputs and outputs running through jack (couldn’t get pipewire to deal with it, although it may be simply a matter of settings… …haven’t found solid documentation on pipewire yet), and the sound is great by my ears.
With the 003 in midi mode, I can associate controllers in Ardour (Ctrl - middle click). In edit → preferences → plugins → control surfaces → generic midi, the incoming and outgoing midi are with the 003. Motorized and Enable Feedback are set.
My question concerns getting fader motorization to work, so I guess it has more to do with the device or the driver than with Ardour. Indeed, I can record automation of a track’s gain/fader from the device, and play it back (shows in qmidiroute).
I have connected all of the Ardour midi out ports to each of the 003 in ports. The 003 ignores the messages, but seems to make them available on its midi ports as the leds blink.
I have tried starting jack with midi driver raw or seq, using none + a2jbridge I don’t even receive midi in Ardour (the only a2jbridge posts in qjackctl are the defaults).
Is there a non official standard for this type of command, can we get the information from the device itself through midi, or would getting this to work involve spying on the communication between protools and the device (I only have linux, not anything with protools).
Am I right to think that the messages should be translated somehow, put them into system exclusive messages perhaps ?
(I’ve looked for more than an hour but so far all I have is: F0 13H … F7, perhaps an Event List Request somewhere inside ? 13H = Digidesign Inc. ID)
If anybody knows how to get the Digi 003 in midi mode to accept
automation feedback as it is, I would be most grateful. Alternatively, I would not take any help in figuring out how to get this working badly. Finally, if this required work on the driver, and not just some midi hack, I would be willing to do testing. (I don’t write C, and know little about device drivers, so I don’t think I would be much help actually developing.)
Cheers,
LiS