Can someone explain the pricing? In 2016 I paid €170.00 to upgrade 6 licenses to VE Pro 6. Now, I just purchased the VE Pro 7 upgrade for €70.00 and I get... 1 license? It's going to be another €225.00 (45 * 5) to upgrade the remaining 5 licenses. That's €295.00 total - almost double the last round of upgrade pricing. I wish this was better explained somewhere - it wasn't clear in the email, or the website.

A little birdie tells me there is a beta of VE Pro 5. I assume it's not public? Any info on when this may be available, even for testing? I am intensely curious. Any info appreciated!

No, I'm talking about the network principle.

Has the VSL team considered engineering its own network protocol to make audio/midi transfer more stable?


I only ask this because I am aware that MusicLab's MIDIoverLAN product does this. It does not use TCP/IP, but instead installs its own network protocol/driver to communicate. From what I've learned, it is far more stable and potentially decreases latency issues because it is on a completely separate layer and does not have proprietary packet formats.


There are other technologies of interest too, such as Dante which I have heard very good things about:

http://www.audinate.com/...=article&id=92&Itemid=92


Just wondering what the software dev team's thoughts are, and what made them settle on the currently used network transmission implementation?

Haven't noticed a problem here. Seems to work fine.

@jackballed:


I have the same issue. Two dozen VE Pro plugins, with 16 MIDI ports each. Takes 2-3 minutes to load a session. Very annoying.


I am tempted now to do some experimentation with load times by changing the number of MIDI ports as you and Karel have deduced it does make a difference.


Although I REALLY wish there was some way for Steinberg or Vienna to do away with the excess processing which makes it so slow in the first place. There's some serious inefficiencies somewhere in there.

Also, not to overstate the obvious, but with a stable ethernet connection you can get more audio channels over VE's Audio-Over-LAN than most interfaces with ADAT. Sky's the limit.

We're talking about persistent VE Pro Server instances. They have nothing to do with audio hardware.

I hate to dredge up old topics, but I am still finding this sample rate issue troublesome.


Please:


1) add the options as described by Will with the manual default setting selectable, and


2) In the VE Server instance window next to the "CPU usage:" status, please have the current sample rate also shown as a visual check, ie "44.1KHz"

jeremyroberts - I had not heard of that, that sounds pretty dodgy. But I'm pretty certain this machine has the capability. I've done extensive ping tests with packet sizes to confirm.

It's only interesting because I've had 9K frames on all of my equipment for quite a while and it actually improved VE Pro performance. I only found out by accident that recently, my Mac's MTU mysteriously reset itself to the default 1500 - perhaps after a system software update or something. I put it back to 9K and then all the problems started with audio streaming. It's a mystery at this moment. But it's working fine at 1500, so I'm not complaining.

These kinds of problems can be really hard to suss out.


Might want to give Play 3 a shot, which was just released.


Sounds like you may have network streaming issues. I use a sequencer audio buffer of 256 and set the VE Pro servers to "2 Buffers" and this works well. But that's in Cubase - in Logic your mileage may vary.


Have you tried looking into 9K Jumbo frames? I know that made a big difference for me.

Here is a riddle I'm hoping anyone tech-savvy might be able to help with:


Mac Pro 8-core running Cubase 6 64-bit


5 external PCs running VE Pro servers


All static IPs on a closed, dedicated gigabit switch.


Each PC is set to Jumbo frames (9K MTU)


When the Mac is set to 9K Jumbo frames, I get stuttering and big audio-over-LAN issues.


When the Mac is set to normal 1500 MTU, audio-over-LAN streaming is almost flawless.


Why?

This is a very frustrating bug. I don't know if it's their plugin that has a glitch or if it's a VE issue.

1. Load Superior Drummer 2 or EZDrummer into a persistent VE Pro server instance - 32 or 64 bit - and save it as a metaframe.
2. Quit VE Pro, then re-launch VE Pro and load the metaframe. The instance will load with VE's audio engine off. If you look at the SD2/EZD plugin, you will see that it has not loaded any samples.
3. Turn on the audio engine for that VE Pro instance. You will notice that the SD2/EZD will then load the samples. This is all fine and good, but.....

Here is where the first bug is: If you connect to this VE Pro instance without first manually activating its audio engine as in step 3 above, the SD2/EZD will permanently remain with NO samples loaded, and there is no way to make it re-load the samples until you close and reload the VE metaframe, or instantiate another SD2/EZD plug-in.

In addition, it seems dodgy with regards to connects and disconnects. At some point, even after loading the samples successfully, I have found that it will have unloaded them upon the next time your DAW connects to this VE Pro instance.

Good to know - I don't own DVZ but I've been considering purchasing it. I'd want to know if there are any significant roadblocks because I depend on VE Pro!

At this point I would say this is a Play/EastWest issue because very few - if any - other people are having problems. Have you raised this issue with tech support over there?

It's interesting you mention this. Someone over on the EastWest forums described the exact same procedure to get Play running inside a VM with VE Pro and reported that it worked very well.



No, I've spoken to Johnny, the developer of JBridge, and he doesn't plan on coding an OS X version.

@dayadon: Projects previously saved load and operate well in C6 64-bit, except the VE plugs in Cubase don't show their GUI. We might have got our wires crossed. I'm talking about the 64-bit VST component - the one used with C6 64-bit. That has nothing to do with connecting to 32 or 64 bit server instances. You may have to explain precisely what you're talking about.

@Karel: any indication of when we can expect a fixed VST 64 for OSX? Days? Weeks? It will make a big difference for me immediately as I am making decisions about how to modify my template now before a large project starts.

Thanks!

Load RealGuitar into VE, then you can insert FX plugins such as Guitar Rig or Amplitube onto the audio channels within VE Pro's mixer.

Make sure to have the latest Syncrosoft and iLok drivers installed too.

I am having no problem loading Play into 32-bit VE Pro on a Mac (I know that may not help much but it's something.)

+1 here



This same issue exists with BFD2.

Excellent! Can always count on you guys :)

I know this is early, but I just got Cubase 6 for the Mac and test drove running Cubase 6 in 64-bit mode. VE Pro shows up twice in the VST instruments list, but neither result in a plug-in GUI, just a bunch of parameters.

Works perfectly fine (so far) in 32-bit Cubase as per usual.

I assume fixes are in the works for the 64-bit VST/VST3 on the Mac?

(latest VE Pro build 7644)

Short answer is: you can't "boot" in 64-bit mode and you don't want to. The normal 32-bit Snow Leopard is perfectly capable of running 64-bit applications. The 64-bit booting will only come years from now when all your software is 64-bit capable. Currently DP is a 32-bit program, as are a lot of other software and plug-ins you are probably using.

You can run both 32-bit and 64-bit VE Pro servers at once, and load/connect to instances of both from DP. You don't need to change the operating system.

The Logic 9.1.3 update claims to add support for 12-core Macs.