SOLVED: Please add VST3 thank you!

Please add VST3 thank you!


I'm surprise that Native Instruments haven't already?
You are leader on all other kind of technology together with SOFTTUBE so its strange that you limp in this matter?
Why haven't you add VST3 compatibility already? You can't say its no point only Cubase / Nuendo support it even though that should be enough of reasons.

AAX support only Pro Tools 11 and that you have no problem to add. If I'm not mistaken there are more users on Cubase / Nuendo / Studio One, FL Studio + more...platforms that do support VST3 already then it are users on Pro Tools 11 or Pro Tools 10.


As for today more and more DAWs support VST3 like Studio One etc. So its not just Cubase and Nuendo anymore.


Thanks in advance!


Best Regards
Freddie

 

Well spoken

+1!

 

VST3 support would be able us to use more then 16ch of MIDI of Kontakt.


As you all notice we have already PORT A,B,C,D MIDI in Kontakt. We can't use them though because NI Kontakt is still in VST2.4.
When NI update to VST3 all MIDI Ports would be able to be used in the DAW.

That is just one benefit with VST3. ;-)

As you all perhaps already notice Steinberg has now official end the Support of VST2.4, 2013.
So now NI must update all instruments to VST3. They have no choice! Finally and its about time!!!



Best Regards
Freddie

 

This is not true. Those who have VST2 SDK can still use it to create new plugins. Steinberg does not limit that. This just means that no updates will happen to VST2 SDK - which is really no big deal, since VST2.4 was the last update from more than 5 years ago. So, you completely misunderstood what Steinberg did there.

 

Yes you are right, but Steinberg finally did something to try to end this madness keep holding on to this outdate VST2.4.
VST3 has been out in over 5 years now... AAX 3 month and that they update right away?


There are more users and people on VST3 platform then Pro Tools 11 or 10.

Its "okay" if they want to add AAX support but add VST3 first. If you ask me the priority is totally wrong here!


Also the "crap talk" that there are no benefits with VST3.5 VS VST2.4, obviously they don't know what they talk about.
Try Cubase 7 x64 with VST3 and you will never want to go back to use any VST2.4 plugins anymore.


FXs Automation or any kind of automation (on single key "note"-based) would be a breeze with Kontakt 5 if they add VST3 support. Today we keep using Key switches? VST3 would be very helpful in completing those tasks like make Symphony Violins change play behavior or change different type of FX in example Evolve bundle library.

Not change the whole instrument behavior as today. Make it only affect the sound playing on the "single key" example key D3 only. The possibilities are endless.


Best Regards
Freddie

 

I wouldn't be so sure about that. In any case, VST3 doesn't seem to be a priority for NI at this point in time, but AAX2 is. The pitfalls for VST3 are greater than you might imagine. Check out developer discussions on KvR about why VST3 isn't that good as you might think it is.

 

I am not a developer and can't speak intelligently about the SDK, etc., but I will say that it would be great to use Note Expression in Kontakt (and Reaktor, Absynth, etc....)
There are some nice features with VST3. I hope they get it sorted out.
J.L.

 

I just kindly ask if NI can update all your VST2.4 plugins so it support VST3, VST 3.5.2 also, thank you!
That's all!

I don't know but as far as I know it shouldn't be so hard to do? Update to AAX support takes much more work compare to adding a VST3 version.

They should be able to compile a VST3 version instead of VST 2.4 version in the "VST Audio Plug-Ins SDK" (Version 3.5.2)
http://www.steinberg.net/en/company/developer.html


Instead of compile a VST2.4 you select VST3.5 version instead. That's it. I don't know why you need to be so stubborn against it?
What's wrong with options? Waves and many other software companies get it. VST3 is here to stay, move on...!



Best Regards
Freddie

 

It is not that easy as you think it is. Otherwise it would have already been done. VST 3 is coded completely differently in comparison to VST 2.4, and changes are not trivial.

 

Okay, fine. Does it take 7 years to program and add?

This is more or less just ridiculous. AAX2 x64 you are willing to add in a heart blink, still there ARE THOUSENDS, perhaps MILLINOS of more people/users that can benefit from VST3 support then AAX2 support.


Host that support:
AAX2 x64= only Pro tools 11!

Host that support VST3= Cubase, Nuendo, STUDIO ONE, SONAR X3, FL STUDIO, Vienna Ensemble, Wavelab, Audition, Bitwig Studio, N Track Studio, Sequel, V-raxtor, VST Host, SAVI-Host, Menu Magic, AudioFinder, Plugin Update,SampleRobot Virtual Cable, Automap..

more to come... (Reaper); (Samplitude);.....





Best Regards
Freddie

 

Another benefit of vst3 if implemented is dynamic plugin processing. I.e. If kontakt is instantiated as vst2 plugin it will eat CPU cycles even though it's not playing anything on a track. Vst3 won't use CPU cycles until a midi note is triggering a kontakt instance.
AUs and AAX64bit are doing this already vst3 Vienna Ensemble Pro and Instrument as well.

 

I don't know what you all talk about or WHAT NI IS WAITING ON?
Seems pretty straight forward to me. No extra program skills needed to add a VST3.x format.

Steinberg focus their efforts entirely on the development of VST 3. The latest SDK--------------> RENDERS SOFTWARES IN VST 3.x, VST 2.x and AU format.

//Timo Wildenhain continues: "The VST interface is extremely popular throughout the world of music production and recording, and the latest enhancements in VST 3.6, such as Inter-App Audio compatibility, pave the way for an even wider acceptance."//

 

Are you a programmer? No? Then you don't know what you're talking about. It is anything BUT straightforward, as VST3 is completely different than VST2 in its very innards.

Yes, but only if you STARTED CODING SOMETHING AS A VST3 PLUGIN! This is not the case with any NI plugins, and things need to be completely recoded to fit VST3 topology. This is NOT easy. VST3 SDK will NOT take a VST2 plugin and magically make it VST3 - that's an asinine assumption.

 

Cool!

Thanks for explain that it isn't so easy as a "press of a button".

"Program" everything for scratch?
So isn't that the same they need to do with the new AAX2 x64bit version from AAX1 x32 or RTAS version? NI needed to program everything from scratch again and still they seem to manage to do that. But they can't do that in 8 years time with VST3? It must be extremely hard to program VST3 plugins....still all others like WAVES, SoftTube, SPL, Fabfilter etc seem to mange to do that.


The funny things is their are still more NI USERS and more DAWs that would benefit from a VST3.x version then any AAX2 x64bit version. If you still think "PRO TOOLS" is the "KING" you must have been living under a rock the last decade.


So to recap!
--->We that want VST3 support has waited for almost 8 years. Still no VST3-version yet.
--->Pro Tools users waited for 2 month to get their new AAX2 x64 version.

Its something seriously wrong here!!!? If you still don't think so you must drink AVID KOOL-AID to breakfast!



I like "EvilDragon"... I really do. See you around stranger!
Best Regards
Freddie

 

No, it's not the same. Differences between AAX 32-bit and AAX 64-bit are much, MUCH smaller than differences between VST2 and VST3.

 

+1 Vst 3.5 are the way to go nowadays. Hopefully it will be supported soon.

 

In my earlier requests (and regrets) for various VST support I discovered that even if a certain version of VST is "supported" the features themselves have to be implemented one by one. In my case it was polyphonic note tuning support (microtonal tuning in Cubase/Nuendo), which is part of VST 2.4. No go.

 

More then + 1.000.000 users that can benefit from VST3 technology.
There are more users that can benefit from VST3 support then Pro Tools AAX format...

 

The benefits of VST3 are pretty obvious when dealing with large samples, multi-threaded processors and independently side-chained instrument channels. Computers today are more powerful than they were 5-6 years ago and VST3 lets the users take better advantage of that power.

 

Kontakt already uses multithreading with VST2, VST3 would make no difference.

In any case, VST3 doesn't seem to be NI's priority. I can't say I blame them.