Vienna Symphonic Library Forum
Forum Statistics

186,358 users have contributed to 42,454 threads and 255,812 posts.

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

  • RAM footprint of disabled channels

    Hello,

    I’m currently redoing my orchestral template in VEPRO 6 (and MIR), and I wanted to have almost all my virtual instruments present, mostly disabled, so I just have to enable the instruments I want for each project.

    But I realized that a disabled channel still has a high RAM footprint. It’s difficult to measure, I tried to disable my whole VSL orchestra and it saved me only the half of the RAM, for some Kontakt instruments it seems to work well (samples almost entirely purged), for other it seems it doesn’t work at all.

    In short, after testing it, my solution is unusable as it overloads my available RAM.

     My questions :

    • What does exactly the disabling feature ? Are the MIR samples unloaded too ?

    •           Is there a different behaviour between VSL instruments and other instruments (specially Kontakt) ?

    •           Is there a way to do what I wanted to achieve ? (other than the Channel set which looses the setting of the Output…)

    Thanks for your help,

     Matthieu

     (Windows 10, Cubase 7.5, VE Pro 6, MIR Pro, 32Go RAM)


  • last edited
    last edited

    @matthieu.lechowski said:

     My questions :

    • What does exactly the disabling feature ? Are the MIR samples unloaded too ?

    •           Is there a different behaviour between VSL instruments and other instruments (specially Kontakt) ?

    •           Is there a way to do what I wanted to achieve ? (other than the Channel set which looses the setting of the Output…)

    1) It unloads all samples, of the instrument. MIR PRO IR Samples are not unloaded. 

    2) Not to my knowledge

    3) I'd work with disabled cells and use "Enable Cells on MIDI Activity" in the VI PRO Settings. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Hi Matthieu,

    if you think that MIR Pro's impulse responses use too much RAM, you can always reduce its IR cache size. The only disadvantage of doing so is that the positional IR-prerendering might take a bit longer when you add a new Instrument or move an Icon on a MIR stage.

    HTH,


    /Dietz - Vienna Symphonic Library
  • PS:

    Image


    /Dietz - Vienna Symphonic Library
  • Thank you Paul and Dietz.