azslow3
The reality is such that no one cares about control surfaces in SONAR. There are severe bugs for years in ACT mapping, preset names, etc. I do not think CW is going to fix them. As you can see from this thread, the number of interested people can be counted on fingers. We will visit Mars before they write some SONAR specific software.
There is more interest in this topic than you know.
My controller is very basic. One slider, eight assignable buttons, 8 Banks,
two increment/decrement buttons. No Sound.
Unsupported by Sonar, even though it was made by Roland,
when Roland still owned Cakewalk.
I find
WAI and
ACT to be tedious and incomplete, if
SOMEWHAT helpful.
I even tried to get into
CAL because of it's low level access to Sonar (Thanks for that,
bakers).
Funny, how the many versions/updates/flavors of Sonar have never broken
THAT.
Then I asked myself do I really want to re-invent the wheel from inside a program that
COULD have
done this more thoroughly in the 1st place, and decided I didn't want to learn more
CODE.
I presently use
GlovePie to control Sonar through voice input trigger,
with phenomenal success;
The Cakewalk/Roland policy regarding long term support of a product and
backwards compatibility reminds me of a teenage virgin walking into a room
FULL of
whatever they are seeking, for the very first time...
You just
know they aren't staying with ANYONE long.
I am hoping this will change under Gibson.
Outlook: hopeful, but guarded.
This drove me away from my hardware controller;
What I am reading gives me hope.
Can you give me a brief synopsis of what is required from me system-wise to
implement your program?
The rest I think I have gleaned/can glean from the above discussion.
Thank you for your help in advance, and kudos for your hard work.
Mel