markyzno
For me the frustration is within the ACT/Remote/midi Learn functionality within Sonar. It's not great.
The second (and the last) attempt. I am not spammer.. I just try to help.
ACT is mapping between virtual "control X" and "parameter Y" in plug-in, changed when you focus another plug-in to "parameter Z". What is Y and Z are configurable (ACT learn). Nothing more.
Remote/MIDI Learn is basic MIDI control, almost historical.
Sonar has a concept of Control Surface plug-ins. They are responsible for communication with hardware and performing tasks in Sonar (ACT is just a small part of possible tasks). CW has limited set of such plug-ins. Some hardware producers have product specific plug-ins (Nektar, Novation, Mackie and Roland), just for several devices and partially outdated.
CW has 2 generic plug-ins, suitable to use with many devices. But only simple devices are covered. And only small subset of possible operations is allowed to be assigned.
The idea was that hardware producers will write own plug-ins for serious devices, the API and the source code is public since long time. It is not about "template" or configuration, it is about real binary program, specially developed for particular device to support CW products. Unfortunately, hardware producers do not see an interest in such development.
I have developed universal plug-in, which can be configured by everyone, without programming skills. It is able to work with almost any device communicating throw MIDI. Unlike generic CW plug-ins it support bidirectional communication. It can trigger close to all supported operations in Sonar.