Komplete Kontrol midi out routing of internal plugins e.g. XO drums

Hi,

I’m trying to set up multichannel routing for XO while running it inside Komplete Kontrol within Bitwig. I’ve enabled the routing options in XO so that each pad can be sent to its own output, but in Bitwig’s mixer, I can only see audio activity on the main stereo channel (1/2). The extra output channels from XO don’t seem to show up at all.

Does Komplete Kontrol actually pass through multi-output routing from hosted plugins, or is it restricted to stereo only when used as a plugin inside Bitwig? I’d like to separate XO’s individual drums to mix them independently if possible.

Thanks for your help.

Find more posts tagged with

Komplete Kontrol SW

Accepted answers

All comments

Vocalpoint

Pretty sure that KK does not support multi out.

But I do use XO here and I just run it as a standard VST in Studio One with multi out no issue.

Thomba

Ok - Komplete Kontrol has quite a few downsides :-( :-)

Thanks

Vocalpoint

Well considering XO is not NKS compliant nor designed for Komplete Kontrol in any way - consider yourself lucky you can run it at all in KK.

Not aware of any actual NKS instruments that are multi channel.

Can’t do something it was never designed to handle.

JesterMgee

https://community.native-instruments.com/discussion/comment/243335#Comment_243335

KK does support multi-out for most plugins. I cannot vouch for KK V3 but V2 100% supports multi-out and I use it often with a few plugins, especially Omnisphere and layers.

XO also has a full NKS library available here (unofficial)

https://freelancesoundlabs.com/nks/xo

Sadly tho, XO does not appear to work with multi-out for whatever reason which is why I did not include a Multi-Out option in my library. I raised this with XLN Audio and they said it was an issue in KK and of course I did also raise this with NI but received the usual silence so the problem is related to KK as there are no issues with XO outside KK, it simply does not rout some plugins properly, likely KK V3 is the same problem. Same with some plugins like Avenger, while KK can see all the available parameters it does not pass automation to the host for 90% of them making it basically useless. Again, this is a long standing bug since KK implemented VST3 support but they have never acknowledged the issue.

Kymeia

https://community.native-instruments.com/discussion/comment/243366#Comment_243366

Yeah KK3 still supports it but as you say not all plugins work well and VST3 can be buggy

Quick links

Unanswered questions