Vienna Symphonic Library Forum
Forum Statistics

178,670 users have contributed to 42,057 threads and 253,904 posts.

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



    I am a user of other VSL products and recently downloaded the VEPRO 7

    demo. I spent a whole day on forums and education videos, but i cant

    seem to answer the most basic question:


    the only way VEPRO7 would make sense to my setup is, if i loaded ALL my

    library on a slave computer (strong machine with all SSDs) and make a template

    in the DAW with ALL my tracks routed permanently.


    But everytime i close and reopen a song i have to reconnect to my Server in

    the plugin window. And in Ableton Live i have to manually reconnect every

    instance of the VEPRO slave plugin manually. Is this how it is supposed to work?????


    Thanks a lot!



  • last edited
    last edited

    I'm a beginner (2019/12/29) as well so please don't expext expert's advice 😊

    First of all you must make sure your slave machine(s) all have a static IP address becaus VEP handles the connections via IP addres not Computer Name.
    I did it
    - by using an extra GBit router and an
    - extra LAN-card per machine. Then I
    - defined a second LAN (192.168.0.x) side by side with my normal one (192.168.1.x)
    - starting with for my Master and for the 1st Slave and for 2nd
    - Network cards IP settings for 1st slave IP, Subnet Mask, no Standard Gateway (leave blank), no DNS server (leave blank).
    - Wrote the lines VSL1 VSL2
    into the HOSTS file (c:\Windows\system32\drivers\etc\) on my Master machine. This way the both slaves ar found by PC name (as I don't use a DHCP server in the VSL LAN).
    As I have understood so far: You can define a standard setup on your slave and save a VEP server file where all your big libraries and channels are stored in.

    Then you steup a DAW project may it be Ableton, Cubase ... and do your routing for the instruments you have defined in VEP server on your slave machine.
    You should disable all tracks in the template as otherwise loading for big templates will take forever.
    Than you can save the template with all VEP instances coupled (means your template will manage all connections and settings in the VEP server).

    When you now want to reuse your template just open and save it under a new name and start to enable all needed instruments/tracks.

    I know it is a bit intimidating but in the end you will get a huge payback in terms of usability/managebility of big projects.

    P.S. 1: Again, this will only work if you manage to give your slave(s) a static IP address! For me it didn't work with my primary LAN thus I built the second. Use good, shielded cables!
    P.S. 2: Saving and loading big templates with VEP connections coupled will take quite a while because  all settings on the VEP server are stored inside the template. When you got mor familiar with the system it makes sense to decouple the instances and save all settings inside VEP server. It speeds up the loading a lot.