Solved Kontakt 6.6.0 Cubase 11 Pro - Messed up outputs

Are you sure this approach does not solve it for you? Can you please try saving an output configuration using "save for all targets", this will over-write the incorrect vst3 default configuration, and everything should be working as normal.

 

Yaron and I triaged this a bit further, here's a quick rundown:

Kontakt stores an output channel configuration for each plugin type (AU, VST, etc). When you FIRST load the new version of Kontakt as a VST3, there is no output configuration present (since you've never saved one for VST3 before). We SHOULD be using the old VST configuration so all the migration goes smoothly and everything is the same.... The bug here is that instead, we're just loading a weird default configuration instead - so your old VST2 project is expecting one channel configuration, but get loaded with an entirely different one. Now all your channels are being routed incorrectly. An easy indicator you're having this problem: on my system, the `outputs_vst.cfg` and `outputs_vst3.cfg` files in my Kontakt configuration / app settings folder are a different size! These two files should always be the same, since (for the time being) we only save them together. If they are different, then you'll potentially get a different output config depending on whether you load VST2 or VST3.

There should be an easy workaround: in the new version of Kontakt, simply re-save the VST configuration you want (via Preset/Batch Configuration -> Save Current Output Section -> VST). This should save a correct VST2 and VST3 configuration, and overwrite/avoid the weird default configuration. Then when you load a project, all channel configurations should behave as they did before.
I believe this should even fix things after you've loaded an old project and migrated the plugins, but I'm not 100% sure of that (we just tracked this down) - it would be helpful to know what ya'll see.

Also, keep in mind that changes to your output config only take effect after you close and re-open the plugin / project (there's usually a warning dialog that gets displayed). Make sure to do this when testing, to avoid muddying the waters.

 

I am not a huge help atm, because I went back to the latest legacy version. But for those, who do need an urgend workaround, the downgrade worked fine. On Windows at least, you have to rename or remove the kontakt.vst3 manually, It resides in the default program folder under /common files/vst3/
Good luck

 

Yes, but not right away, since I already downgraded. I was afraid to loose the entire weekend, but I'd be happy to give it a shot next week.

***Now I'm extremely curious***

 

Hi there,

I've encountered the same situtaion, Im on win10, Cubase Pro 10.5.
Kontakt output messed on the 3rd stereo output, its now permanently surround 5.1...
and deleting channels doesnt change anything at all, its always surround 5.1..

is there a solution for this?

I am unable to change channel 5,6,7,8,9,10 to stereo or mono channel
when i try to configure within cubase output (or kontakt), stereo3 always shown a surround 5.1 (see attached png)

 

I am having the same situation, have you found a way to fix this?

Hi there,

I am also on Win10, Cubase 10.5, but doesnt matter how many instances I open, the third is always 5.1 output..
Do you have to map them to different channels when you set up the 16 stereo outputs?

thanks

 

Read what Scott @ NI wrote above.

 

Hi Scott,

if those two files should always be the same, would it be suitable to simply copy and rename the vst2.cfg? While Kontakt is not running, of course.

Thanks for your efforts!
Peter

 

I think yes, that stands to reason, since Scott said the two files should always be the same.

 

I'll give it a shot tonight

 

yes it worked!!

thanks a lot guys!!

now i can open older projects without having a heart attack Lol

 

I coudn't wait and can happily share that this solution worked.

On Windows 10, simply go to the folder below (user is your username) and make a copy of your outputs_vst.cfg and rename it to outputs_vst3.cfg

C:\Users\User\AppData\Local\Native Instruments\Kontakt\default

Thanks alot, in the end a very easy fix, if you know where to look for .

 

Very glad to hear everyone.

We will make sure to roll out a proper fix for this soon, stay tuned fro 6.6.1 where this should not be an issue to begin with. Apologies to all!

 

We're all humans after all and nobody rolls something like this out on purpose.

Cheers and have a nice sunday, at least.

 

Sorry, to open this up again, but I'm continuing to have problems even after the fix...

The outputs in kontakt are now correct, but routing to them from individual instruments (specifically Spitfire instruments, so I've posted in their forum too) doesn't work as expected at all.

I imagine this is a Spitfire issue rather than a Kontakt one, but thought I'd post here in case anyone has any thoughts or is experiencing something similar.

Working in Cubase 11, Windows 10.

 

Hello, unfortunately I have experienced that the work-around from Scott works only for the standalone version of Kontakt.
The plugin doesnot work as it should be. The same output issue here. My question is how I can roll-back to earlier version eg. 6.4 (which worked perfect) for my plugin in Cubase. I have uninstalled 6.6.1 version and installed 6.4 but still, I get 6.6.1 in my Cubase.!?

 

In the plugin version you just recreate the plugin outputs and save it as new default for the plugin (VST or VST3 depends which one you're loading). Should work then.