Vienna Symphonic Library Forum
Forum Statistics

200,608 users have contributed to 43,204 threads and 259,106 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Vienna Ensemble Pro Slave/Master - how to?

  • Vienna Ensemble Pro Slave/Master - how to?

    I
    I

    It seems I have problems even to initiate Vienna Ensemble Pro from a master computer to a slave computer. Don't know if it's because I'm just too stupid, or if I misunderstood something, or if indeed there is something technical going on.

    I just want to confirm I understood the workflow and how it is intended to look on a master/slave setup. To be honest the instruction material is a little cloudy, at least from my point of view when things may not have worked as expected. Anyway, this is how I perceived a functioning setup could look, I'd appreciate if somebody could confirm or correct this reality check:

    1. First you start a VEP server on your slave. Then on your master/sequencer computer you create a track and insert VEP as a VST instrument. You then connect to your slave computer and it's VEP server. Correct?

    2. By connecting to the server, your master computer will automatically open up the VEP interface. You can then load various sounds and manipulate them on your master computer, but in effect all of this is taking place on your slave computer. The VEP interface on your master computer is just acting as a sort of remote desktop to operate your slave computer. THe samples are streamed on your slave but are sent via LAN back to your master computer which will then play the samples through the soundcard assigned by the sequencer host. Correct?

    Provided I understood the above correctly, something's not right with my current setup. No VEP interface will open up on my master computer after connecting to the slave server. Any advice would be much appreciated.

    T
  • PaulP
    VSL Team
    PaulP

    Hi iqbahl,

    Sorry to hear that you´re having troubles.

    One misunderstanding: the VE PRO interface will always open on the SLAVE machine. If you want to use Remote desktop additionally, you can of course do that.

    Apart from that, everything is correct.

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • I
    I

    Ok, that'll clear up a great deal, thanks. Would have been neat though, to be able to operate the slave from your master computer from within the sequencer. If it can be done with remote desktop, why not implement something similar directly in VEPro?

    I'll dive into this further when time permits. Several workflow issues to sort out. Looks very interesting though.

    T
  • PaulP
    VSL Team
    PaulP

    Hello iqbahl,

    There are several reasons why we don´t implement that features. One of them is the fact that you will need the screen real estate on your slave computer for big setups, another one is that  this would take quite some more processing power, another one is that there are already solutions for this available.

    Hope it works for you!

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • civilization 3C
    civilization 3C

    in practice, it's generally better to treat the VE Pro projects as projects in their own right, saved on the slave(s) as metaframes and the instances decoupled from the sequencer, anyway. The seq. projects can take a lot longer to save and to load if the seq. host has to recall all of it, and quitting both more problematic. IE: (creating a 'template' and) loading all of the VE Pro data first, completely, before connecting.

    If you build the instrumentation from [an empty instance of VE Pro in] the seq. project, once you have something, you can *preserve* that frame at the slave end, name it something useful and then save as (vi frames and) metaframes, then decouple.