Hi
 
I'd like to ask if midi keyboard's volume fader should affect playback on Sonar.
It happens I'm recording some midi notes and I noticed that if I change the volume fader it changes the volume on the playback also.
On other hand, if the softsynth does not respond to volume fader (midi CC 7), then nothing happens.
 
The reason I'm surprised is that I thought that it would just happen if automation was enabled.
I also noticed that any change on midi controller's fader or wheel will show up on track's midi meter.
 
Could it be related to my system configuration - Windows 10 vs. M-Audio Key Rig 49 (legacy keyboard)?
 
Thanks in advance.
 
Best regards

Most controls on your keyboard generate MIDI messages. That is also true for the fader or the wheel.
For Sonar, all that information is in the same stream as used for keys, I mean it is recorded into MIDI track and it is sent to VSTi. If your VSTi can interpret CC7, it react on it. Usually controlling the velocity/volume but theoretically can be something else (can be "MIDI learned" in some plug-ins).
 
By default for Sonar MIDI messages have no special meaning or interpretation. But you can:
1) in Sonar preferences "MIDI / Playback and recording" you can select which type of MIDI messages you want record
2) you can MIDI learn Sonar parameters, that is called "Remote control..." in the right click menu for control. Check the latest tip from Craig ("Beyond MIDI learn") for possible use case.
3) you can instantiate some Control Surface plug-in in Sonar Control Surfaces preferences (ACT MIDI/Generic surface) and learn you control there. If some MIDI message is assigned as a Surface control, it is no longer recorded/sent to VSTi.  Big advantage over "Remote control" is flexibility and no dependence from the project. For example, you can set your fader as Sonar Volume control for track and then switch which track is controlled using WAI (color indicator in the track and console views).

It's normal during playback or any other time for a track that is echo-enabled. Check for that term in help or search. There are two normal ways for tracks to be echo-enabled.

Hi, azslow3
 
Thanks for your response! I was reading Craig's article about Midi Learn and it's very cool. I also used ACT midi / Generic Surface, which is a bit complex, imo, but it did work sometimes.
 
Actually the midi recordings and automation remote controls are working fine, but I guess the problem is I can't move the fader during the audition, otherwise it will affect the mix.
I tried to find some midi automation enabled, but found none.
 
I guess I'll give ACT midi / Generic Surface another try, but I'm thinking the Mix Recall could solve the problem (although I didn't used it yet ).
 
Best regards

Hi bvideo
 
Thanks, that worked!
I changed the focus to another midi track and it worked.
 
Best regards

As I have mentioned, ACT MIDI/Control surface completely block the messages.
Note that in case you use both at the same time (many users do), controls assigned to the first one in the list will not be blocked (CS bug).
 
Theoretically, "Remote control..." should also block them. Practically it does not (another bug).