SOLVED: VST3 please

I want easier configuration of dynamic input and outputs. Better communication with the host is now available.

Thanks.

 

Arturia started to supply their first VST3 instruments! NI please join the movement

 

Please NI , give us Drag and Drop Cubase -> Kontakt VSTi ....

 

This is really getting a big PITA, I am not even interested to upgrade to any recent version of Kontakt since there is nothing added but FLUFF I don´t need.

How about adding some MEAT and making this VST 3.5 so I can use it with Cubase with the expression tools and note expression?

Stop wasting time doing sample libraries and FX fluff, rather try to keep up with current standards ( in fact VST3 standards from freakin´ 2 0 0 7 !)

 

If you will notice, there's still comparatively very few VST3 plugins on the market. The reason: a lot of developers don't find it necessary or enticing to create VST3 plugins, because not all DAWs support VST3. You always have to wager the amount of work necessary to port something to VST3 (which is a lot of work because the whole framework is different) to the amount of users actually using any of those new features. I wouldn't call VST3 "standard" before all or at least most DAWs support it. What most DAWs support now is VST2, so VST2 can be called "standard". But VST3, nope.


Personally, I don't need VST3 at all, and I don't think Kontakt would gain much with it really. Note expression? Fancy name for keyswitches, really.

 

+ 1 for vst3

 

Look, if you don't have a clue what you are talking about, you really shouldn't participate in a thread.

No, this is not about fancy keyswitches, this is about things that are possible with VST3.5 like having controller values changed on single notes instead of globally on a MIDI channel like in 1989.

[ame="http://www.youtube.com/watch?v=uXI-DI0RhXk"]Cubase 6 - Single Note Controller Editing Feature | SOFTPLANET LTD - YouTube[/ame]

I already use this in Halion since 2011 but it is impossible with Kontakt libraries because Kontakt is still VST 2.4

VST3 is out since 2007 and 3.5 since early 2011, we are approaching 2013 and NI is taking a nap.

VST3 is supported by major platforms Cubase, Nuendo and Presonus Studio One.. heck, even Fruity loops is a VST3 host.

Waves plugins have VST3 versions since 2009. Also there is a truckload of VST3 plugin developers, DMG, Fabfilter, izotope, Melda, brainworx, Melodyne, Melda, Nugen, Arturia and a bunch of others.


You get the idea.

And yes, I refuse to buy any update which is not up to current standards but packed with fluff instead of updated core technology.

 

I know what VST3 offers. And I still think that Kontakt doesn't need it really. Scripting allows per-note adjustments if that's really necessary, and there's poly AT support in modulation system.


Ask yourself why Camel Audio, u-he, and other more famous developers are NOT going the VST3 route.

 

more famous than Waves?

 

Waves is way overhyped, there are better plugins than Waves out there.

 

u-he is going the vst3 route........ Zebra will be first... check u-he on kvr forum.

 

well, you were the one saying there are "more famous" developers not going the VST3 route than the truckload of devs I mentioned, as you see U-he is on the list too, now what?
Waves, as the most famous plugin dev doesn't count because they are "overhyped" according to you? Yeah, sure.. let's leave it at that.

I'd prefer someone from NI to reply here instead, clarify when Kontakt finally gets VST3 with a release delay of epic proportions, and when it is finally worth to purchase an update.

 

VST3 comes for many developers, but unfortunately most are still blocked with x64 work...

What VST3 might bring to Kontakt? Improved dynamic output channel assignment, creation, etc. Currently Kontakt does not sit nicely in my DAW. There is room for improvement and user experience simplification.

 

Waves is definitely not the "most famous", by what statistics are you basing that on? It's definitely most overhyped, since there are some free plugins that can be a lot better than them (see Variety Of Sound).

 

EvilDragon: concentrate on the good and let us know what it is ;-)

 

VST3 is not required to make pads light up in pretty colours and is of little use to djs, therefore it will remain low on the list of priorities.

 

As for VST-3

Supporting 64 channels would be welcome.

Expression Map is Key Switches but more complicated.

And Note Expression is more trouble than it's worth.
Would have been nice if pitch bend could work on individual notes when arranging choral parts
But as pitch bend is still global even in VST-3.x

Individual channels are still much easier to score.

 

Microtuning data is per pitch. This is available in VST 2.4 but Kontakt does not respond correctly to it.

 

+1 for the 64 midi channel support

 

I can see how VST3 support would be helpful to you, but I would suggest that VST3 is not supported by most DAW platforms.

Please feel free to correct the following:

VST3 DAW Support
-----------------------
ProTools -- NO
Cubase/Nuendo -- YES
Logic Pro -- NO
Sonar -- NO
Ableton Live -- NO
FL Studio -- YES
Digital Performer -- NO
Presonus Studio One -- YES

I think it gets down to cost/benefit. Until most all DAWs support VST3, many plugin developers won't worry about it. The fact that Steinberg published the VST3 standard in 2007 is irrelevant.

Just look how long it took all DAWs and plugin developers to support 64-bits? Many only support 64-bit VST plugins, not their standalone versions.

In the end I think it all boils down to money.