"Modern" controllers are of 2 types: absolutely the same as 15 years ago and "proprietary" controllers (which are also internally as 15 years ago, but for marketing declared to have "proprietary" protocol).
 

VanessaJ
As for looking at a new console for the first time, I doubt many people would have the trouble understanding what does what. It may require reading instructions to get FULL use of it, but few people would be as befuddled by a new console as they/we obviously are by the ACT midi controller.

I have already mentioned, our conference system is "broken" near every week, just because of one matrix mixer... Note that users are scientists, with normally advanced hardware experience, just not with mixers...
 

That said, I did discover why I was having the particular problem described in my top post. What I didn't find in the literature, is WHY that created the problem that it did.

ACT Follows Context--if you enable ACT, you can still control track parameters by enabling this check box, and then clicking a track name. When you click a plug-in in this mode, your controller goes back into ACT mode.

What is not clear in that statement?
 
By the way. If something is unclear from the documentation, you can read "ACT MIDI Explained" (from me). It not only explain what each option does, but also explains how it does that.

arlen2133
I hate to be on the other side of things here, but I have a Roland A800Pro and I use ACT with it a lot.
Although it took a bit to set it up (twice) so that things are working properly (and understood exactly) it works.
I bought it when Roland owned Cakewalk (and for that sole reason). 
 

+1  I have never had any problems with my A800 Pro, either by itself or using it with my VS 100.  I also use my OctaCapture synced to my VS 100 with the A800.

azslow3
 

ACT Follows Context--if you enable ACT, you can still control track parameters by enabling this check box, and then clicking a track name. When you click a plug-in in this mode, your controller goes back into ACT mode.

What is not clear in that statement?
 
By the way. If something is unclear from the documentation, you can read "ACT MIDI Explained" (from me). It not only explain what each option does, but also explains how it does that.

Maybe I'm more dull than I realized, but no ... the "ACT Follows Context" description is not clear. What the heck does " ... your controller goes back into ACT mode" mean? In order to go "back" into something, it first has to be "out" of something. That description to me is cryptic. It doesn't explain why a plug-in won't work in that mode, or why the ACT Midi controller is essentially locked into "Strip Parameters".


What I mean by updating ACT is simply making a more intuitive interface, and include presets for more current controllers. Who even buys some of the control surfaces listed in that "Presets" section these days? Some of them are no longer available from retailers.

If I was the only one complaining, it could be said that it's just me. But from this thread it's obvious that others share my frustration.

VanessaJ

azslow3

ACT Follows Context--if you enable ACT, you can still control track parameters by enabling this check box, and then clicking a track name. When you click a plug-in in this mode, your controller goes back into ACT mode.

What is not clear in that statement?
 
By the way. If something is unclear from the documentation, you can read "ACT MIDI Explained" (from me). It not only explain what each option does, but also explains how it does that.

Maybe I'm more dull than I realized, but no ... the "ACT Follows Context" description is not clear. What the heck does " ... your controller goes back into ACT mode" mean? In order to go "back" into something, it first has to be "out" of something. That description to me is cryptic. It doesn't explain why a plug-in won't work in that mode, or why the ACT Midi controller is essentially locked into "Strip Parameters".

ACT unfortunately has several interpretation, it is "the technology" (API), mode when controller is used as a DAW controller (not as a MIDI controller, f.e. with "remote control" or MIDI learning inside plug-ins) and as special sub-mode in the DAW controlling mode to control plug-ins.
But as I wrote, you can read "ACT MIDI explained" for details.
 

What I mean by updating ACT is simply making a more intuitive interface, and include presets for more current controllers. Who even buys some of the control surfaces listed in that "Presets" section these days? Some of them are no longer available from retailers.

How to make "ACT MIDI" interface more intuitive is a good question without obvious answer. There is Generic Surface plug-in, more strait forward but less capable. There is my plug-in, much more powerful but more complicated to configure. There is always a trade between flexibility and simplicity.
Controller producers are not interested to support Sonar. And when you get a controller from retailers, Cakewalk does not get a single cent from your money. Who should support some controller in Sonar? As I wrote before, most producers do not even publish technical documentation. I have tried to contact producers, with the offer to integrate particular controller with Sonar, just for one test device and/or complete technical documentation for it (so that will cost nothing for them). NO interest! And some people still blame CW... And I do not users are ready to pay $20-$50 extra for particular controller support in Sonar.
 

If I was the only one complaining, it could be said that it's just me. But from this thread it's obvious that others share my frustration.

Everyone who really want to use (any) device with Sonar so far has got such a possibility. Sometimes that takes time, and the solution is not from producers nor from CW (for some people that is "no go", they prefer "labels" over functionality), other just complain... to complain.
 
I also think that ACT (as API) needs quite some love, to fix several particular bugs and support features from modern Sonar versions. But discussed in this threads ideas are not in my wish list, I mean "ACT MIDI" is already as simple as possible and producers of new controllers should take care about DAW compatibility (as they do with drivers).

I agree with everyone . ACT could be a whole lot better, but also, it can work as expected. 
 
The way I use it is as a "scratchpad" for hardware control of parameters. I gave up trying to match every parameter to everything...probably for the same reason Native Instruments abandoned Kore. I covered this usage in a blog post (which also mentions that you can pick up that sexy Kore controller for dirt cheap since Kore is no longer supported).
 
This article from 10 years ago might also be helpful, but the above approach is what has worked really well for me.

I'd like to use Act to control Massive, but i gave up after reading several pages of nonsense in the Knowledge Base. 
 
Why can Ableton make it a straight-forward easy procedure to do this with and instrument rack, but Sonar can't?
 
Why doesn't Sonar have a ready-made Act template for one of the most used synths on the planet?
 
Please point me to what I am missing, thank you.

I have written a long reply, but forum software has removed it...
 
In short, all your 3 statements are "nonsense" (sorry...):
* there are 3 ways to control Massive in Sonar, you have decided to use ACT. For that you need a controller and ACT plug-in for it (special or generic with tuning for your controller)
* Ableton, when using ACT like approach, also requires controller specific Python script. It is as "easy" to use when it exists as Sonar ACT plug-in/preset when it exists. And as hard to create as ACT plug-in/preset in Sonar.
* there is no "ACT templates" for particular VST(i). Default ACT mapping for Massive is just fine (8 knobs -> 8 Massive Macro knobs), but changing it at your like takes under 1 minute (assuming your controller is setup correctly to use ACT in general).

Some folks just can't get their ACT together!
 
For me, the MackieControl.dll was broke and would not work at all with my Behringer. It was frustrating until a forum member found another one on the web that does work. It works until I update Sonar to the latest version. Sonar overwrites it so I have to replace it each time.

azslow3
I have written a long reply, but forum software has removed it...
 
In short, all your 3 statements are "nonsense" (sorry...):
* there are 3 ways to control Massive in Sonar, you have decided to use ACT. For that you need a controller and ACT plug-in for it (special or generic with tuning for your controller)
* Ableton, when using ACT like approach, also requires controller specific Python script. It is as "easy" to use when it exists as Sonar ACT plug-in/preset when it exists. And as hard to create as ACT plug-in/preset in Sonar.
* there is no "ACT templates" for particular VST(i). Default ACT mapping for Massive is just fine (8 knobs -> 8 Massive Macro knobs), but changing it at your like takes under 1 minute (assuming your controller is setup correctly to use ACT in general).

azslow,
 
Thank you for an unhelpful and snarky reply. You needn't have bothered writing this because i was asking  politely for HELP not a condescending bunch of words designed to show how smart you are.
 
* What are the three ways you mention to control Massive in Sonar? Or is that a mystery reserved for gurus like you?
 
* What do you mean, "using ACT like approach?" My APC 40/Ableton software compiles and runs Python easily. I don't understand what these three sentences mean. Can you rewrite them in complete thoughts so I at least have a chance to understand you?
 
* Your point three is unhelpful to me also. But i'm glad it just takes under one minute to do.
 
I asked what I feel is a legitimate question, but your answer is mocking and a waste of our time. Please don't answer any more of my questions in the future. 
 
Thank you.
 
 

soens
Some folks just can't get their ACT together!
 
For me, the MackieControl.dll was broke and would not work at all with my Behringer. It was frustrating until a forum member found another one on the web that does work. It works until I update Sonar to the latest version. Sonar overwrites it so I have to replace it each time.

I'm trying to get my ACT together. 
 
I'd like to use my APC40, but i also have a couple nano-Kontrols, a BR2000, ipad, Axiom Pro 49, and a Quija Board here. Can anyone suggest a way to use any of them with ACT? Can ACT be controlled by a virtual controller from inside Sonar platinum itself?
 
Thanks.