Question about plugin routing, stereo and mono

Hello, I’m attempting to route this instance of Kontakt to different channels in Renoise. As you can see, I have a bunch of stereo pairs in Kontakt, but after Bus #5, Renoise only sees mono inputs, and splits the stereo outs from Kontakt across separate busses.

I have found a temporary workaround: I just route say Bus 6 and Bus 7 to separate channels in Renoise, hard pan them, then route them to a send so I can say, EQ them as a stereo pair or whatever. Or I just start another plugin instance :smiley: So it’s really not a show-stopper, but I’m curious if there might be something I’m missing, since I tend to work with a lot of routing.

Has anyone encountered anything like this and might have any suggestions? Thanks!

So I believe I found the solution to my problem already, just posting it here in case anyone else encounters it.

Anytime I loaded a new instance of Kontakt in Renoise, under audio routing I only had 5 stereo buses followed by the rest in mono. However, in the nifty Kontakt presets button, you can configure all the Kontakt routing you want and set it to load by default. I set up 32 outs and as soon as I did that, when I loaded a new instance of Kontakt, I immediately had all the stereo buses I needed. :slight_smile:

So I believe I found the solution to my problem already, just posting it here in case anyone else encounters it.

Anytime I loaded a new instance of Kontakt in Renoise, under audio routing I only had 5 stereo buses followed by the rest in mono. However, in the nifty Kontakt presets button, you can configure all the Kontakt routing you want and set it to load by default. I set up 32 outs and as soon as I did that, when I loaded a new instance of Kontakt, I immediately had all the stereo buses I needed. :slight_smile:

I was in a similar situation many months ago, also with orchestral libraries and I solved it as you describe.Just a suggestion, in case you can use it:

Apart from routing the stereo channels to tracks and groups, you can use the “VST alias” when necessary for not to overload the RAM memory (to change the channel number, so each track works with a separate channel, or use groups to share native effects).This way you can load many more libraries without loading many times the Kontakt. This is fine for large projects. Use you “VST alias” also?A good suggestion to control it is to enter the processes section in the Task Manager of Windows, and see how many AudioPluginServer32.exe (Renoise Plugin Server) are running.

Yes! I use vst alias a lot. I end up trying to find a happy medium between balancing the load across CPU cores and filling up every instance of Kontakt as much as possible. Next step, perhaps running Vienna Ensemble Pro in Renoise since it takes care of all the load balancing for you. :smiley:

I was in a similar situation many months ago, also with orchestral libraries and I solved it as you describe.Just a suggestion, in case you can use it:

Apart from routing the stereo channels to tracks and groups, you can use the “VST alias” when necessary for not to overload the RAM memory (to change the channel number, so each track works with a separate channel, or use groups to share native effects).This way you can load many more libraries without loading many times the Kontakt. This is fine for large projects. Use you “VST alias” also?A good suggestion to control it is to enter the processes section in the Task Manager of Windows, and see how many AudioPluginServer32.exe (Renoise Plugin Server) are running.

Is there a specific reason why you want to load all those instruments into one instance of Kontakt, rather than just loading multiple instances of Kontakt? With modern CPU’s there isn’t the same concern as their used to be about the extra load from multiple instances, and as far as RAM is concerned, it’s the same either way, your kontakt patches will eat it whether they’re in one instance, or many.

Just curious, because it seems that simply using multiple instances (it’s how I do it with kontakt libraries) would make your issues, as posted here, moot.