Vienna Symphonic Library Forum
Forum Statistics

199,393 users have contributed to 43,164 threads and 258,952 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. RAM usage - releasing ram if patch removed? How to reclaim ram?

  • RAM usage - releasing ram if patch removed? How to reclaim ram?

    J
    J

    Searched to forum, no results....

    Let's say I start the day with 3200mb of ram avail to VI (hosting in VE Pro slaves). Then, as I load/audition patches, the available "memory free" gets smaller and smaller. But it NEVER goes back up! ???

    Shouldn't unloading/removing a patch also remove it from the memory used? In the old days of hardware samplers (hell, software samplers too), unloading a patch reclaimed the available memory. If I am exploring (some would call it fishing) for the right sound, at some point (usually very quickly) I now have to:

    1. save all project and viframe data;

    2. save and close the host;

    3. restart the slave machine;

    4. Load the session...

    5. repeat as needed.

    Serious waste of my time. Shouldn't the software be smart enough to recapture ram that's no longer being used? Is this a feature or a bug? MacOS VI 5132, VE Pro 5436 as well as beta 5814.
  • D
    D

     AFAIK this is a feature of OSX.

    DG
  • J
    J

    It's not a feature of other software samplers. Yes, it's a feature for applications, but within the application if a file is loaded into ram, closing the file releases the ram.

    Launch Photoshop (CS4 or later). Load a bunch of large images -- load them all into ram if possible. Max out your machine. Close all the image files. Can you load more images now? Yes.

    Launch ProTools. Load 128 tracks with thousands of edits. Max it out.  Close the session. Can you load a new session now? Yes.

    Open VSL VI and load a bunch of large patches. Max out your machine. Close all the patches. You should be able to now load more patches, but this is a "feature" ?

    This does not sound right. hasn't there been a revolt of mac users about this "feature" ? Why would a professional choose to use VSL on a mac with this limitation? Would a Win7 slave eliminate this issue?
  • J
    J
    last edited
    last edited

    @DG said:

     AFAIK this is a feature of OSX.

    DG

    DG,

    If so, then loading gigabytes of Spectrasonics VIs into VEPro would make all subsequent uses of the slave machine useless.

    Try this:

    1. In VE Pro, load some LARGE Ominsphere and Trilian patches. Use all available ram.

    2. Delete the Omnishpere and Trilian instruments.

    3. Can you load anything else now? Yes you can. Your memory has been released.

    4. Restart your slave machine and relaunch VE Pro.

    5. Load VSL VIs -- use all available ram.

    6. Delete the instruments.

    7. Can you load anything else now?

    Why can't VSL VI release ram like other VIs? Can't blame the OS.

    Using MacOS 10.6.3, latest builds of VI and VE Pro.