Vienna Symphonic Library Forum
Forum Statistics

185,535 users have contributed to 42,395 threads and 255,527 posts.

In the past 24 hours, we have 0 new thread(s), 14 new post(s) and 47 new user(s).

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

    switching might behave different from (additional) loading - as long as patches are referenced they don't get unloaded.

    to stay with the figurative explanation: closing a *chamber chunk* having chamber not referenced from other tracks will unload chamber data, now opening another *chamber chunk* will reload chamber data, just opening an additional *chamber chunk* will only load the missing patches, since a certain amount of chamber data is already referenced.

    hth, christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • S
    S

     Thanks again Christian. I think it will work for me then...

    Best,

    --Stu 
  • P
    P
    last edited
    last edited

    @stu goldberg said:

    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?

    You can share any virtual instrument between different chunks by using V-Racks. Normally I have a chunk for every cue, and all my virtual instruments reside in the V-Rack. I can switch between chunks within a fraction of seconds. 

    Cheers, Pitt 
  • S
    S

    Thanks for that, Pitt. Great idea. Ideally, that's what I'd like to do as well.

    So you're running DP on a Mac, & the V-Rack on your Mac can address VSL instruments that are loaded into slave PCs in multiple VE3 instances, as well as some VE3 instances loaded on your host Mac?

    With that setup, what is your experience as far as reliability, latency and CPU load on the host?

    And you don't have to reload samples when you change chunks?

    If so, that's the ticket!

    Best,

    --Stu 
  • P
    P

    I don't use slaves (yet), but the V-Rack will hold ANY virtual instrument audio unit and keeps it loaded whenever you switch chunks, so I am pretty sure it works with VE3 as well.

    I'm working with V-Racks for over a year now, and it's very reliable. I've lots of sequences for every film (at least one for each cue, and these in lots of different versions), and I can instantly switch between the sequences. I haven't noticed any negative effect on CPU or latency. The only downside is that instruments in a V-Rack are not automatable. If you want to automate, say, the volume, then you have to route the output of the V-Rack VI into an aux track in the sequence. (But you can automate the MIDI volume, of course.)

    For me, V-Racks are the killer feature of DP ... read the manual (p. 659) and try it out!

    Cheers, Pitt 
  • S
    S

    Hi again Pitt,

    Yes, I've been using V-Racks also, since they were first introduced in DP. I have a huge Mach Five template as well as several Altiverb instances, which are always loaded into a V-Rack, thus always available from any chunk - I just didn't know if VE3 worked from a V-Rack.

    The obvious advantage would be to avoid the mandatory reloading of VSL samples - until we get the promised VE3 update.

    Has anyone tried this? (DP on the Mac, adressing multiple VE3 instances (loaded on slaves & the master computer) from within a V-Rack in DP).

    Please report how it's working, thanks. 

    Best,

    --Stu 
  • D
    D

    Hi VSL,

    Any news on that update to allow VE3 to keep samples in memory when switching projects?

    Is it still 'late summer / early fall'?

    Thanks,

    David 
  • PaulP
    VSL Team
    PaulP

     Hi David,

    we are working on it. It won´t be "late summer", sorry to say, but we ´re doing our best to be ready in fall (could be "late fall"). Software with that many OS´s to take care of is pretty hard to develop, especially with all the possible combinations and all the tests involved....

    Best,

    Paul 

    Paul Kopf Product Manager VSL
  • O
    O
    Hi, So any idea what the best workaround is on a Mac using Logic 8 until we get the VE3 update? I usually wait around 3 minutes for my orchestral template to load (on the slave) each time I change cue. My current workaround is making a coffee! Thanks, O
  • P
    P
    Hey O. Get RAX. RAX is an AU host for OSX. Then using RAX, instanciate an instrument on your slave, and load it to the gills with the presets etc that you are using in your main template. So now you have an (or possibly two) unusable and odd looking VI instance on the slave but duplicating all the currently loaded stuff. Now, just switch the off/on button on the RAX plugins to off (so audio streaming doesnt get confused). When you switch Logic sessions, Rax will 'hold' all the samples in memory, so loading up another Logic session takes a fraction of the time. Cheers! Paul
  • O
    O
    Hey Paul, Thanks for this. I gave it a go firstly using RAX. This didn't work so I tried the same thing using another copy of Logic on the slave. The problem I had (on both) was that the slave ran out of memory and froze - it's OK loading a full orchestra once, but loading it all in twice is a bit much. Is this the only Mac workaround?!! Thanks, O.