Vienna Symphonic Library Forum
Forum Statistics

195,002 users have contributed to 42,953 threads and 258,083 posts.

In the past 24 hours, we have 12 new thread(s), 42 new post(s) and 66 new user(s).

  1. Home
  2. Software
  3. Vienna Ensemble Pro 7
  4. VEP7 Ensemble Regularily loses connection between host and slave

  • VEP7 Ensemble Regularily loses connection between host and slave

    S
    S
    last edited
    last edited

    I have a Mac (sonoma/Logic) host connecting to a Windows 11 slave running VEP7. All my VEP7 instruments on the Mac are AU3.

    Everything will be working fine at night and then when I come back in the morning I discover only some of the connections still work functionally (i.e. keypress gets me a sound), but many don't. And despite this, all the VEP instances show connected on both sides, but when I try to disconnect (and I see it disconnect on the slave side) and reconnect, there are no server instances shown to connect to on the AU3 side.

    Both computers have static IPs assigned.

    Seems like the only workaround is a full restart.

    Suffice to say this is incredibly frustrating. I expected after doing a major upgrade to my studio that everything would be more streamlined and faster and this appears to be a massive flaw in the implementation.
  • P
    P
    @simon5413 said:
    Seems like the only workaround is a full restart.

    A while ago, one of the VSL employee/moderators mentioned that opening and closing VEP preferences can help. It's not full-proof, but it has restored the connection for me enough times to at least try it. Not much to lose.

    I'll occasionally lose the connection even in the middle of a session (and yes, everything reports as connected and there are no instances presented in the plug-in window after disconnect/connect). Other times putting my Mac to sleep causes it.

  • L
    L

    In the western world, slavery was abolished, that’s why!

    Just kidding and I am sorry for not contributing anything, as I have never had such issues!
  • S
    S
    last edited
    last edited
    @plowman said:
    @simon5413 said:
    Seems like the only workaround is a full restart.

    A while ago, one of the VSL employee/moderators mentioned that opening and closing VEP preferences can help. It's not full-proof, but it has restored the connection for me enough times to at least try it. Not much to lose.


    I'll occasionally lose the connection even in the middle of a session (and yes, everything reports as connected and there are no instances presented in the plug-in window after disconnect/connect). Other times putting my Mac to sleep causes it.

    Yeah I literally just had a mid-session issue now too. Good lord. I'm pretty sure I tried the preferences thing but I'll try again.

    This is def not from sleeping computers, as I have all energy saving / disk sleeping turned off everywhere.
  • M
    M

    I have the same issue in a different context. I have a piece in Dorico with about 10 orchestral section based VEPro instances all using SY libraries connected. VEPPro is running on the same MBP however not on a second PC or Mac.

    All works perfectly but if I want to connect an additional instance e.g for muted brass after an hour or so of work and I press connec after having created the new entry in the VST bank in Dorico, the connect window of VEPro is empty. So all original instances are still connected and work, their connect windows show the instance and server IP but for new instances the link with the server seems lost. The only way to correct the issue I found is closing VEPro and the Dorico project which is time consuming. Just one of the teo two does not work. I also tried to manually enter the server IP and instance name in the connect window of VEPro but this creates a new instance in the VEPro server rather than connecting with the existing one.

  • H
    H
    @Mavros said:

    I have the same issue in a different context. I have a piece in Dorico with about 10 orchestral section based VEPro instances all using SY libraries connected. VEPPro is running on the same MBP however not on a second PC or Mac.


    All works perfectly but if I want to connect an additional instance e.g for muted brass after an hour or so of work and I press connec after having created the new entry in the VST bank in Dorico, the connect window of VEPro is empty. So all original instances are still connected and work, their connect windows show the instance and server IP but for new instances the link with the server seems lost. The only way to correct the issue I found is closing VEPro and the Dorico project which is time consuming. Just one of the teo two does not work. I also tried to manually enter the server IP and instance name in the connect window of VEPro but this creates a new instance in the VEPro server rather than connecting with the existing one.

    Same here with 3 VEP server