Vienna Symphonic Library Forum
Forum Statistics

183,771 users have contributed to 42,321 threads and 255,162 posts.

In the past 24 hours, we have 6 new thread(s), 15 new post(s) and 39 new user(s).

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

    Bidule: Thinking about it - yes as a plugin, each VE instance will occupy the same space. So I seem to be, again, missing your point! Sorry.

    Indeed, I tried hosting VE on a separate machine within cubase and hit a memory wall regardless of how many instances. But just to be clear about Bidule, at least as a re-wire (and standalone in as far as I have tested it) it seems a little shaky. Although it's an extraordinary piece of software. I have read of users progamming Bidule to recognize pitch on incomming audio. Very advanced...

    For me the following is working:  

    2 Instances of VE on a single MacPro with 10GB Ram.

    2 2408's, shared by both instances (ie they are "polite" to each other about sharing a soundcard).

    Instance 1 is using 2.39GB

    Instance 2 is using  2.73GB (not bad for 32 bit)

    The ability of VE to now address (and share accross) 64 outputs as redically changed the potential of all this, avoiding the need for multiple sound cards. 96 outputs would be welcome, as that's the limit of the 424 card.

    Ben 
  • J
    J
    This could also benifit users (like myself) of VE2. One could open and close different "songs" in Logic and have all the samples still available. In the long run, this may become even more important than the VE3 option, since with 8 cores and maybe future 16 core computers, there is (will be) no longer the need for 2 computers.
  • D
    D
    last edited
    last edited

    @benbartlett said:

    Bidule: Thinking about it - yes as a plugin, each VE instance will occupy the same space. So I seem to be, again, missing your point! Sorry.

    Ben 

    Ben, I'm probably not explaining it very well. If you really would like a more detailed explanation of how it helps, then I'm happy to give it, but I don't want to waste your time if it is not really useful to you.

    At the moment it is all theoretical anyway, as Mac does not have 64bit applications yet. However, I'm assuming that this will be rectified soon(assuming that Apple has already released the required code), and in that situation you could well be loading many GB of samples within multiple plugin instances. In that case my workaround could work very well for you.

    Over the next few weeks I'll he temporarily adding one more 8GB slave to my setup, and that will most likely increase my writing template to around 10GB. I certainly won't want to be hanging around for 20 minutes to load each project!

    DG
  • P
    P
    last edited
    last edited

    @DG said:

    If you're not interested in audio flowing into the sequencer, then just use a standalone and MOL.

    Of course I'm interested in audio flowing into the sequencer by network and don't want to buy big, expensive audio interfaces...
  • S
    S

    Just run into this thread as I'm building my 32gb slave.

    Needless to say I too would love to see this feature when I could just use the same 30gb template and keep it on all the time.

    I'm glad that Herb is working on it.

    DG, I thought you were jocking about 16gb loading in 30 seconds.  Currently I have to wait for about 3 minutes for 1.5gb to load on my dual core 2 duo 2gb pc.

    sasha 
  • D
    D
    last edited
    last edited

    @sasha said:

    DG, I thought you were jocking about 16gb loading in 30 seconds.  Currently I have to wait for about 3 minutes for 1.5gb to load on my dual core 2 duo 2gb pc.

    sasha 

    This is why I use my workaround. The first time I load my template it takes 15 minutes. I can't be having that more than once a day.

    DG
  • P
    P

    Ben -

    Hi - long time no see! Hope you are well.

    Have you tried using AUlab to instantiate the VE3s and then address these from Logic in much the same way as if you were just using AUlab to host any other plugs?

    I haven't tried this so I dont know if it will work, but if you have AUlab (free from the Apple dev kit website) you might give it a go. It would fix your problem immediately - the AUlab sits happily in the background 'holding on' to the VE3s while you quit Logic and reload cues.

    Cheers,

    Paul Thomson 
  • T
    T
    I'm going to give it a try. On of my PC servers just died and I'm finishing upgrading it tonight to a Quad 8 gig with XP64. Also if you don't want to deal with having to set up Bidule, (which is a bit of hassle) you can get RAX to host VST for mac, which works great and is super simple to use.
  • T
    T
    DG- I'm assuming that you boot up your other host app to hold the samples, instance VE3 and then in the slave, assign all the same VI that you have loaded into the real VE to the dummy VE so that it holds all the samples even if your working VE goes offline?
  • D
    D
    last edited
    last edited

    @Tripit said:

    DG- I'm assuming that you boot up your other host app to hold the samples, instance VE3 and then in the slave, assign all the same VI that you have loaded into the real VE to the dummy VE so that it holds all the samples even if your working VE goes offline?

    I'm using FXT but the theory still holds. I have a working template, so even though my cues may have slightly different requirements, it is only those different samples that have to be loaded if I switch cues.

    DG
  • T
    T
    Thanks. Yeah, I use all templates as well. They only vary slightly depending on the cue or film.
  • P
    P

    But lets say you have the 'dummy host' (AU lab or whatever) to load up the template using VE3 instances. When you then load Logic with its own VE3 instances wont it try to instantiate another 3/4/however many instances on the slave duplicating the first lot?

    I would love an answer to this from the Vienna crew as it will take me a long time to set up the entire template again whichever way and so I want to make sure it works frst!

    Cheers

    Paul 
  • D
    D

    Why would it load twice? it would certainly load more VE instances, but the samples themselves would only be loaded once. If you're not sure it will work, then just try it with a small template first.

    DG
  • P
    P
    Ahh - I see. I get it now! Unfortunately it fails on my 64bit XP due to the graphic bug of going over however many instruments it is.. I'll have to check the threads out on that and see if I can get around that. Its still not a great solution long term as the extra instances will use a lot of memory and system resources so I hope that the VSL team are working on a proper solution. Thanks anyway! Cheers Paul
  • D
    D
    last edited
    last edited

    @PaulThomson said:

    Ahh - I see. I get it now! Unfortunately it fails on my 64bit XP due to the graphic bug of going over however many instruments it is.. I'll have to check the threads out on that and see if I can get around that. Its still not a great solution long term as the extra instances will use a lot of memory and system resources so I hope that the VSL team are working on a proper solution. Thanks anyway! Cheers Paul

    VSL has already said that they are working on a solution, but it will not be ready for a while. In the meantime, there are a couple of things that you can do to improve things:

    1. Make sure that you do the registry tweak, so that you can get up to 100 Instruments
    2. Set up your dummy very carefully. You don't have to make the Instruments the same, as long as the samples are loaded. Therefore., I'd use as few instruments as possible, and load them to the gills in terms of matrices and cells.
    FWIW I found that with FXT there was very little difference in system resources, because the dummy doesn't actually do anything, and as long as you keep the number of instances and Instruments to a minimum, there shouldn't be a huge memory overload either. Of course this depends on how much RAM you have. If you are sailing close to the wind, my trick won't work I'm afraid. However, a Quad core with 8GB RAM will only cost around £400 to build, so if you find memory tight, then just whack another PC on the end of the Network.

    DG
  • T
    T
    DG is correct. I tried it last night. I had a brass template that was 2.75 gigs in size. I booted up RAX along side DP on my Mac daw and created another VE on the same slave, loaded the same template. My memory usage in the task manager went from 2.75 to 2.81 with the second "dummy" VE. So it only went up a small amount, the price of the VE itself. But here's the strange part. After I had done that, I was dealing with some other issues, and I needed to reboot my main daw, so I lost both VE that were in the slave. When I opened the project again, the slave daw booted in about 5 seconds. I guess that because the VL damon was still open and I was loading the exact same template, it didn't have to looking for the samples. After that I was rebooting my daw several times as I was trying to sort out a IAC issue. Each time, the slave VE loaded up in about 5 seconds. If that is how it's going to work, I'm not going to need to bother with a dummy.
  • P
    P
    Wow.. Now thats interesting. I'll check that tomorrow - see if the slave can hold the memory. That of course would fix the problem! Cheers Paul
  • S
    S
    • Question - I'm using Digital Performer as my sequencer, considering buying slave computers and running them under VE3.
    • Does this re-loading of sounds occur each time you open a new chunk (sub-sequence) or just each time you open a new project?
    • If it's each chunk, that's a real deal breaker for me.
    • If it's each project, that's not so bad, because I typically load a whole film score in separate chunks within one project.

      Please reply, thanks,
      --Stu Goldberg
  • cmC
    VSL Team
    cmC

    i have to admit i can't comment on the chunk technique (most of the time using win and trying to avoid DP support) - but i think i get the priciple ...

    basically sample data which is not already in memory needs to be loaded.

    say if a chunk contains only solo strings and you are loading now a chunk for chamber you need to wait.

     

    other scenario: you have a larger preset loaded across several instruments and are now opening a chunk which contains patches (or matrices) which are not already referred referenced, so you need to wait until the missing patches are loaded

     

    hope you can see it highly depends on the situation and what type of chunks should be loaded ...

    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • S
    S
    Thanks Christian, for your reply. So, to clarify, if each chunk in a sequence utilizes the same track layout and refers to the same sounds which are already loaded, then under VE3, switching chunks won't trigger a VE3 reload - correct? Please reply, thanks, -Stu Goldberg