Having the same problem here. Using Bitwig with VEPro.

Discovered a workaround. After changing an instrument inside a VEPro instance, I open the VEPro plugin window in Bitwig and rename the "instance name" by klicking on the blue box (e.g. I rename "Piano1.0" into "Piano1.1). Now when I save the song, the changes inside the VEPro instance are also saved.

By the way: I don't have this problem when I use VEPro inside Studio 1. There all changes are saved correctly.

@DaddyO: thanks, that helped me a lot, too.

You could try the "Always On Top" utility from Dropbox. Download under http://dl.dropbox.com/u/...nloads/always-on-top.zip

After starting this programm, click on the VEPro Window, press Ctrl+Space and VEPro shouldn't be hidden anymore.

Best regards,

Peter

Hi DG,

thanks a lot! You are right, "Number of midi inputs" is a speed factor. For testing I have reduzed this value to "1" and now it is quite faster (1 second instead of 5).

I am using 16 instances. Some are containing up to 60 instruments, other only 10. All together about 400 instruments. If they are all loaded in VE Pro, I have no problems. But if I connect all instances with cubase, I get cpu spikes from time to time. That's the reason I am testing several setups. I have read that the vienna team suggests to use one big instance instead of several small instances. Anyway I want to try a setup with many instances which can be modular connected/disconnected.

Best regards,

Peter

Hi all,

I load a project in cubase. In the "Vienna Ensemble Pro Server" window I see how the single instances are connecting. It takes about 5 seconds for one instance to be connected. Is this a regular value? Or is it too high?

My settings:
Audio outputs: 10
Midi Inputs: 8
Audio Inputs: 2
Latency: 1 buffer
Cubase 6.5 and Ve Pro Server 5.0.10738 on the same local mashine
All instances saved and loaded "preserved" and "decoupled"
No firewall and no virusprogramm activated

Hi civilization3, thanks for your answer. But I have both on local mashine, VE Pro and sequencer. It's a powerfull working station with 2 processors (16 cores) and 48 GB Ram.

Even if I play no sound and the transporter is stopped sometimes all 16 CPU cores raise to 100%. Then after one minutes the spook is over and the CPUs calm down (to average 30%).

Only If I disconnect all VE Pro instances the problem doesn't occur.

Hello there, I have exactly the same problem. Sometimes asio-meter is raising to 100% and all my 16 CPU cores also raise to 100%. Then after 1 minute everything is fine again.

Are there any news how to fix this problem? Of course I have the latest updates of VE Pro, Cubase etc.

Great, thanks!

Hi Karel,

i created a new instance (32-bit), inserted 6 instruments (6 x RealGuitar2), selected all instruments and deleted them at once -> and VE Pro crashed at the first try. The same on the second try.

Best regards,

Peter

Hi Karel, I will test it this evening when I am back at home.

Hi Karel,

deleting several instruments at once still crashes Ve Pro (using Public Beta 4.0.5814). It doesn't matter for me, but I think this info would be interesting for you.

Best regards,

Peter

Superb, thanks a lot!

I also have often crashes when deleting instruments or busses.

But with a little trick I can prevent the crashes: I move the intrument which I want to delete to the end of the list (by drag and drop). Then I can delete it without problems.

VE Pro is already now an excellent app. But with this feature it'll be a really killer-app! Thanks for the info!

Hi Karel, many thanks, that's great!

Hello Vienna-Team,

I have a suggestion for a next update. I always work with both, the 32-bit and the 64-bit Server. I place both panels next to each other. When I close VE-Pro the window position is saved - but for both panels with the same value. With the effect that when I restart the 32 and the 64bit Server Windows, both panels overlap each other because they have exactly the same position.

So, is it possible to save the position of the 32-bit and the 64-bit Server-Windows seperatly? I know this is not an important thing - but if it is easy to change for you it would be a great improvement for us ;-)

Best regards,

Peter

Hi Vienna-Team,

I just detected your remote controls, which make it possible to change VE Pro's volume, pan and sends from the host sequencer (i.e. with the "Quick controls"). That's an amazing feature, thanks a lot!!

Do you think it's possible to control more than 4 sends in the future (for example 8 sends). That would be great!

By the way: There are a lot of "Dummy"-Values (i.e. "Dummy 1-1-0" ) in the quick controls. Do they have any meaning? Unfortunately I didn't find anything about this great feature in the manual .

Best regards,

Peter

Hi Daniel001,

I found out that editing of saved metaframes is very buggy.

Don't edit a (loaded) metaframe and save it. You risk to damage it. Only save completely new, reestablished metaframes. It means: if you want to create and save a metaframe...

1. create a blanc metaframe (File->Clear All),

2. add as many instances as you need,

3. fill this instances with your instruments (loading of saved projects is ok!)

4. save this metaframe.

If you reload this metaframe everything should be allright. But don't edit and save this metaframe again, in my case it often crashs after reloading (in combination with "Play")!!!!

With this rules I managed to get VE PRO and Play worked again.

Best regards,

Peter

I was so happy because Play always worked with VE Pro, even with the version 4881. I never had any problems.

Last week I updated VE PRO to version 5436 and since this time VE Pro always crashes when playing a Play-instance. Loading a Play-instance is ok, but after playing some notes it crashes.

So I changed back to version 4686 but I still have this problem.That's very strange. Maybe the reason for this problem is at a very different point, for example new (automatically) Win7-Updates, or other things I don't see at this moment. I have to investigate this problem.

Great update, thanks a lot, Vienna-Team!

Peter,
Munich

Great news, Paul, thanks a lot! Best regards to the complete team!

Peter

Very good news and great improvements! Thanks a lot, VSL-Team!

Today I had the same problem that Vienna Ensemble Pro could not find a license on startup. I think it has something to do that I removed a device from USB-port yesterday. The elicencer seems to be very sensitive when changing anything at the USB-port.

I reinstalled "eLicenserControlSetup.exe", then it worked again.

Best regards,

Peter

My first song I compose will be a love song dedicated to VE Pro and the VSL-Team ;-)

Do you have too many audio ports defined? You find this parameter in the VE Pro Server window under 'Preferences > Audio'.

If you use more than 32 audio ports some hosts have problems. In my case Cubase also crashes using 128 audio ports. But if you set "buffer=1" (default buffer=2) in the VE Pro VST-connection-windows then it works.

Best regards,

Peter