Vienna Symphonic Library Forum
Forum Statistics

182,266 users have contributed to 42,216 threads and 254,738 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. VE3 and Multiple Instances on Mac slave

  • VE3 and Multiple Instances on Mac slave

    J
    J
    Apologies if this has been covered already. VE3 rocks and is working great on my two Mac Pros. However, I'm still not sure how to properly setup multiple VE3's on the slave mac. In the video tutorial VSL has three different VE3's open, each with a different name and app, but they don't go into how it was setup.
    I tried using multiple plug-ins of VE3 on my host, but they are multiple instances within the same VE3 on my slave and if I try and load anything into them the whole things crashes. Plus, I can't name them the way the setup doc suggests (there are all the same ip address), so I must not be going about it the correct way.
    I had them working all on my host and understand how it goes, with duplicating the app and re-naming. I just don't know the next step - integrating those duplicate apps into the network for VE3.
    Any advice appreciated!
    Jason
  • T
    T
    Jason

    With VE3 in host/slave mode you don't need to setup multiple instances like you did with VE2. Just point each new instance of VE on your DAW to the same IP address and lo and behold the slave device will create multiple instances for you.
    Regards

    Tim
  • P
    P
    My question here is: Is it better to create a separate VE3 instance on your main computer for each stereo stream you want (thereby creating a separate VE3 server instance on the slave)? Or is it better to use just 1 instance on both comps and use the different H/W outs available to that instance? Basically just wondering what's more efficient: 6 instances using 1 stereo pair each? Or 1 instance using 6 different stereo outputs. Does that make sense? Thanks
  • J
    J
    Tim,
    Thanks for the quick reply. Unfortunately, that's exactly what I was doing, but for some reason what opened fine in three separate apps of VE2 on my main rig crashes the server on my farm machine. I can get two of the three instances loaded, meaning the VSL samples loaded on the farm, and it quits in the middle of the third one.
    I have no problem getting the VSL Servers running on both machines and talking to each other - it just seems to be that little detail of actually loading all the sounds... :)
    Jason
  • J
    J
    I figured out why VE3 is quitting - it's maxing out the available RAM it can address within one instance of itself. All three of my "plug-ins" of VE3 on my master mac are opening (or trying to open) within one instance of VE3 on my slave. The VE3 manual has half a page (pg. 9) about running multiple instances of VE3 on the slave computer to address as much RAM as your computer has. How can I do this? My slave is the newest 8 core Mac Pro with 16 gigs of RAM.
    UNLESS...the VE3 Server is "holding" each instance of VE3 and those instances can EACH hold 2.4 gigs of RAM. It's a little confusing in the instructions, because it talks about duplicating the app to access multiple copies of VE3. Is this just for the local machine?
    PAGE 9 of the VE3 manual:
    "Attention Mac: Under Mac OS X, you can instantiate more than one stand-alone Vienna Ensemble application by copying the Vienna Ensemble entry in your “Applications” folder and giving it another name. Vienna Ensemble can address up to 2.4 GB RAM – in addition to the latest Vienna Instrument’s 3 GB …
    If used as a stand-alone instance on a dedicated Vienna Ensemble computer running OS X, each Vienna Ensemble can address 2.4 GB of RAM. This way you can address as much RAM as accessible on your Slave Computer. "
    Thanks again!
    Jason