michiel, besides we are turning over to windows now, as often answers are *yes and no* ...

Vienna Ensemble starts with about 50 MB RAM usage ... each inserted VI instance will add some amount ... of course a lot of information seems to be redundant, but in fact you would need the *space* to save a complete set of settings (you know the math ... 12  x 12 x 12 x all parameters) ... so 20 MB seems not too much in my view ... you might also notice RAM usage *toggles* a little bit depending on the subset of the GUI you are currently displaying ...

the garbage collecting .... well, this term seems not to fit for me in this case ... collecting garbage means basically to remove unused instances, processes, free unused memory, ect .... with sample streaming the processes and memory is not *unused* but just *currently not used* ... in both operating systems the memory requested for the sample headers is *marked as not to be paged out* ... whereas winXP does fulfill this requirement, apple has confirmed OS X does not and i'm currently not sure if VISTA really does (sometimes im under the impression it does not 100%) ... in any case i don't consider VISTA's prefetch technology as ideal solution for sampling machines.

however there is a lot more stuff which can be paged out and might affect the overall performance of a machine after pausing for a longer time ... wherever possible i therefore set the page file to *don't use* ... unfortunately some applications don't like that at all, so i'd try to set the lowest value possible to avoid windows trying to be more clever than the user ;-)

we must not forget ourdays systems are much more *multi purpose* operating systems than earlier ones and in my opinion less adjusted for realtime applications than ever before ... we need to handle that ...

to be sure how much RAM VE /VI takes always watch the task manager's process tab, maybe even inserting the virtual memory column - if MemoryUsage drops without reason (unloading an instrument) than the OS has tricked out the application ... i noticed that on XP and VISTA 64 on a 8 GB machine when loaded samples in VE went beyond ~7,5 GB ... nothing what makes sense of course, i've just been curious what happens ...

christian

@jbm said:

Since we still don't have a genuine 64-bit Mac OS, and most people aren't running XP x64 or Vista 64 (with appropriate drivers, hosts, etc.), they've made something that will not only work "in the meantime", but will also address the maximum possible RAM *now*. Nice decision, on their part, I think. --- J.

J.:

According to Apple, this is not quite true, Leopard is a genuine 64 bit Mac OS: "Leopard enables developers to build complete 64-bit applications using the Cocoa, Quartz, OpenGL, and X11 GUI frameworks. You can even use 64-bit Java on capable Intel processors. And the 64-bit and 32-bit versions of the libraries are built from exactly the same code base, to ensure a consistent experience for both developers and users." 

Currently there is no Leopard compatible 64-bit of VE - hence the need for the workarounds mentioned. There is a complicated history behind all of this that has been discussed on other threads here - - suffice it to say that you'll notice the absence of mention of a 64-bit framework for Carbon - - at the WWSC 2006 Apple stated that it would release a 64-bit version of Carbon, then, a few months before the release of Leopard, Apple announced that it had decided not to do so - - a decision that stymied many developers. 

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

@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

@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

 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

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

Cheers....

@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 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