Vienna Symphonic Library Forum
Forum Statistics

198,105 users have contributed to 43,100 threads and 258,722 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Is it possible to disable a Virtual Instrument temporarily in VE Pro?

  • Is it possible to disable a Virtual Instrument temporarily in VE Pro?

    T
    T
    I await more ram, in the meantime, my RAM is getting a bit thin. (8gig). It would be nice if I could disable stylus and a few other VIs TEMPORARILY while working on the end of the tune. In the track I am on, some of the stylus drums are at the beginning of the tune. I am working strings at the end of the tune. Is there a way to KEEP the VI inside of VE Pro but have it disabled, not using ram, etc. Temporarily. I don;t want to unload the VI or anything that is a hassle. Just a simple disable function such as is in pro tools or DP where I just shut the track off for the moment.
  • DietzD
    VSL Team
    DietzD

    The blue "ON"-button in the Channel List on the left should do the trick, doesn't it?

    /Dietz - Vienna Symphonic Library
  • K
    K

    That disables processing, but will not release the RAM. For that to happen the whole instrument plugin needs to be deinstantiated really.
  • T
    T
    OK, great. How does one “deinstantiate” then? It has been interesting being a beta tester for many companies because over the yrs, my greatest input to companies has been the “obvious” things in real world use that any given company misses. There are several implementations of my real world scenarios/needs in several well known products. I think Vienna missed an obvious need here. While your product has been a god send to me as far as using VI’s and I sincerely sincerely thank you, your product can still “max out”. It can also still be a waste of resources. Bouncing still needs to occur, if not to just finalize audio in any given project. The way VE is designed now, it wastes RAM. Why , after bouncing 5 string modules to audio, must a user keep eating that RAM? This make no sense. Also, why must VE take away the advantages of bouncing to audio to conserve resources? This is a standard practise and VE neglects it’s benefits if it cannot disable any given VI completely. The only way I can see things working to save RAM now is some sort of increment “down save” where after one eliminates a given plug in, one removes it and saves VE. Keeping old iterations in case one needs to go back. This is far from an elegant solution. Please make tracks and VIs such that they can be shut off with RAM usage recovered.
  • K
    K

    You can't deinstantiate the plugin without removing its channel in VE Pro at this point. Possibly a more elegant solution will be put in place at some point, but I can't make any promises there unfortunately. Little to no hosts provide this functionality as they just disable processing of the plugin when a track is frozen, which relieves CPU use, but not RAM usage.
  • T
    T
    So are you saying that in most DAWS, including DP, when my VI’s are bounced and the tracks are off, they are still using RAM? I don;t see how this is possible as 1) the track istelf is off. 2) The VI never loads when re-starting DP with it off. I can see the DAW using a small amount of something or other on start up by having the VI loaded as an AU, but if it is off, it should be off without RAM having been used. Now, if I turn it ON, and then off without re-starting DP, I could possibly see some RAM being held up. I think the same could go for Vienna. When a VI is off, and then you quit, when re-starting why would the VI load and use RAM? Please advise.