Need helping setting up ACT -- Want to control multiple VST's/channels at once - Sonar X3

No way known to me. As you've already found out as soon as focus is shifted the in focus app gets the MIDI messages. It's doable just not your way.

What you need is something that will select the next app and allow the same controller to do its magic moving the knobs on that VST. On my controller I have a set of knobs that control parameters but just one knob which moves focus to the next plugin, screen whatever

Maybe someone better versed in MIDI and ACT will know something that will help you. Here's hoping.

ACT can control one plug-in per time. No workarounds.
 
SONAR "standard" way to do what you want (theoretically):

• in plug-in manager (Menu/Utilities/CakeWalk Plug-in Manager), find the effect, open it's "Plug-in Properties" and set "Configure as synth"
• restart SONAR
• Insert it into Synth rack and attach MIDI track to it. For MIDI track set required source (your MIDI controller).
• Route audio track in question to the plug-in

But there are 2 problems:

• I do not see either BiFilter support MIDI learn. If not, all instances will need the same MIDI codes. And that mean you have to separate it on input level with some external software MIDI translator
• obvious management nightmare to setup several instances

And now good news: AZ Controller (my Control Surface plug-in, see my signature) can do this without future gymnastic (I have just checked with 2 BiFilters on 2 different tracks). But there are other caveats:

• reserve a weekend to understand how to configure it. You can start with "Startup" preset and make it work within a hour, but you then need to change actions. The end result is obvious for me (3 actions to control BiFilter freq on one track: "Strip Track <number>", "FX BiFilter2 parameter 2", "Value Catch Linear") and I am here in case you have questions.
• the project is Alpha. And you are going to use the result on stage... So you have to stress test that it is working. Do not get me wrong, I have no reports it is crashing (except some crashes on startup in previous versions which I had, not even sure the plug-in was a problem and I have targeted possible reason). There are simply not many beta testers so far to call it "stage ready".

 
 
 

Since I am near my SONAR now and I could really test proposals and remember better way to do things (and I could not convince you to use my plug-in...)
 
1) MIDI input. In the "VST2/3" menu in plug-in UI (on the top, right from preset manipulations) you can in some plug-ins (which support MIDI) select "Enable MIDI Input". Than you can target MIDI track to that plug-in. So, all that works without "Configure as synth". But the problem with MIDI assignment is still there if plug-in has no configurable MIDI mapping and you need some way to say that CC from device should target particular track. If, for example, you can define on your surface that encoder 1 send on MIDI channel 1 while encoder 2 send on MIDI channel 2, you can select specific channel input for different tracks targeted different instances of plug-ins.
 
2) MIDI learn in SONAR. In "Automation Lanes" of track in question select parameter from particular plug-in, right click in the box with automation value and select "Remote control...". Learn your encoder. Note that I had to disable "Read automation" so it works (otherwise it continuously try to reset the value), even in case all automation points are removed. May be someone can give an advise how to avoid that
 
3) think about AZ Controller one more time... it was written to make such operations simple Also do not forget that other methods will "jump" parameter to current controller value, support no "banks" (to use one controller for different parameters in one project you need hardware banks then) and support no feedback.

Hey there again.
 
Sorry azslow, I didn't mean to discount your work so quickly. Since this is going to be used in a stage environment (and I've suffered through catastrophic technical failure before) I just wanted to make sure I'd explored other options before resorting to an alpha release of something.
 
That said, this looks very promising and I'd like to know more. I'm looking at some of the documentation you've written here, but frankly some of it is a bit over my head. The fundamentals of MIDI are not new to me (i.e. CC's, values, corresponding controls, etc.) but turning those signals into something actionable for one specific plugin on one specific track seems like it will take some doing.
 
You said you had what I wanted to do in operation. Can I get a little guidance? Thanks for your patience!

Matter
Since this is going to be used in a stage environment (and I've suffered through catastrophic technical failure before) I just wanted to make sure I'd explored other options before resorting to an alpha release of something.
...
but turning those signals into something actionable for one specific plugin on one specific track seems like it will take some doing.
...
Hey Azslow, I figured it out! WOW! It didn't even take a whole weekend ... In fact, it only took about an hour. You rock, dude!

Once you have your project loaded, the plug-in configured and its configuration window closed, the code executed is minimalistic. It does not even reallocate memory during routine operations. Old style and long time forgotten approach of handcrafting C code without any external libraries. As I have mentioned already, it is alpha because there is no sufficient amount (for me!) reports that it is stable, something I can not change alone.
 
The difference between simple MIDI assigning and my plug-in is like the different between cheap hardware "all-in-one digital studio" and modern DAW. The number of possible "connections" and "processors" is changing from fixed small to infinity. As in mentioned case, it can take some time to understand the way to use it. And it looks confusing at first.
 
I am glad you are progressing fast. I have mentioned the whole configuration for one control in my first post, the project is to make things simpler, not harder. Comments, bug reports, ideas, requests or just simple questions are welcome (better on my site, I afraid CW ban me there... while SONAR dedicated and not commercial, it is still separate project).
 

I will answer here, but we really should move...
 
"Strip Track <First> +0 (+1, +2, +3, or some variable set before, etc)" and then "Function Select strip". You can also add "Command Move Input Focus to Track View", in case you currently observing some Bus. Unfortunately, the last one is not always working (I guess SONAR bug). But for all purpose except visualization (so auto MIDI input, current context for ACT, etc) "Select strip" is working reliably.
 
Note that "Select track" has some duality in SONAR. If you mean you not only want to make it current, but also really select it (as clicking on the track number) you should add "Key ','" (comma) in addition (or Shift+',' to extend existing selection).