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
200,898 users have contributed to 43,216 threads and 259,148 posts.
In the past 24 hours, we have 2 new thread(s), 10 new post(s) and 59 new user(s).
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
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
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. 😉