Vienna Symphonic Library Forum
Forum Statistics

196,625 users have contributed to 43,021 threads and 258,416 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Vienna Ensemble RAM usage question
  • C
    C
    last edited
    last edited
    "It appears that VE (standalone and plug) as well as VI use approximately twice as much RAM as it should, as indicated in the Activity Monitor. any suggestions would be very helpful. Thanks VE (build 2869) VI 1.14 Mac OS 10.4.11 MacPro 2.66 Dual-Core 8 GB RAM" ddunn.
     

    @cm said:

    ddunn, what makes you assume VE or VI is using twice the RAM as it should? each loaded stereo sample needs 64 KB memory for the preload buffer, the application (or plugin) as such also needs some MB of course ...

    please note that RAM usage in the activity monitor will show a certain amount of used RAM even if you unload some instruments due to memory management - loading the same instrument again needs only to restore the pointers then which speeds up the process, this memory can be used by other instruments when needed though ...

     Hi Christian- or anyone else in the know.
     Maybe I'm missing what you mean in your reply here, but having just loaded up a second VE2 with 3 woodwinds presets,totalling 891MB, my available RAM went from 7.17GB to 5.16GB!
     Is this normal?
     Colin
  • cmC
    VSL Team
    cmC

    are you referring to RAM or MEMORY? please consider memory definitions in OS X - only the number for *wired* is memory located in RAM, so loading 891 MB should increase this number by 891 MB (add some MB for additionally opened instances).

    christian

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

    @cm said:

    are you referring to RAM or MEMORY? please consider memory definitions in OS X - only the number for *wired* is memory located in RAM, so loading 891 MB should increase this number by 891 MB (add some MB for additionally opened instances).

    christian

     

     Cheers Christian.

    Just lost as to why it loads into 'Wired' and additionally roughly the same as 'Inactive'  thereby reducing 'Free' by 2GB.

    That besides VE2 is now crashing as soon as the total wired memory goes over 3GB. This is with either 2 or 3 VEs none of which are near 3GB in themselves. My understanding was that every instance of VE could address 3GB  by itself.

    I am using VE as a plugin and have had no problem processor-wise with 30 odd instruments over 4 VEs, but now having 11GB RAM have been attempting to load presets and VE is consistently crashing at the same point. Logic remains active.

    Additionally, as soon as VE reaches 2GB in Real Memory in Activity Monitor, the RM figure jumps to 16,777,216.0 and remains there.

    My system is MacPro 2x 2.66 Ghz Dual Core, Logic 8.0.2, OS10.4.11. The same happens with last 2 versions of VE.

    Any ideas? Cheers..

    Colin

  • cmC
    VSL Team
    cmC
    last edited
    last edited

    @ct1961 said:

    as soon as VE reaches 2GB in Real Memory in Activity Monitor, the RM figure jumps to 16,777,216.0

    a known bug in OS X, caused by using signed instead of unsigned integer resp. interpreting an unsigned integer as a signed one (max range for 32bit integers is 2^32-1)  what somehow reminds me to a quotation attributed to Bill Gates: “640K ought to be enough for anybody.”

     

    more info on memory definition in OS X here

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

     Read and understood! Cheers.

    Am I right in my belief that I can open up to 4 VEs as plugins in Logic with each addressing up to 3GB? The crash is occurring at a total of 3 and a bit GB wired.

    Colin

  • cmC
    VSL Team
    cmC

    well, the 32bit nature is a real hindrance ... usually i'd say you should be able to load about 3.2 GB, we can reproduce that everything gets unstable beyond 3.5 - 3.6 GB, but some reports indicate this can also happen with just 2.6 GB - it might depend on configuration and/or condition of computer ...

    i'd like to leave more detailed help to our mac support though, christian

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

    Cheers....

  • J
    J
    last edited
    last edited

    @ct1961 said:

     Read and understood! Cheers.

     

    Am I right in my belief that I can open up to 4 VEs as plugins in Logic with each addressing up to 3GB? The crash is occurring at a total of 3 and a bit GB wired.

     

    Colin

    Hi Colin, I may be wrong and shot down in flames but as far as I am aware however many instances of VE you open as a plug-in the 3GB (approx) limit is across all of them rather than each instance. I've got 32Gb of RAM and currently VE's start creating a problem with total addressed memory around 3.2GB (though I take this reading from the virtual memory column in Activity Monitor as this, for some reason, seems to more accurately chart when apps are near their max RAM. Logic, by the way starts to become unstable after 3.5GB and unusable after 3.9GB on my system. Regards, Julian
  • C
    C

    Hi Julian. 

    I believe you're right. I was sure I had read a post, more recent than above, that I could open 4 with up to 3GB each but obviously not. Will now have to figure out how to route a standalone version back into Logic.  Cheers...

    Colin

  • J
    J
    I don't use the standalone but I think each one of these has it's own RAM allocation ( 2 VE standalones = 6GB max) Julian