Vienna Symphonic Library Forum
Forum Statistics

182,255 users have contributed to 42,214 threads and 254,734 posts.

In the past 24 hours, we have 2 new thread(s), 23 new post(s) and 45 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP5 slave not connecting sometimes...

  • VEP5 slave not connecting sometimes...

    G
    G

    Hi I've got a issue with VEP5 that won't connect the instances in the Slave machine in unexpected moments.

    For ex : My main DAWN (Mac pro 2009 32GoRam/Nehalem) is running Nuendo 7.0.40 with OSX 10.10.5 and the Slave is an I-Mac 32Go RAM with OSX 10.8.5.

    My template is using 80 VEP instance as Track instruments with different Libraries (Kontakt/U He/ Specra).

    All in preserve and Decouple All mode.

    Last week I've worked everyday with no problem. Everytime I launched my Nuendo session all the VEP instances connected correctly in the master and slave (about 40 VEP instances in each machines).

    But today I launch again the same session I saved Friday evening and only the VEP instances on the Master connect and not the ones on the I-Mac slave.

    Nothing as changed in my setup during the week end but I have to manually re-connect all the VEP instance on the slave machine to be able to work with my template.

    This time it didn't create empty VEP instances on the Master VEP to replace the ones it doesn't connect, but sometimes it does, so this is a random problem, and very anoying as my template will increase up to 150-200 tracks while I'm going along the curent project.

    This is hapening for a while now and I thought I might find someone here to help me solve this.

    Thanks for your help.

    Stephane
  • PaulP
    VSL Team
    PaulP

    Hello Stephane, 

    What are your network settings?

    You should definitely use static IP addresses, and avoid 169.x.x.x addresses (these are automatically assigned by your computer and tend to change).

    Please try the following: 

    Manually assign one of these IP addresses to the computers in your setup: 192.168.0.x or 10.0.0.x, and assign a subnet mask of 255.255.255.0 (leave the other fields blank), then it should work. 

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • G
    G

    HI Paul,

    Thank you for the fast answer.

    The numbers were as you mentioned but with DHCP in automatic mode so that might have caused the issue.

    I did what you advised and will see if it happens again in the next couple of weeks, I'll keep you posted about it.

    Best regards.

    Stephane