Vienna Symphonic Library Forum
Forum Statistics

180,783 users have contributed to 42,141 threads and 254,364 posts.

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

  • Sometimes VEP connects, sometimes not

    I have a main computer (Mac Pro running El Capitan), and two orchestral slaves (one a Mac Pro running El Capitan, the other Windows 10). Everything running the latest versions of everything. The main computer is running DP9 and the VEP MAS stub plug-in. The two slaves are running the 64-bit VEP server.

    I find that VEP is erratic about when the MAS stub plug-in connects to its slave instances. Sometimes it connects perfectly, other times it doesn't, so I have to manually connect each instance.

    I'm also unclear about what order I should shut down. For example, if I've finished working, and I try and quit VEP on the slave machines, it tells me there are active instances that will be shut down if I quit. If I click yes, it asks me whether I want to save. I'm confused about this, because no changes were made. Am I perhaps accidentally saving things in a disconnected state (which is why they don't auto-connect next time)? However, on next boot, sometimes they do auto-connect, and sometimes they don't.

    How can I make auto-connection always work so I can get straight to work every day? What order should I boot things up in, and what order should I shut them down in?

    (Side note: I wish I didn't have to think about this at all, and that they just worked in any order. That would make VEP much more friendly!)


  • last edited
    last edited

    Hello ddas,

    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.

    Also, you should check out how Preserve and Decouple Modes work. If you keep your VE PRO instanced preserved, they will still be available after you shut down DP9 (thatĀ“s a feature). See page 52 in the VE PRO 5 manual.

    Best.

    Paul


    Paul Kopf Product Manager VSL
  • Thanks Paul!

    I do use static IP addresses. My router assigns by DHCP, so I switched it to DHCP with fixed addresses, so all my computers have internal IP addresses like 192.168.1.5, 192.168.1.6, and so on...

    I do use both Preserve and Decouple.

    Still, I find they sometimes auto-connect and sometimes don't. I have a suspicion that the order in which they are opened has something to do with it, but not always. Sometimes the slave computers' VEP instances are already open, then on the main machine, I open yesterday's project which connected just fine yesterday, but they don't auto-connect today.


  • Hello ddas, 

    VE PRO connects based on 2 parameters: 

    1) the instance name (needs to match the instance name that is already open => "preserved" name)
    2) the IP address

    You can try with simple test songs, this should always work.

    You should definitely UN-DECOUPLE ALL instances before you save and close a song!

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    You should definitely UN-DECOUPLE ALL instances before you save and close a song!

    Really? So every time I'm switching projects on my main computer, but intend to leave all the samples loaded on the slave computers, you want me to go into every single VEP stub plug-in and decouple? That's a lot of manual clicking, only to have to redo it when I re-open!

    Regarding the other problem (not automatically connecting) I will see if I can get a reliable repro recipe to demonstrate when they do not auto-connect.


  • Hi ddas, 

    ThatĀ“s why thereĀ“s Decouple / Couple ALL => one click :-)

    Best, 
    Paul


    Paul Kopf Product Manager VSL