@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
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).
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. 😉