I am setting up VEPro7 for the first time with DP 9.52 on my mac.

I set up the first instance, called Bass, put in four bass libraries, connected them to the VE Pro MAS instance in DP, connected the outputs in the Bass instance in the Server to the aux channels in DP, and success! Upon testing I got the right sounds in the right place coming out in my DP.

Then I switched off and shut down.

Later I tried to set up a second instance in my server, AcGtrs, but when I went into my DP to allocate the VEPro MAS instance, In the DP invitation to connect window, no server instances are shown?

I checked on the first Bass instance, and the connection was all as it should be?

So what have I missed in connecting my second instance?

Originally Posted by: Gone To Lunch

I am setting up VEPro7 for the first time with DP 9.52 on my mac.

I set up the first instance, called Bass, put in four bass libraries, connected them to the VE Pro MAS instance in DP, connected the outputs in the Bass instance in the Server to the aux channels in DP, and success! Upon testing I got the right sounds in the right place coming out in my DP.

Then I switched off and shut down.

Later I tried to set up a second instance in my server, AcGtrs, but when I went into my DP to allocate the VEPro MAS instance, In the DP invitation to connect window, no server instances are shown?

I checked on the first Bass instance, and the connection was all as it should be?

So what have I missed in connecting my second instance?

Have you tried to manually reconnect your instance? Does it work fine if you do? My understanding is that the servers displaying in the DAW plugin is handled through DHCP broadcasting. And I have seen (and personally have) computers just not want to broadcast their DHCP information meaning the DAW plugin cannot find the server instance. When this happens for me I just manually enter the information. But I usually don’t have problems because I have a template that seems to be very robust about reconnecting my instances. So long as I don’t try to open the project/template when the VEPro projects aren’t open. And I think so long as you aren’t trying to connect the instances every time you open a project then it shouldn’t be too big of an issues when they don’t occasionally connect.

Originally Posted by: Falcowe

Originally Posted by: murphy761

Mine is only creating a new blank VEP7 slot next to the pre-loaded/preserved orchestra template. It only works with Pro Tools and Logic X when running everything on a single machine.

Hey Murphy, I would suggest to also try manually reconnecting the instances rather than relying on the automatic method. However in your case I might have some guesses as to why this is happening. First I would guess that the name of your instance has changed. And I would guess that you changed the name of your instance in VEPro after closing your session. If you changed the name of the instance after you closed/saved your DAW session then when the session is opened again from its last saved state it tries to find the instance it was last connected to but can’t since the name was changed. So instead it makes a new instance with the name it last remembers on the same IP address that it did successfully connect to VEPro on. I had a similar issue when I discovered a space at the end of one of my instances, removed it and then tried to open a session only to have a new instance show up with what looked like the same name. I was confused until I figured out the names for VEPro must be exactly the same on the DAW and VEPro side of things otherwise they will not reconnect properly. This actually is the only logical explanation I can think of why an instance wouldn’t reconnect if saved properly. Hopefully this helps you figure what is going on when your issues.  

Hello and thanks for the reply. Unfortunately, manual reconnection does not work. The VEP7 insert in Pro Tools always creates a blank new instance. Reinstalling the VEP7 software on the slave MacOS computer did the trick until it "degraded" again. After a few times of this, I'm now running everything from my main "brute force" DAW machine (VEP7 Server, Logic X, Pro Tools 2021.7, UAD). Doing this also improved the System Delay as reported in Pro Tools. I think there may be an issue with the most recent VEP7 release. Strange stuff.