Vienna Symphonic Library Forum
Forum Statistics

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

In the past 24 hours, we have 4 new thread(s), 22 new post(s) and 50 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Logic template does not reconnect to slave VE Pros

  • Logic template does not reconnect to slave VE Pros

    D
    D

    I'm running an instance of VE Pro on my Mac Pro and two slave machines (G5s), all controlled by Logic. Once I restart the machines and the software, my Logic template recognizes and reconnects to the instance on the local machine, but not the remote ones. I have to manually reconnect them, which is a major pain and completely impractical. All the instances are decoupled. Does anyone have any idea what I might be missing here? I'm running the 4.1.7846 version on all machines. 

    Cheers,

    DP
  • D
    D

    Yes. All instances are decoupled. Re-couple before saving the project before closing it, and they should connect automatically next time you load it. Also check that you are using fixed IP.

    DG
  • D
    D

    Thanks, DG. Wouldn't re-coupling cause the instances on the slave machines to load everytime I open a new sequence? This is what I'm trying to avoid.

    DP
  • D
    D

    Sorry, I don't understand what you're trying to do then. Please could you give a detailed explanation of what behavior you are expecting from VE Pro and I might be able to narrow down the best course of action for you.

    DG
  • D
    D

    Sorry if I'm not explaining things properly, DG. I run VE Pro on two slave machines and locally, on the Mac Pro. I have a Logic template with VE Pro instances connecting and triggering instruments on these machines. From what I understand, enabling the decouple button will keep the samples loaded in RAM, so that they do not have to re-load every time I open a new sequence based on that template. This indeed happens on the local machine - all the instances are connected once I load the template, or any new sequence based on that template. However, this does not happen with the slave machines - they're telling me they're 'not connected', and I would need to manually click the connect button and go through the whole timeconsuming process again. I hope this describes the situation better.

    DP
  • D
    D

    Hey DG,

    I'm not sure if you've seen my reply above yet - please let me know if you have any other questions. Your help is much appreciated.
  • D
    D

     OK, there are a couple of things that you need to check:

    1. Make sure that all machines are using fixed IP
    2. Make sure that all instances are named and preserved before you save your Metaframe

    If you decouple without naming and preserving you won't get an automatic connection when you next come back to the project. Note that the first time you open any new project you will have to connect manually, but as long as you save it coupled, it will always "remember" what to connect to when you re-open it.

    DG
  • D
    D

    Hey DG, thanks for getting back to me. I'll try the fixed IP - that sounds like it could be the issue. I've been diligently naming and preserving instances before saving Metaframe. Many thanks for your help!