Vienna Symphonic Library Forum
Forum Statistics

202,015 users have contributed to 43,278 threads and 259,391 posts.

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

  • Dummy VST Host trick - cannot achieve on mac?

    Hi, I have been trying to achieve DG's dummy host trick on a Mac Pro. It seems impossible to take advantage of shared memory. I have tried running parallel VE instances - doesn't work. I've tried Rax - doesn't work. Has anyone achieved this? Am I the dummy here? Thanks anyone. Ben

  • You aren't trying to use standalones are you? I suggest that you give a bit more information about your setup and sequencer, so that others can have a go at testing it for you.

    DG


  •  Hi there.

    Yes I am using standalones, as a rule. However I have tried with the Server method too. Everything works fine really, including the Server method. I am just trying to get round the re-loading problem, in order to use the Server method more efficiently. Which would be preferable.

    My work method currently is standalones that just load up in the morning, avoiding the Server completely for now. I would like to get the server methiod working though.

    I am running (in this case) a single Mac Pro 2.8 with 10 GB Ram (soon to expand to 16GB). All sequencing is done on a separate Mac Pro. Audio is hooked up via a rack of 2408's with a Nanoclock WC distributer, and MOTU midi interfaces. For the server, when I try it out, I have a completely seperate Gb Lan with switch, utilising the dual Ethernet capabilities of the Mac Pros. There is a G5 Quad waiting in the wings on this network too (also with 10GB Ram).

    Basically I have read that users are abble to trick VE into loading samples more quickly by having these samples already in RAM. My problem is I am unable to achieve this vis either: loading up a redundant VE instance (as a standalone) or loading individual Vienna Instruments into a host. For the host I have tried Rax. Also tried launching a loaded VE into Rax, and tried Cubase too as the host.

     I was just wondering if anyone had managed to do this on a Mac at all. Perhaps memory is shared differently than on a PC.

    When I load up a standalone VE, by opening a desired project/setup previously saved from a server instance, when that server instance is re-loaded form scratch (with the standalone still loaded), Activity Monitor shows two instances of VE (one being the standalone, the other being the Server) both using separate memory. Say about 2GB each.There seems to be no acceleration of loading.It's tricky to explain, butin a nutshell the Mac seems to segregate all memory accross applications including Vienna Ensemble.

    To recap: I have created a project called Strings, with outputs etc all setup.

    I launch VE standalone, and load that project. It takes a while.

    I launch my sequencer on the other Mac, and instantiate Vienna Server. I connect.

    In the slave, (currently holding a loaded standalone) VE pops up as it should and starts loading an identical project (previously saved).

    Loading is at normal (lengthy) speed.

    However, if within a sinlge VE instance (be it standalone or server, no matter), if I unload an instrument, and then reload it, it loads fast. Kind of temptingly frustrating!

    It's seems I am stumped. Or missing something obvious.

    Thanks for your time as usual,

    Ben


  •  Delving a bit deeper, I realise that what is being suggested might be to launch, say, Rax frmm the machine hosting the sequencer, not the machine hosting the Veinna Ensemble Server. Is that right?

    Ok, but: On a mac at least, we hit the 32bit OS wall, as the Vienna Server on the slave is just a single entity. So launching more VE plugins on the sequencer will be limited by this on the slave. Whereas, standalones with soundcards are effectively unlimited on the mac (memory-wise) as each instance is self-contained. The inverse of the original problem I suppose!

    I have yet to test (due to lack of time) whether TWO vienna servers could be run at once on the slave. I can't imagine how this might work however, as the plugin on the sequencer would have no way of knowing which one to "load". 

    I realise I am mixing my problems in this post (ie memory capacity VS load speed).

    Perhaps I should skip all this and run bootcamp?

    Back to work....


  • You will run into the memory limits quite quickly on your slave Macs using VE3. I would suggest running Bootcamp (XP64) on these machines, as not only will you be able to use as much RAM as you have, but my trick will solve your loading problem as well.

    As you have noted, standalones each use their own memory block, so my trick only works with plugins. However, this is the ideal way to work, as all your settings are set with each project, making it much easier to recall at a later date. Assuming that by then you aren't using VE4......!

    DG

  • last edited
    last edited

    @benbartlett said:

     Delving a bit deeper, I realise that what is being suggested might be to launch, say, Rax frmm the machine hosting the sequencer, not the machine hosting the Veinna Ensemble Server. Is that right?

    Sorry, I forgot to answer this. Yes...!

    DG


  •  Thanks DG. I knew you would know how to expain it.

    Kinda need a family therapist (between me and my macs) before doing bootcamp....or at least a few days down time to get it working and transfer the library to suitable drives etc etc. But perhaps it will be worth it.

    In the mean time, I'll stick with my hardwired, multi standalone method for now, as I know it works.

    You right of course about project settings though. As I run it now, I MUST remember to programme key switches at the fron of each project...

    Thanks again for your time.

    Ben Bartlett.


  •  Sorry about this - Windows dummy here.

    If I go o Bootcamp, I am wondering:

    If I instantiate more than one VE on the Daw machine, does windows create more than one VE instantiation on the slave like the Mac does? And in this case, presumably, they share the (64 bit) memory space?

     I just wasn't sure how windows handles this.

    Also what version of windows would be best to run VE on via Bootcamp?

    Thanks.


  • last edited
    last edited

    @Another User said:

    Also what version of windows would be best to run VE on via Bootcamp?

    If it was a regular PC, then I would say XP64. However I would suggest that you question the Macheads on this forum, in case there are any silly hoops to jump through with Bootcamp.

    DG

  • Thanks again. B