In case we choose the cloud solution (which I personally would prefer) does that mean we can activate only one computer - or maybe more? With libraries growing bigger and bigger it does sometimes make sense to split up a library between 2 (VePro) systems. And it's meanwhile common that plugin developers allow more than one activation - e.g. Soundtoys.

As far as I recall it was somewhere mentioned that support for VST3 plugins would come to VEPRO.

When will will this happen? 

Same behavior here with Reason 10 on OSX High Sierra

However it works with Live on the same machine.

Can't be a network thing - otherwise it wouldn' work with other hosts in the same environment.

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.

If this is the case I won't upgrade. This is a downgrade with a price tag.

You guys realy know how to turn off existing customers - especially after the Synchron Strings release desaster.

And as many mentioned: Epic orchestra is completely uninteresting for the majority of your customes since they own the sounds already or have bigger and better libraries.

Agreed. This complete ignorant behavior is simply insulting. 

Last Library from VSL for me too.

Just watched the video.

Did that guy in the first row cover his ears through the presentation? :D

I hope we'll get some more videos with better sound.

Frankly, this is unprofessional. It must have been clear for a very long time that the release date could not be reached at all. We are now talking about "parts" in december. Why should a part be usefull at all? Early bird does not justify that - but it generates revenue based on false promises. This is a kickstarter campaign with Apple attitude.

With Bitwig and Reaper two serious DAWs launch(ed) on Linux. Will we get a Vepro VST plugin for those in the near future?

I don't want a vepro server for Linux but being able to connect the Linux DAW via the VePro plugin to a Windows server would offer the Linux world all availaible windows/Mac plugins.

Thank you!

In Reason 9.5 VST support was introduced.

VEPro runs only - pretty bad - with zero buffer. This puts much stress on the cpu and produces tons of crackling etc. Everything above a zero buffer sice does not work.

The public beta of 9.5. was slightly better but I am not aware of any significant changes.

VEPRO ist not working in Reason 9.5.

I can use it loacally on the same machine (what does not make much sense) but only with zero buffer and switched on delay compensation in Reason

It's completly unusable over the network even with zero buffer.

It seems that it's not reporting latency over the network within Reason.

Working with Reaper and Studio One.

I have an issue with Ableton Live - the VePRO Plugin does not find the server and the window stays empty. Not sure if I am doing something wrong here since I am new to Live.

Rewire support for the Server - i.e. connecting Reason on a slave machine would have been great. Or even better a VEP rack extension for Reason to be able to use VEP directly in Reason.

One usability thing that I would like is that the midi port numbering is related to inserting a plugin. What I mean is that most users use multitimbral plugins - e.g. Kontakt - with VEP which need one port and several midi channels of this port. When I insert several Kontakt instances the Midi Port of VEP stay alway at the same number (number 1) and I have to manually change this portnumber to a different port after I inserted for example Kontakt. It would be nice to have some option setting so that VEP raises the port number with each inserted instance automatically.

Although VEP is not intended as a DAW I would like to have an option to record the audio of the main out or even several outs to disc - maybe even with a metronome/click precount in the first bar. I use the standalone version of VEP with Reason and trigger VSTIs in VEP via midi. It would be great to be able to record the audio performance within VEP to be able to transfer the files later to Reason for mixing.

How are you doing this?

Today I was trying out U-He's plugins in VST format for Linux and they work great within Bitwig Studio. Practically all the plugins are now available for the Linux plattform.

It would really be nice to have the VEPRO plugins - of course not the server - as Linux VST plugins to be able to access a VEPRO slave machines from a Linux audio machine.

It hast been asked for some while ago, so I bump this question again.

Can we have Rewire support for VePro to be able to move Reason to a networked PC?

It could be a Rewire Plugin or whatsoever.

Having a rack extension for Reason that could connect to a VePro server would also be nice.
Maybe the new RE SDK makes this possible now.

I use VePro also standalone on the same machine when using it with Propellerhead Reason. But with huge Kontakt templates things get difficult very fast. Regarding PC slaves you don't need to invest big money. An high clocked i5 is sufficient. I use a cheap regular harddrive (who cares how long the slave needs to start up) for the system and a single SSD for the samples. It's more important to have a separate network card for use with VePro.

You need seperate machines. Stick with the Mac for composing ans use cheap PC-Slaves for playback. I have an old Mac for composing and the effects work and PC slaves for sample or synth playback with VePro.
While sampele streaming is no issue with SSDs anymore - scripting in Kontakt is a CPU issue.
Some libraries like Spitfire and Cinesamples need very much of your CPU for the scripting.
This may explain yous cpu spikes because at a certain position of you musical piece less or more scripting is needed.
Depending on your used mic position you'll probably playback thousands of voices and release samples. This also needs CPU power - at least with Kontakt. A large number of Kontak instances do also need not too little CPU time for just "hanging around" in idle mode doing nothing at all.

I would too be interested to hear if this is still impossible.

The SDK has evolved and Reason has now midi out. Maybe Karel can check again if it is possible now. With the new midi module of Reason 7 it is a nobrainer to send midi to a (localy running) Vepro Server. Midi sync with Vepro is also working fine. The big deal is to get the audio from Vepro in the Reason mixer. The thing needed is "only" an audio input RE from Vienna.

Thank you.

I realized that I can not tryout Vienna Suite because I've tested it a long time ago (years?) whe it came out and had less plugins. This should be changed. Od course it should not be pssoible to use the testversion over and over again. But when there are years passed it should be possible.

Does Vienna Suite in Connection with VePro run on all slaves or is it a license that is valid for only one slave? Or in other words do I have to get 3 VSuite licences for 3 VePro slaves?

I use VePro standalone midisynced to Reason sending midi from Reason. Since routing the VePro audio back into Reason causes significant latency, I'd love to have some simple audio recorder / track in VePro to record the Output into a wav file that can be reimported into Reason. I'd be perfectly happy with a single stereo track recording the master out of VePro.

I have to add that this seems to be a problem affecting Windows only.

I'd appreciate any Vienna response to this.