Any update on Rosetta and/or native M1 support? 

Bumping this old thread. I still get glitches in VE Pro 6.0.17966. It happens with Kontakt and Spitfire BBC. It's especially noticable when you ramp the tempo change, like from 70 to 50 in two bars. I'm using Cubase 10 for Mac as my DAW, VE Pro Server on Windows 10. Has anyone ever found a fix for this? Disabling tempo in Kontakt helps a bit, but this isn't possible in the Spitfire player. 

Windows is going to auto-update to Windows 10 Creator soon, is VEP6 working OK in that version? 

Is it better to use the VST2 plug-ins instead of the VST3 versions in Cubase 8? 

Is it possible for VE Pro to play its audio through an interface card, instead of through Ethernet back to the host? If so, where is that set up? Thank you. 

Seem to have it working. Trick is to create an input channel, set input to "Kontakt 4 1 2" and output to "NET 3/NET 4"

Yes, I read the manual. I'm doing what it says to do on page 22. The numbering scheme isn't explained anywhere, "Kontakt 4 1 2," "Kontakt 4 1 3" etc. But none of them work. 

Searched around but couldn't find an answer to this. How do I get the additional outputs in Kontakt to throughput to Logic when hosted in VE Pro? I want to have two choir samples in Kontakt, one using ST1 and the other using ST2 outputs in Kontakt. I want these to route to NET1/2 and NET 3/4 so that I can have them show up in Logic. I know that I can make two instances of Kontakt and do it that way. But how do I get one channel of an instance to use a different set of outputs? It seems like an instrument can only have a stereo out. I tried making an Input in VE pro and assigning "Kontakt 1 3" to the input but it doesn't see anything. 

Thanks, -jl

This update brought back the "takes a minute and a half to save or add a track" bug when used in Logic 9.1.1. 

Working great for me. I've had the beta dialogue pop up but was able to work around it. Loading time on K4.1 on a Mac Pro is AMAZING. Fast fast fast. And working great in the 64-bit server. 

Got a reply. I'm going to try upgrading to Windows 7 Ultimate and see if that fixes things. 

No reply from them in email, either. 

Is this not being answered because my system is not supported? I will upgrade to Windows 7 if it will help. Is Kontakt 3 or Kontakt 4 hosted on VSL Server (32-bit or 64-bit) on Windows 7 working well with Logic Pro? Thank you. 

Are you looking into this, or am I alone? Please let me know, thank you. 

If you're a programmer then brobson's explanation above should suffice. Open regedit and make a new folder, with new binarys or whatever with the values shown in the other directory.  

Did another test tonight, I don't get the slowdowns in Logic if I use the default (VI) instrument on the Windows machine. It only happens when hosting a VSTi on there. 

Are you using the AU plug-in with DP or the VST plug-in? What kind of Mac are you running? Which OS version? Which plug-ins on the Windows machine? Perhaps my problems are system-related (Mac Pro 8-core Nehelem.)

Probably a good idea to do some reading on regedit or enlist a knowledgeable friend to do this. You can really bork your system if you do the wrong thing in regedit. I got my system working OK but I've done a tiny bit in the program. 

No, you don't need to do this on Mac OSX 10.6. If you have Snow Leopard, open your Activity Monitor app. You'll see that many of your Apple apps and processes are already running in 64-bit mode. Or just open VE Pro 64-bit server. :) 

I upgraded my Mac to 24GB of RAM today. This seems to have solved the “Out of Memory” errors but I’m still seeing slowdowns. My system specs are: 

Mac Pro 8-core (early 2009 Nehelam) 2.26GHz, 24GB RAM

Mac OS X 10.6.2

Logic 9.1

VE Pro build 4881

I did three tests using a Logic 9.1 project I built with nothing but 7 instances of VE Pro plug-ins:

1. No VE Servers running

In Activity monitor, Logic Pro shows 320MB physical memory/420MB virtual memory loaded, 5% CPU when idle

Opening the project with no servers running took 10 minutes! 

Making a new track, deleting that track, and then saving took 1-2 seconds per task.

2. VE Pro Server (32-bit) running on Mac Only

I opened VE Pro Server on the Mac and opened my MFrame project, four instances of Kontakt 3.5. For each of these steps I quit Logic, opened VE Pro then opened Logic and the Logic project again. 

Logic Pro now shows 276MB/376MB RAM use, less than when no servers were running for some reason. The Logic project opened very fast, about 1 second. 

Making a new track, deleting that track, and saving again takes 1-2 sec per task.

3. VE Pro server running on Mac and x64 (both 32-bit)

I again quit Logic and opened VE Pro Server on Windows x64 SP1 (4 instances of GVI, 1 instance Kontakt 3.5. The 2.5GB RAM template took 10 min to open. 

Logic Pro now shows 370/480MB RAM use, 17% CPU in Activity monitor

Opening a project and making a new track go instantly.

Deleting a track takes forever with this setup: 30 seconds of spinning beachball, then the track goes away, another 30 seconds of beachball = 60 seconds total

Saving the Logic project takes 30 seconds of spinning beachball. 

So there seems to be a problem when using VE Pro Server on the Windows machine. I suppose I can upgrade to Windows 7 if you think this will help, but it seems like Logic is unhappy with something happening with the plug-in when connected to Windows. 

I also found that the VE Pro plug-in doesn’t remember connections if you open when a server is not connected and then save the Logic project. If I did this I had to open each plug-in, connect, and choose the instance name. 

I hope this is helpful, -jl

A 64-bit AU host (Logic 9.1) has only been available for about a month. 64-bit VSTi hosts were available on Windows for years. That's why there aren't any instruments for Mac yet, the format was only recently released. Kontakt, Play, and EXS are still 32-bit as well. At least VSL has a 64-bit solution for Mac, using the player in Vienna Ensemble Pro. 

I can't tell if it's decoupled! The UI shows all-red, and it's still there when I quit Logic, which makes me think it's decoupled. But when I save the Logic program, I see a little "Project Saved" message on each VE Pro instance, which seems more like coupled.  I'll look at the RAM usage tonight. I have new RAM getting here Wednesday and I really hope that helps. 

I'm running less than that. I'm also using the Kontakt 3.5 memory server, which uses an outside memory space for sample memory. And VE Pro is not crashing, Logic is just running very slowly: 30 seconds to save a project, 60 seconds to delete a MIDI track, etc. If the AU plug-in is 64-bit, then I will be able to run Logic 9.1 in 64-bit mode which may help. (Even though Logic itself shouldn't need a lot of memory -- all I'm running at this point is ~9 instances of VE Pro plug-ins.)