First of all: For me VEP7 is a big hit! And maybe future updates support VST3....

I like to know if I'm the only one using VEP with Bitwig. I use VEP adhoc to offload CPU. So the plugin/automation updates are a relief! Allthough it seems that de parameter name doesn't sync to Bitwig the first time it's added. Connecting to an instance with automation allready in place does show the parameter names.

Other issue I have is 'tick' in the audio stream from VEP every 2-3 minutes. With Bitwig I'm used to low (128) buffers. Raising thwe buffer to 512 is less ticks, but I can't resolve it completely. Also adjusted the VEP plugin buffers. 2 buffers give 512ms latency. Should this be less or more then the interface buffer size? I don't understand how a VEP buffer size of 'none' would result in latency. Maybe I'm missing some fundamentals ;-)

Also, same rigg with Cubase (9.5) I have never ever had any ticks from VEP. So maybe it's an issue in Bitwig,

Cheers

Hi,

Good to hear v7 is here! Is it possible to demo the new version?

Regards,

Martijn

Originally Posted by: fatis12_24918

 

To be very honest I'm a bit surprised by the large discussion about licenses: actually if you own VEP 6, you may update 1 licence + EO2.0 for 75€ and if you need to update all the 3 VEP 6 licenses you just buy 2 more single licence update at 45€ each. What's wrong?

Total cost is easy to calculate, and I don't think it's just a bad policy change, the opposite it has some advantage as well (e.g. if you don't need additional licenses or if you need just 1, you will pay according your real need, not being forced to the batch).

What's a bit weird instead is the almost total lack of technical features explanation, but we are not forced to buy today:

the people buying today just trust VSL for the previous good experience with VE Pro, and hope it will keep the standard. Due to the fact VEP is the core of my system I had no doubt about using the last version available, because the actual one starts to be unstable and conflicts with recent OS and VST updates are day by day more frequent, so a VEP software update was really welcome if it just makes the program solid and compatible again.

Any additional feature beside stability and compatibility is very welcome, but not the core motivation factor for me. I just hope VSL will not disappoint the trust... in case they will do, of course next time I won't buy any pre-order anymore (as I won't pre-buy anything from Synchron series after being disappointed by Synchron Strings I).

Very simple, isn't it? :)

YES! What about the new features? 12 pages of upgrade fee frustration, but will there be a marvelous plugin manager?? VST3 support? ASIO guard solution? Which value for money ;-)

Would there be a performance difference if I run 10x VSTi in one instances or 10x VSTi each in it's own instance?

I used to have instances with some VSTi's in it. For example 3x Massive, 3x Zebra2, etc. in one instance. Another instance for 3x Kontakt, etc. But most of the time I don't use these instances so it's a waste of channels and cluttering audio/midi tracks and especially automation in Cubase.

So I'm thinking about creating Cubase Track Presets for stereo-out Kontakt and multi-out Kontakt (VEP instances), loading an empty Kontakt in Vienna and configures the audio/midi in Cubase. After that I load the required Kontakt lib on VEP server instance. Each non-multi-timbral VSTi (Massive/Zebra2/FM8/etc.) gets it's own VEP instance the same way.

I would need arround 20 of these instances. My questions are (in comparison with the same amount of VSTi in just 4 instances):

- Would this create unnecessary overhead in Cubase?

- Would this create unnecessary overhead in VEP server?

Cheers,

Martijn

One more thing we would like to point out at this stage: with the release of the VST 3.6.11, the SDK for VST 2 has officially been discontinued. We are happy that third-party developers are now looking forward and will continue VST plug-in development with  the SDK of VST 3.

Source: https://www.steinberg.net/en/newsandevents/news/newsdetail/article/vst-3611-sdk-now-available-4906.html 

I guess the main advantages Steinberg created VST3, but for me personal having only VST3 plugins installed for consistency. I run VEP also on the same host as Cubase. Now I need to install also VST2 on that host. But I understand this isn't a strong business case for Vienna to implement VST3. 

The adaptation of VST3 is verry verry slow. If I'm correct Native Instruments isn't VST3 at all. A small amount of plugins are VST3 only. See: https://forum.reasontalk.com/viewtopic.php?t=7508745 These are probably new developed plugins, cause rewriting excisting plugins could be an intensive job.

But a plugin manager would be much much more appreciated :-)

Cheers,

Martijn

Is perhaps VST3 support anywere on the priority list?

Good to hear!! 

I realy would like VEP utilized with a (Cubase like) plugin manager. Seeing all UAD (mono+stereo) plugins via an oldskool menu is a real workflow killer here. I thought VEP6 would eventualy get such a feature, but I can't find the post anymore. 

@developers: When can we expect a 6.1 update? With a plugin manager 

Thanks Marnix,

I will then check again what must be the problem or maybe some specific circumstances. Good to hear it should be possible!

Regards,

Martijn

Could somebody perhaps confirm this is by design behaviour?

I can't move/copy an insert FX from an instrument track to a bus. Isn't that odd? I need the same setting so now I have to save as a preset to insert on a bus. Feature request?

Cheers,

Martijn

Hi,

I'm researching a switch from Cubase 8.5 to Bitwig. Seems you have a reasonable workaround for this issue. Are there any other mentionable issues with VEP6 you are aware of?

In Cubase I use a lot of VEP6 (VST3) instances with track presets. Most of the VEP channels are individualy routed to Cubase channels (mostly 8 to 12 channels per instance). All firing up with a template. Would this workflow work in Bitwig2?

Thanks in advance

Martijn

Hi,

I just started using VEP6 but had some crashes yesterday while connecting from Cubase 8.5 to VEP6 x64 server running an instance with instruments allready in it. Didn't have any crashes with VEP5 in the past. 

Do others have problems with connecting to allready opened VEP6 instances?

Regards,

Martijn

So VEP will never again work optimal with Cubase? Steinberg will never change it's engine in favour of one 3th party developer..... Hmz...

It would be more clear if you stated VST2 instead of VST. It is also something you would never expect as a customer: The plugin itself is VST3 and the server software doesn't support VST3's as a plugin. 

I'm not a programmer at all, but is it that much work to support VST3 within the server software?

Regards,

Martijn

Hi,

Are the ASIO guard 2 problems (silence when switching tracks) with Cubase 8 fixed in VEP6?

Still no VST3 plugin support within VEP server?

Regards,

Martijn