Hey there.
I should probably have 2 threads. I have 2 questions.
 
1) Can Sonar record more than one parameter of automation at once? When I set Record automation, it lets me select what controller I want to record. Normally it set to record controller 9, volume, right? And then we can change that to what ever we want to record. But what about XY Pad type of control? What if I want to record a movement on XY Pad which has Cutoff and Reso parameters in "Up-Down-Left-Right" motion? Can such automation be recorded? (If you know what exactly I am trying to record- here is this beautiful BioTek software synth that has XY Pad as its main feature. Check it out- press Play- it is really fun! https://www.tracktion.com/products/biotek  I contacted Traction Tech support and they said- my DAW should be able to record movement and that they would be very surprise if my DAW is so limited to only record one parameter at a time).
 
2). I asked Traction tech support how to set Midi Learn to make controller control knobs in BioTek, and guess what- they say- my Host DAW should handle it. I know there is that MIDI Learn icon in every plugin window, but I rarely use it. It works for Cakewalk plugins, but most of 3rd party plugins able to Learn Midi CC when they detect it. I have tried to assign Midi Learn. I activated the Icon in Sonar, I moved the controller in BioTek plugin, then moved knob on controller keyboard. Nothing happens.
 
Now- Traction is DAW company. I can see why they would be happy to call Sonar limited and rob in the fact that it only can record one parameter at a time on Automation, and that it can not perform MIDI Learn. But are they right and Sonar is deficient, or is it their jib to make sure it works in other DAW if they sale it for other DAW and not only for Traction? Thank you.

To send midi to a VST you have to configure plugin as synth. I do this with TH3 and it works great.

Another alternative is to configure your controller in preferences and then use act. I think I have a video for this in my signature.

http://www.soundonsound.c...es/sonarnotes_0610.htm

It is a synth. Configure controller how? It is configured. It just that it does not respond to Midi CC when Midi Learn is activated. Not sure what ACT does- what is it for? Thanks.

https://www.cakewalk.com/Support/Knowledge-Base/2007013008/Configuring-the-ACT-MIDI-Controller-Plug-in

So, if it is a midi synth and you want to do automation, I would use the method described in this link if the controller you wish to use on the synth differs from the controller sending the midi messages the synth is playing.

Yes, you can record lots of concurrent automation.

This does not sond as what I am looking at. I was talking about MIDI Learn to make soft synth knobs receive MIDI CC data from hardware controller.
 How do you record concurrent automation at the same time if there is a dropdown menu that let you select whatCC# you want to record and there is only one option. If it is Volume, it only volume. Can you record lets say Volume and Pan at the same time?

I'm probably not best to answer - but hope this can help you  
 
https://www.youtube.com/watch?v=Ab__e6xqv08
 
I'm going through same type of issues myself w/new controller (novation impulse 25) which supposedly auto-maps each synth as well as DAW parameters, but not having much luck - always have to use midi learn/ACT & then save template or preset

To record the controllers, first check the synth is responding in the way you want to what the controller is sending. In other words, if you want, say. CC25 to control cutoff that the synth is set to CC25=cutoff. That's where the MIDI learn function can come in handy. Obviously lake sure the controller is selected as input for the MIDI track that feeds the synth, channels match etc.

If you then arm the MIDI track for recording and record as normal operating the controller knobs/faders/whatever all the controller changes will get recorded into the MIDI track. No need to select anything, the controller selection pulldown is for drawing envelopes and you're not doing that, you're recording MIDI. It works exactly the same way pitch bend and mod wheels get recorded into MIDI tracks.

Vlada, you're overthinking this, it can be done very easily. It only gets complicated if you want to assign certain controllers to certain parameters permanently, which I seldom need. What I want is fast, simple, real-time control when recording to add expressiveness. If that's all you want, here you go. I'll use Kontakt as an example.
 
1. Make sure your controller is set up correctly:

• Kontakt is receiving MIDI data from your controller
• Each knob generates a unique controller number
• The controller isn't sending out messages that the instrument already uses, like Controller 7. If it is you won't break anything, but depending on the instrument you may control two or more parameters at once. Controllers 20-31 are a good choice for your controller numbers as they are undefined, and are likely not already assigned. Controllers 32-63 are rarely assigned as well. 

2. Right-click on a Kontakt control. Either move a control and click on Learn, or click on Learn and move a control.
 
3. Record enable the MIDI track, and turn as many controls as you want while recording. The gestures will be recorded as MIDI data.
 
That's all there is to it. However, bear in mind that different synths respond in different ways. Not all work the same way as Kontakt although it's pretty typical. 
 
 
 

You, guys soooooo off! I do appreciate you trying to help, but this is not what I am asking. It must be me not explaining properly.
 
I know how to record keyboard controller knobs moves. That is not an issue. I also know that most of synth have option to click on graphic knob and it will open "Midi Learn" option and it will learn.
 
With Traction's BioTek- this does not happen. There is a reason I wanted you to watch that video. Look at this video at 1:14 and up. https://www.youtube.com/watch?v=AyxChtddSLU
 
Do you see this industrial city view changing to wild nature view when he moves the mouse? There is a big circular graphic in the center of plugin. The sound changes when we move mouse in XY Pad style, left right, up and down.
 
There is no Keyboard controller involved, only the mouse. I need to record mouse move. The only was I know to record mouse move is to activate automation. To activate automation, you need to set which controller to record. By default it sat to Volume. In case of virtual XY Pad as this synth offers, it would take 2 parameters- let's say Reso and Cutoff. Is there a way to record both parameters?
 
If I had XY Stile pad on my controller, it would make it easy, but I do not. I have to use a mouse as shown in the video.
 
The MIDI Learn in this plugin is not existent. Traction is a DAW, and BioTek soft synth likely relies on Traction's built in ability to handle Midi Learn for it. In Sonar- when I activate ACT, it does not learn, or I am not doing it right.
 
Thank you for your help.  

vladasyn
 I asked Traction tech support how to set Midi Learn to make controller control knobs in BioTek, and guess what- they say- my Host DAW should handle it.

I do not think so...

I know there is that MIDI Learn icon in every plugin window, but I rarely use it.

I do see it... Which Sonar version are you using?
 

vladasyn
There is no Keyboard controller involved, only the mouse. I need to record mouse move. The only was I know to record mouse move is to activate automation.

A kind of yes.
 

To activate automation, you need to set which controller to record. By default it sat to Volume. In case of virtual XY Pad as this synth offers, it would take 2 parameters- let's say Reso and Cutoff. Is there a way to record both parameters?

The simplest method is arm ALL, just deploy the latest updated in case you have already installed Manchester (there was a bug in initial release).
 
But let me explain how all that works because "Automations" have nothing to do with "MIDI learn", at least not directly.
 
A VSTi  has some parameters and own User Interface. On that user interface, VSTi can put some knobs, X/Y panels or whatever this plug-in wants to show to the user. By definition of VST standard, DAW is not aware what is going on in this interface not it automatically can see/control internal plug-in parameters. So, it is not possible for (any) DAW to implement "MIDI Learn" for arbitrary graphical element in VSTi interface.
 
VSTi normally response to MIDI events. Some of these MIDI events can be used to control parameters. Which events control which parameters is defined inside the plug-in, statically or by own "MIDI Learn". DAW has not influence on that. What DAW can do in that respect is map some MIDI events to some other MIDI events before sending them to VSTi. In Sonar, that is implemented by Drum Maps for Notes and MFX (MIDI FX) for any type of controls.
 
VSTi can also expose parameters as "Automatable". Which parameters and with which names are exposed is up to concrete VSTi. These parameters are named and have values in range 0. to 1. (floating point). In other words, they have absolutely nothing to do with MIDI.
 
Sonar let you record these parameters as automations, any number of them in parallel and independent what trigger the changes. That can be:
1) VSTi own user interface (VSTi inform DAW that these parameters are modified)
2) "MIDI Learned" controls within sonar, called "Remote control...", including:
2.a) automation Remote control, right click in the "box" inside opened Automation Lane
2.b) Remote control for Assigned Controls, read more about that there: https://www.cakewalk.com/Documentation?product=SONAR%20X3&language=3&help=SoftSynths.13.html
3) using Control Surface API methods, including:
3.a) direct control, for example user for Mackie Control (Universal (Pro)) and compatible devices
3.b) ACT Dynamic Mapping, used with other controllers. Check Chapter 40 in Sonar Reference Guide. In plug-in windows there is "ACT Learn" button, related to that method.
 
Apart from recording live, you can also just draw required changes in the Automation Lanes.
 
Also in Sonar it is possible to create MIDI Control Envelopes. They are represented in the track view and controlled the same way as Automations, but they function differently, they influence which MIDI events are sent to VSTi, the same way as Control Changes events in the clip.
 
I hope that has clarified a bit what is there...