Hi all,

Very interesting thread as I'm experiencing the same issues so far...

IMac Pro as main machine, Macmini as slave, both machines connected via Ethernet.

Cubase 10.5, VEP7 on both main and slave machines.

Like Mark and Erik, I have checked all Firewall permissions and manually set up the IP addresses and Network addresses. To no avail, sadly, as I cannot see any instance of the slave's VEP, even when typing in the server IP as well as instance name...

Also maybe worth mentioning, never have I seen the window saying "VEP pro is trying to establish a connection accep/refuse"... Which I did have with VEP6.

Main machine is running Mojave and slave is running Catalina. Should this make it complicated?

Very much looking forward to seeing how this will resolve! Hoping it's a one click "permission" to react to.

Best,

Nathan

Hi, 

The best idea is to send your network settings (screenshots of all involved computers) to support@vsl.co.at, so we know a bit more. 

Static IP addresses will help, consumer networks will help (192.168.0.x or 10.0.0.x), subnet masks 255.255.255.0

For testing, try direct connections as well (take out the switch/router for a quick check). 

Best, 
Paul

I was having this same issue before I realized that you have to open the Vienna Ensemble Pro Server application and create an instance before any instance will show up in your DAW. This could be entirely elementary as I just upgraded a few hours ago. But if it is of any help let me know.

Thanks.

Hi,

could anyone meanwhile solve this problem? Because I'm having the same problems. Sometimes it shows up, but most of the time not. It seems to happen accidentally.

Frank

Also still having the same problems. Have been back and forth with VSL tech for months and they eventually gave assuming it was a conflict with a (then needed) wifi connection concurrently running.

Have since reconfigured 2 Macs and 1 PC all connected via hub (wifi off) and still problems. iMac slave shows most of the time, PC often not. I have noticed if I boot Logic and open a new project the PC is normally showing, however if I boot Logic straight into a current project then it doesn't. It's incredibly frustrating, but at least I have found the workaround of typing in the PC IP and instance name.

VSL - surely you have had enough of these reports since VEP7 to resolve the issue?

Best

Harry

Hi Harry, 

Just catching up on this and couldn't find any cases in our ticket system from your registered email address... Network discovery can sometimes be a bit tricky, but usually works (I'd say for at least 99.9% of all our users). 

Glad to hear that the workaround works for you, and we'll keep that in mind for our next development push!

Best,
Paul

Hi Paul

Sorry multiple email addresses.. last case number was 325926.

I will open a new ticket and try another round of support when I get a minute. It feels like it might be something specific to Logic, since I have moments where VEP VST in Bitwig can see the PC while AU in Logic can't.

Cheers

Harry

Good evening folks,
Did someone solve this problem?
Thank you.

Hi Cochise Studio, 

It's usually very user-specific and has to do with a few elements that can block network communication (firewalls, AV programs...). 

You can always contact support@vsl.co.at with your specific situation.... or post some details about your setup here. 

Best,
Paul

I had these issues recently on a brand new DAW Mac mini M1.

I was able to solve that problem with "First Aid" (repair permissions) under Disk Utility! 

I had a few days of panic when my DAW (Logic) would always hang when starting up a session with VEP7 instantiations connecting to my slave machine.  When the hanging occurred, the  VEP7 on the slave would pop up an instance but wouldn't complete the loading as if the DAW wasn't able to fully "send" instructions.  When I quit VEP7 on the slave, the Logic session would continue to load - which was a huge relief.  Also,  I was able to create sessions and connect with VEP7 (slave) but upon reconnecting later on, the hanging would occur again.  I should also add - connecting to VEP7 locally was totally fine.  

So after much head scratching, reformatting my slave (because I did the HIgh Sierra upgrade fiasco with an older MP), reading numerous forums, and finally stumbling on this thread I figured out my problem!  With the discussion of possible network issues I thought it'd be good to look into my own network settings.  

THE PROBLEM:  NORTON 360 Content Filter - DISABLE THIS!

I had installed Norton 360 and it automatically puts this content filter feature into the network settings.  I disabled it and then voila everything connected as expected.

Hope this helps!

W

I was fiddeling arround for a while too. My configuration is Cubase on a Mac (OS Big Sur) running the VEP7 client and a Win10 PC as VEP 7 host. I tried several suggestions for Port configuration and firewall settings.
The only way I could get a runing connect to the host was by disabling the PUBLIC Network firewall on the PC.
Well - I don't like that and hope the VSL people finde a better solution for communication in the future.

Hope that helps someone.

Just updated 3 of 4 Macs to Ventura from Big Sur.  Latest versions of VEPro. I no longer can see any instances across any of the 4 VEPro servers once the servers have been running for any extended period of time... including local. Any saved track templates will connect (via Reaper), but the servers+instances only show up in the plugin when VEPro is initially loaded on each server, then disappears shortly after. I thought it might relate to the number of instances, but even empty VEPro sessions quit showing up as well. Any help would be greatly appreciated. 

Hi I just bought VEP 7 and installed it. I’m just trying to run VEP 7 on the same machine as my DAW DP 11.22 running on an i9 Intel Mac with MacOS Ventura.

2024.

Any fix to this problem?

Hi! Multiple issues have been discussed here. If there is a general issue you wish to discuss with the community, the forum is a good place. If you need help with VE Pro on your system, please contact us via support@vsl.co.at! Best, Andreas