wst3
so VSL uses the 'real' multi-port feature as specified in VST3. Do you know what Kontakt is doing with their 'extra' three sets of MIDI ports? Is there perhaps some way to provide access to them?

 
From what I can see the A/B/C/D ports of Kontakt are only accessible by using the standalone version of Kontakt.
There is no multi input port support in VST2 and Kontakt doesn't support VST3 yet.

Thanks for clearing that up Noel.

Noel Borthwick [Cakewalk]
From what I can see the A/B/C/D ports of Kontakt are only accessible by using the standalone version of Kontakt.
There is no multi input port support in VST2 and Kontakt doesn't support VST3 yet.

Of course you are right... sorry for the false alarm!

I am glad someone posted this.  I just updated my VSL software to VEP 5 that supports multi midi input.  It was a feature that I was really looking to forward to using in X2.  Only afterwards did I realize X2 doesn't support VST3.  I wasn't planning on upgrading to X3 as there wasn't anything useful for me in the upgrade except VST3 support.  When I realized I needed it, I downloaded the demo only to find that it still doesn't work.  Thanks for clearing this up.  I was about two minutes away from spending money on an upgrade that would have been useless to me.  I do believe that multi midi input is an important feature of VST3 that is currently missing in Sonar.    

Nitrox32
I am glad someone posted this.  I just updated my VSL software to VEP 5 that supports multi midi input.  It was a feature that I was really looking to forward to using in X2.  Only afterwards did I realize X2 doesn't support VST3.  I wasn't planning on upgrading to X3 as there wasn't anything useful for me in the upgrade except VST3 support.  When I realized I needed it, I downloaded the demo only to find that it still doesn't work.  Thanks for clearing this up.  I was about two minutes away from spending money on an upgrade that would have been useless to me.  I do believe that multi midi input is an important feature of VST3 that is currently missing in Sonar.    

This is what happened to me and I push the buy button. I dont even think about situation that CW doesnt implement this VST3 feature. I really dont see more important feature of VST3 than this. Almost all {including sidechain} can be done in VST2.5. But what is worse, I am going to pay again to CW for this feature, because they are not going to include it in X3. I see this situation as not new feature request, but as bug fix. It is similar to buying DAW software without record function.

'It is similar to buying DAW software without record function.'

No it really is not at all similar. Record is essential, this is a 'nice to have'.

So your NI use case has been put to bed (you need to lobby NI for VST 3). So what VST3 plugins are you using right now that needs this? What exactly are you trying to achieve right now?

To be honest I'm not seeing this feature request every day in these forums. Yes if you want it you are going to pay for an upgrade. Just like everything.

Now you may have a point that perhaps cake need to specify better that it is not fully VST3 compatible. I'm not sure if they do this or not. Over to Noel.

CakeAlexS
So your NI use case has been put to bed (you need to lobby NI for VST 3). So what VST3 plugins are you using right now that needs this? What exactly are you trying to achieve right now?

You should read whole thread, I am not talking about Kontakt I dont using it. I am talking about Vienna Ensemble software. And what I am going to achieve? Better computer performance of VSL resource hungry machinery by opening whole orchestra in one instance of VE. If you search CW forum you can find request of this functions several times over past years...

When it's case of priorities it will be either be a choice of getting new features for free or getting stuff like this fixed. You will see many of these issues posted several times over as well in the forums, Cake I think have enough on their plate right now, would you say your issue is priority over all of this?
 
You may wish to consider opting for a DAW which is more tailored to your requirements. Right now I think Cake has given you a direct answer, you will probably get what you want on the next full release. Good luck with your choice or sticking with what you have (sorry it isn't the answer you want).

Bug fixes aside, I think it would suffice to say that Cakewalk (or any other) should implement the features of a standard included within a build in full or not at all. Not a partial inclusion of features of the standard only to be figured out by the end-user at a later time.

Amen!