FYI...resolution:

I installed 4gb of RAM. Ran the 3GB switch w/ the USERVA=3328. Virtual memory is turned OFF.

I can now get Cubase/VSL to load about 2.7-2.8gb of sample buffers, so, yes--C4 IS large address aware.

On top of that, Gigastudio, which uses kernel memory, can still load both my Bosendorfer 290 and (yamaha) Gigapiano. Although, it chokes if you load much of anything else on top of them. So, no need to buy a user mode piano instrument. Giga will get me by until I find a nice Yammy U1/U3 to put down here.

I did, for the record, first install 3gb total...but, while the 3gb switch did make Cubase/VSL "see" more RAM to load into, it didn't really change anything in the real world--it maxxed at about 1.7GB of sample buffers. Considering my OS boots into 110mb, and C4 uses about 100mb overhead, this factors correctly--the 3gb switch doesn't really work unless you've got more than 3 GB, even with the USERVA option set to 2.3 or 2.5gb, which are the options I tried. Like I said-it does make it "see" more, but it can't seem to utilize more than an untweaked default memory allocation.

Oh, yeah...this also dispells the rumor that the 3gb switch only works with XP Pro, as I'm running Home. I've long told people that Microsoft said that it would work with either version of XP, but people didn't seem to believe me--proof is in da puddin'.

Hi guys...it's been a while... [:)]

popmann, if you're able to load both of those pianos with the 3GB switch turned on, I would bet that you have a separate graphics card in that machine which uses its own memory...? On the tests I've made with the /3GB switch on machines with shared memory for the graphics driver I couldn't load much before GS choked.

Regarding the rumor that the /3GB switch wouldn't work with XP Home...it's false nowadays. If I remember correctly the support for 3GB in Home Edition came with an update, maybe SP1.

/Mattias

Rule #1 (for me) when building a PC system for ANY use...don't get a shared memory architecture video solution. Yes...256mb of RAM on a fanless ATI 9600. Even for a little web surfer, I've found integrated video (meaning the shared RAM, GPU-less on board variety) will cause noticable GUI drag--compared to a 10 year old graphics card (not that you could actually put a 10 year old card in a new PC, but...). 

Hello

How much samples can be loaded (in %) on a 8GB slave machine (64-bit), when using the complete SE Plus Extended VI (and using VE3 ?)

Thanks

Fred

here's the math: 133.370 samples x 64 KB per sample need 8.1 GB memory

since one could load up to appr. 7 GB used memory on a 8GB windows 64bit machine this would be a theoretical value of 85%

but: in a test i couldn't manage to get more than 3,9 GB load with the special edition only which has already 74.860 samples (or i've simply been too dumb to find the missing patches/matrices), so this means you can load every single patch and matrix from the Special Edition bundle into such a machine.

of course this wouldn't make any sense for working on a real arrangement, one would load a much more selective preset ...

christian

You also have to take the VE instances and VI's memory consumption into account.

Each VE is about 45mb and for each intrument instance you add its another 16mb - not much but it adds up. You typically end up with maybe 4 VE's with a total of say 50 instruments: Thats 1 Gb.

Thanks!

While I know It doesn't make any sense to have every sample loaded, I just love it when everything is ready to play.

But even at 70-75% of all SE loaded it's pretty cool.

Fred

Quick memory question:

I have a slave PC (3GB RAM, XP Home, 32 bit) running Plogue Bidule as a host with the 3GB switch enabled. I am currently loading 2.7GB of samples into several instances of GVI within Plogue. If I upgraded to 6 or 8GB would I be abe to load an extra 2.7GB into VE3 instances within Bidule, as I noticed that VE seems to occupy a different process in the RAM usage? Or would I have to upgrade to XP64 to do this?

Dom 

@DG said:

You won't be  load more than 2.7-2.8GB of anything in XP 32bit.

Thanks Daryl.  So that means anything combined or 2.7GB per process?

@DG said:

You won't be  load more than 2.7-2.8GB of anything in XP 32bit.

Thanks Daryl.  So that means anything combined or 2.7GB per process?

In total.

DG

Thanks. 64 bit upgrade is unavoidable then.... 

Dom 

Hi Mike, 

you can even mix different OS´s with VE PRO, as it works cross-platform. You can also run a 32-bit and 64-bit Server instance of VE PRO simultaneously on the same computer. 

Best, 

Paul

It is worth remembering that the thread is very old, and back when it started, a 64 bit o/s was not the norm, thus, back then, most computers could not address more than roughly 3.5 gigs of RAM.  That has totally changed now, and all VSL products are designed to be run in a 64 bit o/s, and indeed, some of them, such as MIR Pro, can only be run in a 64 bit o/s.

If you get more RAM, you will be able to use it.  Even if your sequencer remains a 32 bit one, there are ways VSL can still access your entire RAM.  Overall, your goals, your sample libraries, and/or if you intend to get MIR PRo, and what you intend to write will influence how much RAM you will need.  For example, the SE libraries need less RAM than the full collections.

For larger templates 24 gigs would be strongly recommended, and even 32 gigs could be of use.  Anything under 16 gigs may quickly become a bottleneck with larger orchestral compositions.  On the other hand, if you will be using just the SE libraries, 8 gigs would most likely be enough.

Off-topic side-note:

@noldar12 said:

[...] all VSL products are designed to be run in a 64 bit o/s, and indeed, some of them, such as MIR Pro, can only be run in a 64 bit o/s. [...] 

Technically, you actually _can_ run MIR Pro as a 32-bit application. It won't get you very far, though. 😉