Time to improve ACT (jog wheel / Shuttle)

[Will Zégal]

ACT is great. OK. Not as simple that it could be, but great.

It has been made to fit Roland & Edirol controllers and MIDI keyboards. It may be the time to escape this restriction and improve ACT so it can be used with any control surface.

According to me, what's missing the most is a jog wheel. A jog wheel is maybe the most relevant controller for a DAW and ACT has none.

There are so many controllers with shuttles, endless knobs or even XY pads and of course many touchscreen controller that could provide jog/shuttle if ACT would allow it.

We could even think about affecting a standard keyboard pitch bend to jog control.

[abacab]

Any update to ACT would be welcome. Agreed that it's not as simple as it could be!

[chris.r]

+1

I liked ACT, I believe more people could benefit from a more matured revision.

[azslow3]

A bit late, but ACT support jog wheel.  F.e. MCU use it.

ACT is a C++ API, so it "support" any kind of devices, as long as someone implement support for particular device using it. No restrictions there, API is open as has MIT License (open source, public and can be used for free by everyone, unlike related APIs in most other DAWs).

BTW. For someone who doesn't like to write in C++, there is AZ Controller. "Jog" Action with all related parameters and ready to use by any encoder (including touchscreen apps throw OSC) is about 1minute to configure using it.

There are many things ACT does not support, f.e. content editing and matrix. But jog wheel and almost all other mixing related operations are supported already.