That's a big problem for VEP.... whatever you do "pop orchestral film..." kontakt is always here.....

do not use VEP in the meanwhile

use the Kontakt inside your DAW

Originally Posted by: Bill

Yes, confirmed. VST3, AU, AXX only

It's really high time that VEP runs VST3. Same goes for M1/M2 support. I understand that there are companies like FabFilter, who adapt to new trends and technologies super fast, and others don't. But this is lagging so far behind now.

Originally Posted by: Lucy

Until now, VEP not hosting VST3's has been a cause of some frustration for me, and a worry for the future. It's now become a major problem. 

The time has come VSL; you simply must give this the utmost priority.

Please?

I feel the same.....no excuse for being so far behind the curve with VST3.

On Mac you get less CPU load if you use AU/VI instrument

Originally Posted by: jesus_calderon_679

PLEASE, Vienna, update VEP7 ho host VST3.

It's a shame that now we can't use Kontakt 7 as VST (the most used tool for media composers in the world) in your software. We need an EAT as soon as possible. Big disappointment and frustration.

iZotope has stopped making VST2 versions, Neutron and others are VST3 only...
And Kontakt will also be VST3...

The good plug-ins for me have recently become VST3 only, and VEP without VST3 support has become a software that I cannot use even if I want to use it.

I hope VST3 will be supported as soon as possible.

If more piled on +1s help VSL to prioritize this, here's another :)

With Steinberg pushing hard to kill off VST2 and major platforms like Kontakt 7 following suit, VE Pro needs to add the ability to host VST3 plugins soon. It can't be the universal host that we continue building large orchestral templates with if it can only host older plugins.

Even for instrument plugins that still offer VST2 + VST3, I hesitate to continue building large VEP templates with the VST2 versions, because there will be so much manual effort required to rebuild those templates with the VST3 versions in the future.

(Also new developers haven't been able to obtain licenses from Steinberg to release VST2 plugins for quite a few years now, so VEP has been locked into the grandfathered developers club -- an unfair and unfortunate situation).

Can anyone from VSL at least confirm that this will be on the roadmap? (I very much understand not wanting to promise any specific timeline).

Thanks!

- Eric

Originally Posted by: Dewdman42

VSL has already stated numerous times on this forum that its on the roadmap, but there is no timeline they can give at this time for when exactly we will see it.  They have already told us a dozen times, they are working on it.

OK, great.

Originally Posted by: Dewdman42

One thing you need to understand is that VST3 is a huge change from VST2 in terms of how its coded in any VST3 hosting app..  Its not a small change.  Its a very very large change, especially for a sophisticated host software such as VePro.  If it were an easy thing to add, I'm sure VSL would have released it already a long time ago.

Of course. It's not a trivial change, but it's also a much smaller scope feature than say switching your deeply ingrained software licensing system or adding 3D audio support, so this has to be mainly a question of prioritization. (I've spent a lot of time writing MIDI software and dealing with the annoying differences across audio plugin APIs, so I'm very familiar with this particular problem set -- as I know you are too).

Originally Posted by: Dewdman42

In the meantime, I suggest you consider using a sub-hosting plugin for K7 as a work around.  DDMF MetaPlugin, DDMF SuperPlugin, Kushview Element, PlogueBidule, perhaps even KompleteKontrol, are all possible plugins which come in VST2 form and can host VST3 plugins inside of themselves..which will essentially allow you to use K7 inside VePro7 right now.

I have a few of these -- I guess I'm just hesitant to add yet another layer of nesting (DAW => VEP => Wrapper Host => Actual Sample Player). Has to add at least a small bit of memory + CPU processing overhead, adds additional clicks to the already arduous process of large orchestral template building, puts critical reliance on another manufacturer+software staying up to date with OS compatibility issues, etc.

Originally Posted by: Dewdman42

Myself, I am still basically avoiding VST3 plugins.  I'm still using K6 and have no "pressing" need to run out and get K7 any time soon.  The VST3 spec also has some interesting design problems that can sometimes affect midi in problematic ways that does not exist with VST2, so me personally I always choose VST2 whenever possible and I will continue to do that as long as I can until it truly becomes a situation such that for example, there may be some sample library that only works on K7 which is only VST3...  But we're just not there yet, there are really only a few isolated situations where VST3 is a hard requirement.

It's not a hard requirement right now, but there will come a point in the not too distant future where it is, so before investing tens/hundreds more hours building new large templates, I'd rather future proof as much of that work as possible. I do save sample player specific preset files, of course, but even just the work of having to load a new plugin format and call up each one of those presets across dozens of libraries is going to be mind numbing.

So I'd prefer to start using VST3 plugins in VEP as soon as possible, even when that means having to deal with annoyances like choosing keyswitches instead of MIDI CCs for more reliable articulation management because of those VST3 design quirks.

Originally Posted by: Lindurion

So I'd prefer to start using VST3 plugins in VEP as soon as possible, even when that means having to deal with annoyances like choosing keyswitches instead of MIDI CCs for more reliable articulation management because of those VST3 design quirks.

Oh and on this point there is something to point out.  Its good that you are aware of this!  In the case of Kontakt, it doesn't matter if you are VST2 or VST3; as Kontakt itself has some of the same design flaws as VST3 in the midi implementation of its VST2 version also.  In other words, some of the VST3 problems are also present in Kontakt VST2.  Not all..  but some.  So with Kontakt, avoid CC switches period.

Something else I want to point out.  It is NI's decision to drop their VST2 version of Kontakt7.  There are very few plugin developers who have made that decision so far.  Steinberg has of course been heavily pushing this, but there was no forced reason for NI to drop the VST2 version of Kontakt7 other then their own decision to do so.  

Additionally, I will just say that its highly probable it would have been much easier for them to continue supporting a VST2 version of K7 in addition to VST3....then it is for all hosts out there to upgrade to VST3 hosting.  The latter is a much much more complicated, difficult and expensive endeavor to do.  Perhaps Steinberg is behind pushing NI to do this, hoping it will force more hosts to get better at hosting VST3 (shrug)...we don't know....just speculation.  But anyway my point is, make sure to let your feelings known to NI also!  They could have just as easily, if not far more easily...released a VST2 version of K7, compared to expecting all hosts out there to drop what they are doing and implement full VST3 hosting...which is usually quite a complicated matter for some of them.  In fact its still not too late for NI to reconsider and release a VST2 version perhaps. It doesn't hurt to ask them too is all I'm saying.