Vienna Symphonic Library Forum
Forum Statistics

182,201 users have contributed to 42,210 threads and 254,707 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Networked VE3 must re-load everytime I switch projects on DAW

  • Networked VE3 must re-load everytime I switch projects on DAW

    B
    B

    This is a problem. If I am running a sequence on my DAW accessing VE3 server on another Mac, and when I change to another sequence which only needs the EXACT same setup, VE Service on the Slave re-loads all over again.

    One of the main points (for me at least) of running VE as a slave is that we AVOID this reload.

    Now, I can understand why this has been done in this way, as VE Server must behave like a real plugin in the DAW (which would of course reload in the same manner).

    Could it PLEASE be made an option for the Service on the Slave to ask (via the plugin): "do you wish to reload". If I KNOW that my sequences are setup to address the same sounds sets (as they are currently, by running VE as a standalone on a separate machine, via MIDI and ADATs) then I would KNOW that my sounds will link up.

    Waiting for Vienna Service to reload is, frankly, a complete showstopper for this networking solution, brilliant though it is. My thinking is this: I must switch constantly, all day long, between different sequences on my DAW, as I work my way through numerous music cues for  my projects, which DELIBERATELY SHARE the same setups (not just on VE, but other standalone VSTi's too accross my studio).

    For now, I am back to a rack of 2408's. Obviously, a 64 bit version of VE will still vastly improve this (non-networked) workflow. But jut think: if I load up 25GB worth of samples or more on a slave, networked, and have to wait for this to reload everytime I switch sequences, I will be wasting a lot of time.

    In the real world of music production, sadly, we must sometimes work at great speed, swapping around sequences often with clients present in the studio.

    So, my "feature request", if you will, is can VE3 be tweaked to allow an option that avoids a re-load somehow?

    Thanks,

    Ben 
  • D
    D

    This has been requested by other users and is currently being lookinged into, according to the powers that be.

    I have a little trick to avoid these long loading times using FXT, but I don't know whether or not it will work with VE or even on OSX, for that matter. Do a search for DG and FXT in the VI section of the forum, and you should find some info.

    DG
  • P
    P

    Dear VSL team, please make this a top priority! I'm considering buying a Mac Pro as a VSL slave, but I'll wait until this is sorted out. I think the whole point in using a server is that you can switch projects or restart the sequencer without reloading samples...

    Cheers

    Pitt
  • D
    D
    last edited
    last edited

    @PierreFunck said:

    Dear VSL team, please make this a top priority! I'm considering buying a Mac Pro as a VSL slave, but I'll wait until this is sorted out. I think the whole point in using a server is that you can switch projects or restart the sequencer without reloading samples...

    Cheers

    Pitt

    If I were you I would also wait until 64bit is possible on OSX, or be prepared to run XP64 or Vista64 via Bootcamp.

    DG
  • B
    B
    With all due respect, I think the last poster doesn't quite see the point. It's irrelevant how much (Ram) we can load. It's the fact that it must RELOAD each time we switch projects. In the meantime, multiple instances of VE works well on a mac while we wait.
  • D
    D
    last edited
    last edited

    @benbartlett said:

    With all due respect, I think the last poster doesn't quite see the point. It's irrelevant how much (Ram) we can load. It's the fact that it must RELOAD each time we switch projects. In the meantime, multiple instances of VE works well on a mac while we wait.
    And as I said earlier, I can load projects with 7.5GB in my template in around 30 seconds.

    DG
  • D
    D

     I agree this should be made a priority for VE3. Reloading each time partly defeats the point of having a slave computer with an orchestra template ready for use in any project / cue. Hope a new version is in the pipeline! Best,

    David 
  • R
    R
    Here! Here! Yes, this is a total pain! VE 3 is incredible!....but the reload every time is a pretty counter productive. Please, please, PLEASE make this an "option"! Thanks!
  • O
    O
    Yesss! I agree! Dear Vienna Team: PLEASE make it a priority! Otherwise it´s a pain, a mistake in design. Even with 64bit-PCs: it makes no sense to reload 16GB for a little cue again and again. Just imagine 32GB!!!... Many of us are film composers, so: Is there hope soon???? Best Oliver
  • D
    D

    Oliver, please try my trick whilst you are waiting for an update to VE3, even if it is going to be possible. At least re-loading will only take 30", if it works with VE3 as well as it does with FXT.

    I don't know why people aren't willing to try things that are suggested. The time taken to test would probably be less than re-loading one cue! [;)]

    DG
  • R
    R
    Hey DG...I can't seem to find your post? Thanks
  • R
    R
    Ok...I think I found it....not really sure what a 'chainer' is though(?). Being a Mac user, I'm not sure if I'm a viable candidate for this work around. Any insight would be appreciated! Thanks
  • D
    D
    last edited
    last edited

    @rpmusic said:

    Ok...I think I found it....not really sure what a 'chainer' is though(?). Being a Mac user, I'm not sure if I'm a viable candidate for this work around. Any insight would be appreciated! Thanks

    Chainer is just a simple VST host. If you have something similar it would be worth testing out. Bidule maybe?

    DG
  • R
    R

    Thanks DG....I looked at 'Bidule' at one time but decided to pass since I didn't have an 'engineering degree' [:D]

    Anyway, I'll revisit the site and see if I can figure out a way to incorporate it into my system.

    Thanks again for the reply... 
  • B
    B
    30 seconds for 7.5 GB is WAAAY too slow. We need snap snap bang - loaded. If you translate that to 16GB that would be a whole minute. Plus, each load and re-load can slightly fragment memory, eventually leading to unnecessary memory consumption. At present, a slave hardwired is really the only method right now, if you are working on multiple cues or projects at the same time. We already have the discipline to make sure our templates "fit". Thanks.
  • B
    B
    Regarding Bidule: It's simpler than is at first apparent to set it up. However, it drops midi when it's fully loaded. And delay compensation (in Cubase at least) is not covered properly under re-wire (if you use Bidule that way). As a standalone, Bidule offers no real benefit now that VE can support 64 outputs - allowing you to pretty much address any chunk of your hardware you want.
  • H
    H

    The next version of VE3 is in developement, and will offer this feature of samples stay loaded if you switch projects in your sequenzer.

    It's a major developement step and will need some time. We expect to have it ready in late summer/early fall.

    best

    Herb
  • R
    R
    Bavo Herb! From the film scoring community, BRAVO!
  • O
    O
    Thanx a lot Herb for a clear statement.!!! Best Oliver (Does it have to be that long?))))))))
  • D
    D
    last edited
    last edited

    @benbartlett said:

    Regarding Bidule: It's simpler than is at first apparent to set it up. However, it drops midi when it's fully loaded. And delay compensation (in Cubase at least) is not covered properly under re-wire (if you use Bidule that way). As a standalone, Bidule offers no real benefit now that VE can support 64 outputs - allowing you to pretty much address any chunk of your hardware you want.

    No, you don't understand. Nothing passes through Bidule. No MIDI; no audio. It is only a way of getting the samples loaded into plugin memory. The advantage being that you can load cues much faster, as VE just checks which samples are already loaded into VE plugin memory. It also means that the sample settings are saved with the project, rather than having to save lots of standalone versions. Obviously I haven't checked that this works with VE, as I was just offering a suggestion to cut loading times between cues from 15 minutes (in my case) to 30 seconds.

    DG