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 !!

Hi legodo, 

Ok, then we'll have to dig deeper there.... Luckily, this fix seems to have worked for everybody else we know with this specific problem. 

Can you please send us some screenshots and a description of your network situation?

support@vsl.co.at

Anything unusual in your setup that might block network communication? We have made a network version jump since 1406, so anything from free AV software to strong firewalls will be good to know. 

Thanks for your support in solving this!

Best,
Paul

i have the same issue as legodo

did everything as you suggested, but to no avail

i see the server but no instances

i disabled the firewall, but apart from that i have no software running that might interfere.

also, everything worked fine, i just relocated my studio and reconnected, then this happened

cheers,

Geert.

Hi ghuinink, 

Thanks for your input!

Please get in touch with us via support@vsl.co.at, so we can send you latest beta versions as soon as they are ready. 

More information about your setup and some screenshots will be very helpful. 

Best, 
Paul

@Andreas8420 said:

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

Hi Andreas,

2 computers: iMac Pro running Ventura 13.2 DAW is Nuendo 12; Server machine is Windows 11 hosting VEPro.

Each machine has 2 ethernet network 'cards', one connecting to an internet router with IP assigned by DHCP on router - I don't use this for VEPro connections. The second ethernet 'card' on each is cabled point-to-point with a normal cat6 cable (crossover cable irrelevant these days) with a fixed IP address in a different address range to the other card. This connection is for VEPro only. 

@ghuinink said:

i have the same issue as legodo

also, everything worked fine, i just relocated my studio and reconnected, then this happened

Hi Geert,

According to your email, you are on eLicenser and VE Pro v7.0.1120. This thread and the issue of instances not being advertised is a problem that only showed up after VE Pro 7.1.1406 (iLok).

You mentioned that you relocated. In case your IP or instance names changed, existing project can no longer auto-connect. In that case, one has to manually re-connect and re-save with the new connection.

We can continue in your email - this thread here is not about eLicenser legacy builds of VE Pro.

Best,
Andreas

Greetings. The VEP 7.2.1516 instances are still not showing. I have to type-in the IP address and instance name and it will appear. The various patches workarounds, updates, and "fixes" have still not resolved the issue. it was working great about a year ago and earlier. Basically, the versions before the iLok changeover were much better. 

MacPro 7,1 Ventura 13.2.1 (22D68), Pro Tools 2022.12, VEP 7.2.1516.

iMacPro 1,1 Mojave 10.14, VEP 7.2.1516.