Dubstepforum.com

If a 32 bit operating system is limited to by Windows memory manager to a maximum of 4Gb physical address space, it's advisable to use a 64 bit OS to get the most out your RAM.

Does this mean that a 32 bit DAW will likewise not be using the full capabilities of RAM, for example 16Gb?

http://stackoverflow.com/questions/5916 ... -64-bit-os

I guess the answer is that it won't be, but it could be.

32-bit programs will only be able to allocate and use a maximum of 4Gb of RAM to itself, just like the limitations of a 32-bit OS.

Dub Fiend wrote:32-bit programs will only be able to allocate and use a maximum of 4Gb of RAM to itself, just like the limitations of a 32-bit OS.

So having 16Gb of RAM with a 32-bit DAW would be pointless?

wub wrote:

Dub Fiend wrote:32-bit programs will only be able to allocate and use a maximum of 4Gb of RAM to itself, just like the limitations of a 32-bit OS.

So having 16Gb of RAM with a 32-bit DAW would be pointless?

Totally pointless, it'd be a waste of RAM. That's one of the main reasons that they switched to 64bit processors. All CPUs these days are 64bit, so it's advisable to use a 64bit OS and 64bit software. The code will run slightly more efficiently too.

wub wrote:

Dub Fiend wrote:32-bit programs will only be able to allocate and use a maximum of 4Gb of RAM to itself, just like the limitations of a 32-bit OS.

So having 16Gb of RAM with a 32-bit DAW would be pointless?

Unfortunately so. The only downside of running a 64-bit OS is that you need a decent VST Bridge if you're using 32-bit VSTs - bad example would be the Bridge on Cubase 5 when that first came out; the latency was unbearable so I switched back to 32-bit.

In honesty, I've never had an issue running 32-bit DAWs on a 64-bit OS; currently I'm running Win7 with 8Gb RAM and I'm still using 32-bit Cubase 5 and I've never had an issue. Unless you're running monster VSTs with massive soundbanks and like, 32 tracks chockablock with effects then you will never really encounter issues. Otherwise, good use of busses or freezing audio will bypass the negative issues associated with 32-bit DAWs.

Yep, running Windows 7 64 bit and FL Studio 32 bit with few problems. The bridge to 64 bit is a little wonky, but liveable. I ought to make sure I am running 32 bit versions if my VSTs have them though.

A few things wub, fl has a 64 bit beta out now, or have they released the 64 bit retail version already? Most of your vst's should have 64 bit versions already. Just go 64 from the start, as you build this system, only install 64 bit versions of your vsts. That's not such a hassle for you as you are going to have to install everything from scratch anyway.

If you insist on using 32 bit fl on a 64 bit system, fl and plugs will only be able to address 4gb, but your system will be able to address the rest, so you still benefit in that fl won't be competing with your system for scarce ram resources.

Don't look back dude. 64 bit from here on out. And truss, I'm still running my main production pc in 32bit, but it is a dead end.

I'm reluctant to switch to 64bit FL just because I'm unsure about the bridging... atm I'd guess that at least 50% of my VSTs are 32bit only, and since I have enough issues already with 64bit bridging idk if it's worth it... any advice on this from people who switched? Having said that more and more I'm starting to hit the RAM limit within FL which is quite annoying...

Anither thing I have noticed is that if your running a 64 bit windows system and plan on having/using over 16 gigs of ram you need to have the 'Professional' version, not home premium etc

Ok, Professional isn't an issue, will add to the list


May as well jump into 64bit, not like they're suddenly going to start going backwards