Hello.
 
I own a Behringer X-Touch mini and a M-AUDIO CODE 61 keyboard. They both have MIDI DAW Controller functionality.
If I set them to MIDI mode and add them to Sonar as a ACT MIDI controller I can normally use them to control volumes and pans, but only in direction from controller to Sonar. If I move pans in Sonar with a mouse the hardware controllers are not updated (the endless rotaries with leds).
So I'm asking is ACT bi-directional at all?
 
I'm also reading on the forums about AZSlow - is it bi-directional using controllers in MIDI mode?
 
If I switch both controllers to Mackie mode they work bi-directionally flawlessly, but Mackie mode is so limited with no customization.

slocupax
So I'm asking is ACT bi-directional at all?
 
I'm also reading on the forums about AZSlow - is it bi-directional using controllers in MIDI mode?
 
If I switch both controllers to Mackie mode they work bi-directionally flawlessly, but Mackie mode is so limited with no customization.

MackieControl (which you use in Mackie mode) is also "ACT plug-in". So yes, ACT is bi-directional.
 
Cakewalk generic ACT plug-ins ("Cakewalk Generic Surface" and Cakewalk "ACT MIDI") are not bi-directional.
 
AZ Controller is "multi-directional" (it is possible to send feedback to the MIDI controller(s) in parallel to OSC apps and to Windows build-in Text To Speach engine). But that comes at price... Only several users have succeeded in understanding how to configure it for such operations.
 
"Mackie Mode" is also just a MIDI mode, the whole "magic" happens in software. Original Cakewalk Mackie Control is a 2000+ lines of C++ code (open source, on github). AZ Controller has a preset which mimics close to all these operations one to one, so you can use it as a basis to construct what you want. But if you are not ready to invest significant time into that, just keep using your current setup...