Same. I had this issue before the most recent update - this update was supposed to fix it, I think. I have to manually connect the instances by inputting the server and instance information. It connects that way, so that's what I will continue to do until it gets resolved.

Hi,

Thanks for your input!

This was indeed fixed for most users who reported this behavior, so now we'll have to find out what could possibly block communication on your specific systems. 

It would be great to get more information about your network setup, ideally directly sent to support@vsl.co.at, so we can investigate and provide you with new beta versions as we are trying to solve this, 

THANKS!

Best, 
Paul

FOR ALL AFFECTED v1503 (macOS) USERS:

The best way to further look into this is to find out what is being reported by the Discovery Bonjour Browser. The app can be accessed from here:

https://apps.apple.com/us/app/discovery-dns-sd-browser/id1381004916?mt=12

The "_vepro._tcp" key should match what is shown in the plugin browser. Similar tools exist on Windows but require CMD commands. Please get in touch with us via support@vsl.co.at.

Your input would be highly appreciated, as we cannot reproduce the issue on any of our test systems.

Best regards,
Andreas

Having posted earlier in this thread, I am a WIndows 10 user. What network information do you want? Let me know and I'll send it.

In my previous post I mentioned Studio One. This morning I tested a new empty Cubase project and attempted to connect to VE Pro with a single rack instrument. Same problem, no available instances are shown in the connection window. So it appears the problem is not DAW-related, although I draw that conclusion as a layman.

Interestingly, in my Studio One projects previously existing connections to VE Pro instances (from before this problem cropped up) are still connected, only newly attempted connections are affected.

I have had this issue as well. I have given both my Mac and PC server fixed ip addresses and then it's possible to connect to the server via those addresses! Fill out the instance name - remember uppercase matters! - and then connect. 

@Stig Christensen said:

I have had this issue as well. I have given both my Mac and PC server fixed ip addresses and then it's possible to connect to the server via those addresses! Fill out the instance name - remember uppercase matters! - and then connect. 

Thanks so much, Stig. That worked, at least it did using the non-DNS IPv4 address shown in my network properties. Not sure how to assign a fixed address to VEP, nor which one to assign, but what I did worked. 

That is at least a workaround.

Again, much thanks.

There have been reports that reinstalling VE Pro 1503 through the Vienna Assistant (right-click > Reinstall) temporarily solves the issue until the computer system is restarted. Is that the case for everyone?

Best regards,
Andreas

It was the case for me. Solved for one day by uninstalling/reinstalling 1503 using VA. I shut down every night so the lights won't bother my wife. Next morning, problem returned. Then reinstalling didn't even work any more.

Update.

Based on detailed suggested steps by VSL Support the problem was fixed.

I'm not absolutely sure which of the steps did it, but I suspect it was entering specific inbound port permissions in my firewall settings. Instructions are found in the VE Pro manual under "Firewall"

@Andreas8420 said:

FOR ALL AFFECTED v1503 (macOS) USERS:

The best way to further look into this is to find out what is being reported by the Discovery Bonjour Browser. The app can be accessed from here:

https://apps.apple.com/us/app/discovery-dns-sd-browser/id1381004916?mt=12

The "_vepro._tcp" key should match what is shown in the plugin browser. Similar tools exist on Windows but require CMD commands. Please get in touch with us via support@vsl.co.at.

Your input would be highly appreciated, as we cannot reproduce the issue on any of our test systems.

Best regards,
Andreas

I am experiencing this problem. I downloaded the discovery app and it looks like the VEP instances appear in the plugin at the very moment I start the Discovery app. Maybe Bonjour is sleeping in some way and Discovery pokes it....?

Hi @santamorphic

Could you please let us know how many computers are involved, what constellation, and what OS versions and how your network is set up? Thank you!

(Just in case your forum signature is no longer up to date)

Best,
Andreas

FWIW, if I:

• Use Vienna Assistant just to download the latest VEP7 (WITHOUT installing)
• Use the Uninstall Vienna Ensemble Pro app to uninstall the existing version
• THEN install the update...

The update works fine, and DP finds instances as expected. And it keeps working even after I shut down and restart. I'm on Catalina—not sure if that makes a difference. This is of course a workaround—it would great to see this fixed, along with the issue I reported in another thread that the rollback function in VA doesn't work (can't return to an earlier version of VEP using that app).

Thanks,

Peter

2013 Mac Pro, OS 10.15.7, DP 11.21

@Andreas8420 said:

There have been reports that reinstalling VE Pro 1503 through the Vienna Assistant (right-click > Reinstall) temporarily solves the issue until the computer system is restarted. Is that the case for everyone?

Best regards,
Andreas

Hello,

Today we released Vienna Ensemble Pro build 7.2.1515. Please download this latest update in the Vienna Assistant.

Fixed: Switching between VST3 instrument channels could cause a hang
Fixed: Instance discovery on machines without an internet connection

In case of instances still not showing up:

MAC:

Step 1: Open "Activity Monitor"
Step 2: Find the process: mDNSResponder
Step 3: Double click > Quit > Force Quit (the process will restart immediately)

MAC & WIN:

Step 4: Re-start both DAW/SERVER machines (resetting Bonjour) to see if your instances reappear.

Best regards,
Andreas

After updating VE Pro to the new version I started up a blank Studio One project and tried to connect to my VE Pro Server template. All available instances now show.

Thanks so much, Andreas and VSL team!

Hi,

Here I have the same issue with this new update !! The first time it's ok , but if I qui Logic or VEP or a restart the issue is here !! I have reverted to 1406 !! With 1406 no issues at all it see the server on local and on my slave Mac Pro .

I'm sorry but this is the fact.

Mac mini M1 with Slave Mac Pro on Ventura 13.2.1

Hi legodo, 

Thanks for reporting!

Just to be sure, please double-check: Have you followed the steps listed by Andreas 2 posts before your post?

Thanks, 
Paul

Thank you for your answer Paul, I have followed the steps and at first no issue, but when I quit logic or VEP or other music software ( DP, Logic or Reaper ) the issue is here and my Mac don't show the servers !!

I'm sorry , but with the 1406 version all is great regarding this issue.

Thanks

Hi legodo, 

Sorry to insist: You did restart all connected computers after you performed this little sequence, right?

Best, 
Paul

Thanks Paul,

Yes I have restarted all computers and software after the steps indicated. And bam !! Same issue, it see the server but no instances !!