No biggie Kamikaze. It's all in the spirit of helping. (Nice screen print with colored text!! 👍) I personally have never used simple instrument tracks so I can't vouch for their reliability or functionallity for that matter except for just now playing around with it for help in this thread. I don't doubt that it normally works correctly. Could just be a freak event. Even so, I personally like the extra control of split tracks and the fact that it reminds me of the old school days of synth hardware when you actual had a midi track, then an audio track from that synth. When I'm gonna mix, everything is bounced or frozen and I hide the midi tracks to de-clutter.

Vdorn, For fun, I created a Simple Instrument track to see what would become of CC7 data. For me it automatically used CC7 for the Kontakt volume slider, with 127 being 0db. Makes me wonder if you accidentally recorded a CC7 onto your Simple Instrument track. The way to check for that is to either double click the midi data in your simple instrument track OR click Views, Piano roll view... might have to click Tracks, pick tracks and select the track you wish to view. Check the CC7 Down at the bottom of your Piano roll view, you might have to zoom out to find a stray CC7 causing the volume issue. You can then delete all CC7 and the Kontakt slider will remain where you put it, OR delete all CC7 and then draw in the volume yiu wish to acheive at the beggining of the song. Just a thought.

Blogospherianman
Vdorn, For fun, I created a Simple Instrument track to see what would become of CC7 data. For me it automatically used CC7 for the Kontakt volume slider, with 127 being 0db. Makes me wonder if you accidentally recorded a CC7 onto your Simple Instrument track. The way to check for that is to either double click the midi data in your simple instrument track OR click Views, Piano roll view... might have to click Tracks, pick tracks and select the track you wish to view. Check the CC7 Down at the bottom of your Piano roll view, you might have to zoom out to find a stray CC7 causing the volume issue. You can then delete all CC7 and the Kontakt slider will remain where you put it, OR delete all CC7 and then draw in the volume yiu wish to acheive at the beggining of the song. Just a thought.

Ok, here is the continuation of the story.

At my very first post I mentioned, that I checked all controllers events in the Even view of the problem Trumpet track (including the hidden events), so I think it is completely equal to deleting of CC7 control in PRV.

But... I did it one more time and the story repeats. The volume is down to about minus 18 db any time I restart Sonar. I opened a new doubled track, copied the date there - the same story.

The only one thing that really worked, was setting the CC7 controller to about 127 near the first piece of the Trumpet playing. When I see the slider in Kontakt, it stays on minus 18 db, and then jumps to 0 db. Apropos, minus 6 db was definitely not enough, so I wonder whey they set it by default in Kontakt.

I didn't do it before, because I was scared that it will interfere with the Console volume. Now I understand that it is something different, so I will probably just do it any time I have the same problem...

As for now, I don't see any reason to open doubled tracks for Kontakt instruments, but I admit I could use for fututer, if it would become necessary.

Thanks to everybody, who took part in the discussion. Now I have one more problem changing of the articulation of the instrument inside of one track. I have read that the best way is to use keyswitches. Could anybody explain me in the very easy way how to do it? I just need a simple change of articulation in a certain moment of the song...

I will try not to edit this post, since it looks like the editing just erases it completely, and than comes the problem to post it again. Seems to be a bug of this forum...

First, do yourself a favor and stop using Instrument Tracks.
 
Users used to complain that other DAWs had this feature, and therefore SONAR should, too. So CW added it. However, Instrument tracks offer zero additional functionality beyond saving screen real estate (not I problem most of us needed a fix for, because we put MIDI and audio into separate track folders and collapse the ones we're not working on). What it does do is hide some useful features and confuse others.
 
Internally, you're always going to have separate tracks for MIDI and audio, regardless of how the DAW presents them. It just makes more sense to actually see them and treat them as separate things, which they are. One benefit is that you don't have to fight a software synthesizer for control - just automate the volume (or pan, or whatever) on the MIDI track and you're in control.
 
As for why Kontakt defaults to -6 dB (or is it -12, I forget), that's to assure adequate headroom for mixing. In practice, you don't want any track to actually hit full scale. However, most Kontakt instruments' samples are already set to sensible levels, and a few are set to frustratingly low levels. At times I've had to tell Kontakt to max out at +6 or +12 dB to compensate for low sample levels, knowing that the instrument will never actually hit that. That's why I changed the global default to 0 dB (Options -> Engine -> "Default Volume for new instrument and volume reset") and control the actual volume via MIDI automation.

bitflipper
First, do yourself a favor and stop using Instrument Tracks.
 
Users used to complain that other DAWs had this feature, and therefore SONAR should, too. So CW added it. However, Instrument tracks offer zero additional functionality beyond saving screen real estate (not I problem most of us needed a fix for, because we put MIDI and audio into separate track folders and collapse the ones we're not working on). What it does do is hide some useful features and confuse others.
 
 
Internally, you're always going to have separate tracks for MIDI and audio, regardless of how the DAW presents them. It just makes more sense to actually see them and treat them as separate things, which they are. One benefit is that you don't have to fight a software synthesizer for control - just automate the volume (or pan, or whatever) on the MIDI track and you're in control.

Well, that main thing why I use Simple Instrument Tracks is navigation. With 34 tracks in my recent song (not counting the hidden ones) it is important. So, I would need a sort of a breakthrough in my track navigation system. As for now I use only Hide option.
I know theoretically, that it may be made by using Lens or whatever, but I wouldn't like to experiment now by myself. If I would find a video on YouTube with the system to organize doubled tracks, I would be thankful and probably change the system.

bitflipper
 
As for why Kontakt defaults to -6 dB (or is it -12, I forget), that's to assure adequate headroom for mixing. In practice, you don't want any track to actually hit full scale. However, most Kontakt instruments' samples are already set to sensible levels, and a few are set to frustratingly low levels. At times I've had to tell Kontakt to max out at +6 or +12 dB to compensate for low sample levels, knowing that the instrument will never actually hit that. That's why I changed the global default to 0 dB (Options -> Engine -> "Default Volume for new instrument and volume reset") and control the actual volume via MIDI automation.

What is interesting, I have default volume set to 0 db in Options, but any time I add a new instrument the volume is set to minus 6 db and I need to go to Edit Mode - Instrument Options - Midid Controller range to set it to 0 db.

vdvorn

bitflipper
First, do yourself a favor and stop using Instrument Tracks.
 
Users used to complain that other DAWs had this feature, and therefore SONAR should, too. So CW added it. However, Instrument tracks offer zero additional functionality beyond saving screen real estate (not I problem most of us needed a fix for, because we put MIDI and audio into separate track folders and collapse the ones we're not working on). What it does do is hide some useful features and confuse others.
 
 
Internally, you're always going to have separate tracks for MIDI and audio, regardless of how the DAW presents them. It just makes more sense to actually see them and treat them as separate things, which they are. One benefit is that you don't have to fight a software synthesizer for control - just automate the volume (or pan, or whatever) on the MIDI track and you're in control.

Well, that main thing why I use Simple Instrument Tracks is navigation. With 34 tracks in my recent song (not counting the hidden ones) it is important. So, I would need a sort of a breakthrough in my track navigation system. As for now I use only Hide option.
I know theoretically, that it may be made by using Lens or whatever, but I wouldn't like to experiment now by myself. If I would find a video on YouTube with the system to organize doubled tracks, I would be thankful and probably change the system.

bitflipper
 
As for why Kontakt defaults to -6 dB (or is it -12, I forget), that's to assure adequate headroom for mixing. In practice, you don't want any track to actually hit full scale. However, most Kontakt instruments' samples are already set to sensible levels, and a few are set to frustratingly low levels. At times I've had to tell Kontakt to max out at +6 or +12 dB to compensate for low sample levels, knowing that the instrument will never actually hit that. That's why I changed the global default to 0 dB (Options -> Engine -> "Default Volume for new instrument and volume reset") and control the actual volume via MIDI automation.

What is interesting, I have default volume set to 0 db in Options, but any time I add a new instrument the volume is set to minus 6 db and I need to go to Edit Mode - Instrument Options - Midid Controller range to set it to 0 db.

Yes, I agree. Best not to use Simple Instruments with Kontakt. It is a very powerful device being the most outstanding Sampler on the market. Having to deal with Velocity Layers, Key Switching, Drum Maps, Scripting. For example, as you blow harder into sax or trumpet it not only gets louder but the dynamics changes as well. Midi volume can be mapped to velocity sample layers. You need to articulate that sound different to the relative audio level in the mix. Does it take up too much real estate? So is golf.
 

As for articulations, I use CC5 in Cinematic Strings. I assigned that number to be the CC controller. CS has its own list of art's, each with their own number. I'm guessing your VSTi has something like this also. So, you need to figure out how to use it.
 
The other way is to use key-switches, assuming the VSTi has them. I prefer CC events, as I use staff view and don't like the weird things that happen when you put in a note 2 octaves below the bass clef.
 
Another comment on the volume problem: I'm thinking you have competing ways of controlling volume in use, which are interfering with each other. I would eliminate all but one method. for me, that is CC events, but most people use other method. Pick the method that you like to use, then get rid of the others.

michael diemer
As for articulations, I use CC5 in Cinematic Strings. I assigned that number to be the CC controller. CS has its own list of art's, each with their own number. I'm guessing your VSTi has something like this also. So, you need to figure out how to use it.

Well, I have figured out that the desired articulations have numbers D0 and Eb0. Where do I put this note to make it working?
 
 

michael diemer
Another comment on the volume problem: I'm thinking you have competing ways of controlling volume in use, which are interfering with each other. I would eliminate all but one method. for me, that is CC events, but most people use other method. Pick the method that you like to use, then get rid of the others.

I wanted to understand the system, but it looks like it is too complex. So I just put about 127 for CC7 in PRV for Trumpet Section midi track and will do it again if the problem repeats...

CC127 is fine for start volume, especially if the VSTi is low volume to start, as some are. But you should then use CC11 for on the fly adjustments.
 
As for the notes, D0 and Eb0, these are actual notes. The "0" refers to the first octave, so they are way down there. you can put them in manually in staff view by hovering your mouse cursor way way down, until that note shows in the view that tells you what note it is; and then change it if incorrect in Note Properties. You can add them in PRV and change to correct values the same way. You can even add them in Event List, by hitting the insert button on your keyboard, then changing the event to the correct note. you should add a keyswitch at least one measure before it is needed, if possible. Otherwise, add it at the very end of the preceding measure, so it doesn't affect the last note in that measure. Be aware, however, keyswitches don't always work. that's why I prefer CC events. but your instrument has to have them, obviously.
 
Another way to do it that is foolproof: just add another midi track and set it to the desired artic.

michael diemer
As for the notes, D0 and Eb0, these are actual notes. The "0" refers to the first octave, so they are way down there. you can put them in manually in staff view by hovering your mouse cursor way way down, until that note shows in the view that tells you what note it is; and then change it if incorrect in Note Properties. You can add them in PRV and change to correct values the same way. You can even add them in Event List, by hitting the insert button on your keyboard, then changing the event to the correct note. you should add a keyswitch at least one measure before it is needed, if possible. Otherwise, add it at the very end of the preceding measure, so it doesn't affect the last note in that measure. Be aware, however, keyswitches don't always work. that's why I prefer CC events. but your instrument has to have them, obviously.
 
Another way to do it that is foolproof: just add another midi track and set it to the desired artic.

I just had a Teamviewer session with one experienced Sonar user, he explained me the articulation changes. It seems to be very simple - just add a note in the PRV of the track. The only thing was that the number can be not correct for PRV. I my case it must be not D0, but D2.
 
He adviced me also to reinstall Sonar (since some features are not working) and learn a new way of starting the project, based upon 16 midi tracks with the audio tracks as an addition. I will probably try to do it, especially because it is not hard to move the tracks contents from the old project to the new one with correctly organized structure.
 
I have now more that 16 Kontakt instruments, so may be the problem with the volume is connected with the fact that some midi channels are doubled or so...
 
Thanks a lot one more time for everybody who participated in the thread.