Vienna Symphonic Library Forum
Forum Statistics

181,904 users have contributed to 42,191 threads and 254,627 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Swaping computers with VEP very urgent

  • Swaping computers with VEP very urgent

    A
    A

    Hello, I will have a bigger Mac for my DAW and I want to work sometimes on this bigger Mac and sometimes on my current MacBookPro. I am investing in new computer so this is why I need to know what I can expect.

    Is there any quick way to not have problems to switch between external VEP IPs for Logic so it can understand what I want to do:

    1. Current scenario: I use my MBPro 255.255.1.6 and connect to the external Windows MAchine that has IP 255.255.1.7. All my projects since a few years open with this configuration

    2. Scenario 2: I I want to work on my new DAW Machine with the IP 255,255,1,5. and still connect it to my 255.255.1.7 Windows Machine. There will be difference in DAW IP,  does it matter? Or my projects will open correctly in spite DAW IP has changed?

    3. Scenario 3: I want to use the VEPServer on the same DAW Big Machine 255.255.1.5  What can I do so my old projects open and I can work the way I choose?

    The IP of the VEP is somewhere encoded in the Logic file? Is there a way to have a control over it? I do not want to change IPs of current computers to not to have conflicts (there is a time machine backup etc)  but please focus on reply on my 1.2.3 scenarios. Thank you
  • A
    A

    Any experience with it?
  • A
    A

    No reply after many days. I am sending official mail

     

    thank you
  • F
    F
    last edited
    last edited

    @Adia said:

    Hello, I will have a bigger Mac for my DAW and I want to work sometimes on this bigger Mac and sometimes on my current MacBookPro. I am investing in new computer so this is why I need to know what I can expect.

    Is there any quick way to not have problems to switch between external VEP IPs for Logic so it can understand what I want to do:

    1. Current scenario: I use my MBPro 255.255.1.6 and connect to the external Windows MAchine that has IP 255.255.1.7. All my projects since a few years open with this configuration

    2. Scenario 2: I I want to work on my new DAW Machine with the IP 255,255,1,5. and still connect it to my 255.255.1.7 Windows Machine. There will be difference in DAW IP,  does it matter? Or my projects will open correctly in spite DAW IP has changed?

    3. Scenario 3: I want to use the VEPServer on the same DAW Big Machine 255.255.1.5  What can I do so my old projects open and I can work the way I choose?

    The IP of the VEP is somewhere encoded in the Logic file? Is there a way to have a control over it? I do not want to change IPs of current computers to not to have conflicts (there is a time machine backup etc)  but please focus on reply on my 1.2.3 scenarios. Thank you

    Hey Adia,

    Sorry no one got back to you sooner. And it would be a good idea to get in touch with official VSL support on this. But the way I understand your scenarios whatever your DAW machine’s IP is shouldn’t matter, just so long as you are on the same subnet, VEPro will find the instances that you previously connected to. Especially since it seems you have them setup as static which certainly helps. And switching which DAW machine you are using shouldn’t effect the connection. If it were the Slave machines that were changing IP then you might have an issue but I think VSL has done some work so that even if your Slaves have DHCP assigned addresses they are still “re-link-able” if they can be discovered (which would again require you to be on the same subnet).

    In your third (3) scenario that is a bit more difficult to be precise about. Assuming you only have one Slave machine then that would actually be a relatively easy change to make, just open up the Slave VEPro project on your local DAW machine and connect to the local instance. You’ll need to delink your old project the first time you open them but after that they should remember the new instance locally on your DAW machine and not the remote Slave version. If not you’ll just need to re-link it properly as required. If you have more than one slave then you’ll need to combine the multiple projects wich will be tricky. I would suggest creating channel sets and importing the project that way as there is no good way I know of to do this. But maybe there is an import project functionality that i am not aware of. I did this when I was still in VEPro 6 so things could have changed or been updated since I last needed to do this. 
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hello Adia,

    Thanks for posting in our USER forum, where you can ask for input from fellow users. As you know from 23 support cases you have opened with our support team, direct help is best requested from support

    @Another User said:

    3. Scenario 3: I want to use the VEPServer on the same DAW Big Machine 255.255.1.5  What can I do so my old projects open and I can work the way I choose?

    Connect them manually. 

    Best, 
    Paul

    Paul Kopf Product Manager VSL