vst Kontakt: more than 1 midi channel. Possible?
***Edit wrong words substituted***
Hi all!
I remember that Kontakt, as a [vst] object, cannot have more than 1 midi channel port (A).
As I need more than that, I'm looking for the best way to implement another set of instruments.
At the moment I'm thinking about having two [vst] objects, both on "A" port Channel, and then route my midi messages to the first or the second depending which instrument I want to play.
Sounds not ideal, but at the moment I don't *think* I have many more options. Do I?
Thanks for any feedback on this
What you remember is wrong ...
Kontakt can be used as multichannel midi sampler
All you need is to assign midi channel per Sampler instance.
oh, I would be happy to be wrong!
but actually it is Kontakt vst itself telling me that only "A" is available...
problem still remain, apparently...
I guess my question had a semantic problem, as I meant *ports*, NOT *channels*...
***edited *** just changed wording on my question
Ok, that clears it, you ask for more than 16 in one vst instance...
Then the limit applies as you describe it.
I see nothing wrong in using 2 vst~ objects, even that it doubles storage of fx banks
and midi routings.
At least a bit of logic could be used to apply _A and _B named fxbanks when storing them
and auto - reroute midi input on instruments assigned to second instance.
right, I think that [poly~] might be the way to go.
So I can avoid CPU usage for unused [vst]s
will give it a try.
Thanks for you feedback @sourceaudio!
i dont think that is a limitation which only appears in kontakt ;)
Sure, that is limit of midievents and raw midi, vst~ accepts only 1 input.
Would you be using more than 32 Instruments ?
I don't think Kontakt would consume CPU on non sounding voices,
only in case you have some effects in use.
I don't think poly is really needed, might just complicate the
whole thing.
disable and bypass messages would also do
@roman: oh, so it is a Max problem/limitation ? sounds like a perfect feature request then! ;-)
@source: [vst] patchords, even if not carrying signal/sounds, will always be processed 44200 times per second, AFAIK...
So in my opinion it's a safe bet using poly~.
That is the only way a signal patchcord will not consume CPU at all if poly voice is muted
there is nothing what could force hosts or plug-ins to allow more than 16 channels only because the VST 3 SDK would allow it.
what i dont understand is why kontakt shows only the ones which are allowed and disables the others. there are no others in vst~, because there are no ports, so why disable them? little communicaiton problem between host andplug-in i guess.
imagine max would allow to use channel 17. how would kontakt know about that when it it made like it is, only checking its host, which is the vst external. ? ;)
many hosts only have 16 or 32 channels per plug-in.
i understand why 100 could be great now that there are more and more MPE in virtual devices comes around the corner.
but as long as we can also not send parameter control for dozens of channels individually, sending midi notes on many channels seems uninteresting.
loading more than once instance of the plugin seems adequate. unless you have an instrument preset which uses 17 channels. then i dont know what happens.
@roman, thanks. As for Kontakt showing what could not be used, perhaps it is a scaling problem from standalone to vst. Maybe save coding? The company does amazing sampler, but in my opinion their UI and Mac integration is from the past decade, nothing really improved much for years. I hope the Apple Silicon version would force them to rethink it. But I'm getting too far in the OT kingdom here. ;-)
So, actually I should ask if there is some statement/rumor/info from Cyclings about the Apple Silicon version of Max. Would be nice to know! And I hope would prepare the road for max running on iPads and iphones(!?)