Hi,

Congratulations for VEP7.

There is only one thing that will make me very-very happy with it.

I appreciate the new automation setup, but there is only  the"disable" function. It would be great if there is also the ENABLE function, so i can load my huge metaframe with no patch loaded (saving load time and ram) and then enable only the VEP7 tracks i need for the project using for example the expression maps for the tracks that are playing.

This little implementation for me will make the difference between a good product and a great product!.

Thank you

Marco

Several VePro Plugins used in Reason 10 can connect to only one server instance even if there are several more available - no difference over the network or locally. After connecting and disconnecting to one of the initially visible instances no instance at all is visible anymore in the "connect" window and even the initially connected instance is not visible anymore - while all server instances are still there but not connected.

This is no general network or firewall related issue. It works with other hosts. And it did work with version 6.

@lafauna said:

Does it suport VST3 plugins?

Sadly, no! And Steinberg no longer officially support VST2. VST3 plugins in the VEP mixer has been a long time coming and I'm very surprised its not been inlcuded in this release.

https://www.steinberg.net/en/newsandevents/news/newsdetail/article/vst-2-coming-to-an-end-4727.html

Late 2013 we announced that the Software Development Kit (SDK) for VST 2 would no longer be maintained and would only be available as subset of the VST 3 SDK. Five years down the line and this transitional phase is now also coming to an end.

From October 2018 onward we are closing down the second version of VST for good. While the  VST 2 SDK has been unavailable, and so have maintenance and technical support, the subset within the VST 3 SDK will also be omitted.

VST 2 compatibility with Steinberg VST hosts will remain, however, we recommend to root for the latest version of VST. VST 2 was introduced in 1999 and since then the technology has evolved dramatically. Since 2008, the SDK for the third iteration of VST, VST 3, has been available and since then efforts are focused entirely on the further development of VST 3.

“We appreciate that developers and users alike gravitate strongly toward the VST 3 interface that comes with many technological advancements. By bidding farewell to VST 2, we hope to offer everyone a clear direction,” comments Yvan Grabit, technology lead at Steinberg.

@lafauna said:

Does it suport VST3 plugins?

Sadly, no! And Steinberg no longer officially support VST2. VST3 plugins in the VEP mixer has been a long time coming and I'm very surprised its not been inlcuded in this release.

It's in the works, just didn't make it into the first release.

Hi, 

@richmn: "I love the idea of the VM1 (Beta) App and look forward to the 'Helper App' being available for Windows VEP servers.   Leading up to that, does the VM1 app allow us to select patches or parameters for any VST or just VSL instruments?" 

=> Patch seletction is not integrated (yet), but of course you can manage all installed plug-ins. 

@sui: "Upgrading to VEP7 broke the interface for me. I loaded a VEP6 instance and I get sound in Cubase just fine, but I cannot interact with the UI at all."

=> Do you maybe have some special font settings or other unusual tweaks? No troubles here on any of our Windows machines. 

@everen: "I appreciate the new automation setup, but there is only  the"disable" function. It would be great if there is also the ENABLE function, so i can load my huge metaframe with no patch loaded (saving load time and ram) and then enable only the VEP7 tracks i need for the project using for example the expression maps for the tracks that are playing."

=> "Disable" lets you enable and disable the chosen instances, folders and channels, of course. 

Best, 
Paul

@lafauna said:

Does it suport VST3 plugins?

Sadly, no! And Steinberg no longer officially support VST2. VST3 plugins in the VEP mixer has been a long time coming and I'm very surprised its not been inlcuded in this release.

It's in the works, just didn't make it into the first release.

Firstly, a gret release with excellent features etc (I meant to add that before my last note 😊 That's great to hear re VST3 being on yhe list. Any idea when it'll be implemented?

Hi fuzzydude, 

I'm afraid "asap" is the only answer I can give you there :-)

Best, 
Paul

@Paul said:

@sui: "Upgrading to VEP7 broke the interface for me. I loaded a VEP6 instance and I get sound in Cubase just fine, but I cannot interact with the UI at all."

The problem was that the old instance loaded in a separate window. Right-clicking the instance in the main server window and selecting "Snap Instance" put it back into the main window and now everything works as expected.

Hi sui, 

Thanks for the update, we'll look into that. Could you please send the project zo support@vsl.co.at (with the unsnapped window), so we can check?

Best,
Paul

VEP 7 - Didn't get more than one activation code so can only activate on one machine. Help!

Hi glasswing,

We have changed our licensing model with VE PRO 7, making licenses available separately, as the trend is definitely going to using a single machine.

Introductory upgrade prices for VE PRO 7 are:

75 EUR for the first license (comes with Epic Orchestra 2.0)
45 EUR each for additional upgrade licenses

Best,
Paul

Installed and producing sound, that is a good start. Will dig into it more in June, for now, its crunch time. Finals are mid May and then I am taking 2 classes compressed into 3 weeks at the end of May, ending the first week of June, so wont have time to play with this until mid-June, where I will be taking only 1 class starting the second week of June. The dreaded music appreciation class, which should be a breeze. Ironically, I already appreciate music, however, apparently, the college doesnt know that yet.

@FKV Studio said:

Well, I have a problem. I try to start VEP 7, I get an error that says "Please ensure that the 'bonjour service' is running before starting Vienna Ensemble Pro" and it does not start.How do I solve it?

Same problem here. Would appreciate to hear what the solution is.

Hi Dominique,

That should be solved with the latest update.

Best,
Paul

@Paul said:

Hi Dominique, 

That should be solved with the latest update. 

Best, 
Paul

Thank you for your response Paul. The update has but partly fixed the problem. I still get the same message about Bonjour service, but now if I click 'Ok' VE Pro 7 opens normally. Is there a way to get rid of the warning message?

Hi Dominique, 

I don't have that on any of our systems.
Which Windows version are you on?

Best, 
Paul

Hi Paul,

Thank you for the support. It is Windows 10 Pro, 64 bit, version 10.0.17763, build 17763. Here is a picture of the error message I am getting:

Bonjour Error

Simple solution: Just connect the instance with your DAW and everything should just work fine. It's a known issue with Kontakt.