azslow3

That dialog serves just one purpose, enable some control over Cakewalk from keyboards/DPs which have no DAW controller functionality. For example if you have Digital Piano with 3 pedals, that assignment allow you to use up to 88 commands when let say left pedal is pressed. That is great feature I was missing in REAPER when I have switched. I have missed it so much that I have re-created that functionality there (till AZ Controller is written for REAPER). But specialized controllers are working throw specialized route. That has many advantages, including multi-functional buttons and combinations, feedback, etc.: Generic Surface is the simplest to learn and support all MIDI events (f.e. SysEx as on some MMC capable controllers). But it has fixed list of available operations Cakewalk ACT MIDI allow all commands from "General Bindings" page in preferences and simple one modifier combinations. But it does work fine with MIDI CC messages only (Note off are "leaking" in stock version) and implements fixed number of physical controls (8+1 buttons, 8+8 knobs or sliders) AZ Controller is most tricky to understand and configure from these 3, but it has no limitations (has feedback, OSC support, etc.) So there are several options how to configure the transport buttons, but MIDI assignments in the keyboard shortcut section is not the way to go in this case. At the moment I do not like NI: They have declared NKS (in part of common switching presets and light guide) proprietary and are not going to change that They are selling TFT monitors and LEDs as accessibility tool... (at least they have plans to change that with A, but for some reason that has not happened last months). If they fix at least issue (2), I can try to support S 2 and A. Technically that is possible (with AZ Controller).

Since that is a new forum, I re-post what I have written on the old one: There is user created preset for AZ Controller: http://www.azslow.com/index.php?topic=458.0 I can not say what it can since I do not have the device. Buses are in a separate section and require explicit switching, as in Cakewalk GUI. I do not know if that is already implemented in mentioned preset, but it is definitively possible to add if not yet there (you can ask the preset creator, do this yourself or ask me... but please use the last option only after you have the device and ready to test the result).

Most people have no problems getting transport to work with any MIDI device. As long as the device is really MIDI. NI has decided to drop MIDI for controlling part in S 2 keyboards. I do not know how it is with A. If MIDI from transport buttons is working, it can work in Cakewalk (it theoretically should, but not sure in current firmware/future or with extra NI bridge...). Generic Surface, ACT MIDI, AZ Controller. Any from these 3 plug-ins can do the trick for any MIDI device (AZ Controller also can do this with OSC, so for S2, but no one has done that so far). How hard can it be? At most deleting not existing devices in Windows device manager, deleting 2 files in Cakewalk and spending 10 minutes with documentation. Definitively manageable in 3 decades... Ableton is a nice program. But there are not many people which use it instead of Cakewalk/S1/Cubase/ProTools/REAPER/etc. Ableton has specific workflow targeting specific purpure, people use it in addition to conventional DAWs (when they need related functionality).

For me, that is the only problem in this well made forum.

Please change red (and alike) color for text (topics , etc.) to anything else.