• SONAR
  • Problem with Kontakt routing - solo one channel, all channels solo
2017/01/08 13:22:38
obiwanshinobi30
I'm using Kontakt orchestral libraries to work on a piece. I have three Kontakt instances, one each for strings, brass, and percussion. When I click on the Solo button for the trumpet's MIDI channel (as an example), ALL of the instruments in the brass instance of Kontakt become solo'd, not only the trumpet which is what I'm expecting to happen.
 
I've checked all of my Kontakt audio routing and it seems fine, as do the MIDI channel and audio routing in SONAR.
 
Anyone have any ideas? This is making it virtually impossible for me to do FX processing.
2017/01/08 14:20:42
ralf
Sonar cannot know what midi input channel is mapped to what audio output channel inside of Kontakt. If you solo one midi channel that goes into Kontakt, Sonar solos all audio channels that come from that Kontakt instance.
 
However, if only one midi track is soloed, you should nonetheless only have that instrument playing, because the other instruments in Kontakt don't receive midi input. As an alternative, you can solo the audio track for that instrument (which automatically solos all midi tracks that go into the same Kontakt instance).
2017/01/08 18:42:33
obiwanshinobi30
Makes sense, ralf. What was hanging me up, however, was when I applied an EQ to one of the instrument audio tracks, it would affect all of the other tracks. It was causing lots of problems.
 
I ended up having to bounce all of the tracks to their own audio tracks, then applied EQ, etc... and finished. Here is the track, for whatever it's worth: https://soundcloud.com/joshsager/kings-coronation
2017/01/09 08:21:09
dcumpian
Well, for what it's worth, that isn't how it work,s for me. If I solo the midi track, that channel is soloed. It sounds like you have all of your instruments going into Kontakt on the same midi channel. Don't do that.
 
Dan
2017/01/09 10:37:49
obiwanshinobi30
Dan, 
 
I assure you I have everything on separate MIDI channels. That's why I am so confused and prompted me to seek help.
2017/01/09 11:01:42
Slugbaby
obiwanshinobi30
Makes sense, ralf. What was hanging me up, however, was when I applied an EQ to one of the instrument audio tracks, it would affect all of the other tracks. It was causing lots of problems.
 
I ended up having to bounce all of the tracks to their own audio tracks, then applied EQ, etc... and finished. Here is the track, for whatever it's worth: https://soundcloud.com/joshsager/kings-coronation


Another assumption:  You have each Kontakt instrument going to it's own Audio track in Sonar?
Where are you applying the EQ?  If it's in the FX bin of an audio track that's specific for one instrument, it should have no impact on any other audio tracks...



2017/01/09 11:05:29
obiwanshinobi30
Correct assumptions, Slugbaby. Each Kontakt instrument going to its own audio in Sonar, EQ applied to each respective audio track. But it was bugging. 
 
I'm wondering if it has anything to do with a related problem I posted about a few weeks ago where audio routing was getting jumbled when I added more than five instruments. 
 
I don't know. In the end I was able to do what I wanted, but it was a bit cumbersome and I want to understand what's happening more than just fixing it to finish a tune.
2017/01/09 11:11:27
Slugbaby
I've never experienced your issue.  Perhaps it is Kontakt getting overloaded?  I've never used more than 3 different libraries in one instance.  
Does this happen if you put each instrument into it's own Kontakt session (or <5 per session)?
2017/01/09 11:30:07
obiwanshinobi30
I haven't done extensive testing, but it seems - at least in this case - to not matter how many instruments.
 
Mind you I haven't yet created a new project in Sonar to do a bunch of tests. I think that's my next step. I will be perfectly happy for this to be an isolated incident. 
2017/01/09 15:21:49
brundlefly
Did you by any chance start with Kontakt inserted as a Simple Instrument, and then clone the track? SONAR really shouldn't allow cloning Instrument tracks because they are by definition a combination of one MIDI track and one audio track with a soft synth linking them.  The GUI allows it, but cloning an Instrument track does not clone the synth instance as it should, and it creates hidden linkages between track controls that can produce unexpected results like this.
 
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account