Hello,
 
Using the synth rack remote control option as seen in the video below, is there any way to get my knob on my controller to ONLY control the synth I am playing at the moment?   I know I can use different MIDI CC #s, but I only have 8 knobs on my controller, so of course I am going to be using some of them on more than one synth!
 
When I use MIDI Learn in each individual synth, I can teach various softsynths the same MIDI CC# yet they only react when I am playing that particular synth.  
 
I am looking for that same behavior here in the synth rack.  See my video below.  Notice how ALL synths are being adjusted, not just the one I am playing.
 
https://youtu.be/JoNkyonZllo


Thank You!

Not sure why i just got this?  It seems like it is still in the forum
 
 
bitflipper  sent you the following notice:

~~~~~~~~~~~~

Your post titled 'CC Data Controlling All Synths - Only Want It Controlling The Active Synth!' in forum 'SONAR' was sent to the recycle bin.
It is no longer available for viewing.

~~~~~~~~~~~~

NOTE: Your message may no longer be viewable on the forum depending on the
action performed.

=========================================

The thread was duplicated by the forum software and the duplicate was deleted.

Oh ok - thank you very much!  
 
So it appears that the remote control feature in the synth rack will control ANY and ALL knobs with the same MIDI CC# whether or not that synth is the active track or not.  I wish that wasn't the case

MIDI CC to you synth is not steered by "current" track but by the "echo" on the track, which default happens to be "switch echo on for current track".
 
Remote Controls work other way and is project wide. Still has nasty bug "MIDI leaks". As I have explained in your other thread, any "smartness" for Control Surfaces is available throw ACT only.

azslow3
MIDI CC to you synth is not steered by "current" track but by the "echo" on the track, which default happens to be "switch echo on for current track".
 
Remote Controls work other way and is project wide. Still has nasty bug "MIDI leaks". As I have explained in your other thread, any "smartness" for Control Surfaces is available throw ACT only.

oh ok, so what is happening in my video is normal then?

Hi Azslow3,

I installed your software but it doesn't show up as a MIDI plugin.  I feel it didn't go to my VST folder and also didn't ask for it.
 
Thank You,
Adam

SilverBlueMedallion
I installed your software but it doesn't show up as a MIDI plugin.  I feel it didn't go to my VST folder and also didn't ask for it.

It is not a MIDI plug-in, it is ACT plug-in! And I recommend to start with Cakewalk plug-ins first. From my site, you only need "AZ ACT Fix" utility. It will help make your "ACT Learn" (do NOT mix it with "MIDI Learn") assignments persistent.
 
In general, for per SoftSynth control, I would recommend:
1) if the synth support "MIDI Learn" internally, use it.
Pro: do not need anything else, you record changes directly into the MIDI clip
2) if the synth does not support "MIDI Learn", use "ACT Dynamic Mapping". For that you should configure some ACT Plug-in to work with your hardware ("Cakewalk ACT MIDI", "Cakewalk generic surface" or "AZ Controller"), including "MIDI Learning" (nothing to do with VST plug-ins yet! that is completely different MIDI learn!). Then use "AZ ACT Fix" utility to create sane plug-in mapping environment. Then inside Sonar use "ACT Learn" for required parameters. Finally close Sonar and apply "AZ ACT Fix again".
With that, as soon as you focus some SoftSynth (note, not the track with it, the plug-in itself!), you controller will operate "ACT Learned" parameters for it.
 
I do not claim that using ACT is simple nor perfect. But that is Sonar's way to do things.
 

azslow3

SilverBlueMedallion
I installed your software but it doesn't show up as a MIDI plugin.  I feel it didn't go to my VST folder and also didn't ask for it.

It is not a MIDI plug-in, it is ACT plug-in! And I recommend to start with Cakewalk plug-ins first. From my site, you only need "AZ ACT Fix" utility. It will help make your "ACT Learn" (do NOT mix it with "MIDI Learn") assignments persistent.
 
In general, for per SoftSynth control, I would recommend:
1) if the synth support "MIDI Learn" internally, use it.
Pro: do not need anything else, you record changes directly into the MIDI clip
2) if the synth does not support "MIDI Learn", use "ACT Dynamic Mapping". For that you should configure some ACT Plug-in to work with your hardware ("Cakewalk ACT MIDI", "Cakewalk generic surface" or "AZ Controller"), including "MIDI Learning" (nothing to do with VST plug-ins yet! that is completely different MIDI learn!). Then use "AZ ACT Fix" utility to create sane plug-in mapping environment. Then inside Sonar use "ACT Learn" for required parameters. Finally close Sonar and apply "AZ ACT Fix again".
With that, as soon as you focus some SoftSynth (note, not the track with it, the plug-in itself!), you controller will operate "ACT Learned" parameters for it.
 
I do not claim that using ACT is simple nor perfect. But that is Sonar's way to do things.
 

oh ok, i was watching your youtube video where you see it in the plugin manager.