Bitwig

HamHat · Post by **HamHat** » Wed Mar 26, 2014 8:00 pm

Why is there no x64 release? Are there plans to make one? Yes this is a deal breaker for me, I have 32 gigs of ram I don't like the idea of being limited to 4.

EvilDragon · Post by **EvilDragon** » Wed Mar 26, 2014 8:02 pm

Again... GUI is hosted in a 32-bit process, but all plugins are hosted in their own processess, so if it's a 64-bit plugin, it gets a 64-bit process, 32-bit plugin gets bridged.

panten · Post by **panten** » Wed Mar 26, 2014 8:32 pm

So we are limited to 4 Gigs for the rest of the program? that includes all the buffered samples in audio tracks and memory taken up by devices..?

ZenPunkHippy · Post by **ZenPunkHippy** » Wed Mar 26, 2014 8:40 pm

panten wrote:So we are limited to 4 Gigs for the rest of the program? that includes all the buffered samples in audio tracks and memory taken up by devices..?

Probably not a problem if they've used a separate memory server for RAM allocation (like some versions of Kontakt running on 32-bit OSs).

Basically, they know that > 4 GB is important and they have not created a host with that kind of limitation.

Nothing to worry about.

Ameyah Audio · Post by **Ameyah Audio** » Wed Mar 26, 2014 9:19 pm

all comes down to what arch the java is using, bitwig core is based on Java virtual machine.

and the bitwig.exe you see is only there as loader for the JVM. the concept is kind of similar to the FL concept.
so i dont think its a problem, because every process has its own 4GB to work with.
so i agree with ZenPunkHippy.

HamHat · Post by **HamHat** » Thu Mar 27, 2014 3:41 am

panten wrote:So we are limited to 4 Gigs for the rest of the program? that includes all the buffered samples in audio tracks and memory taken up by devices..?

That's how its sounding to me. routing, buffering, bitwig tools, nested devices, etc. can only use 4 gb ram. Nice.... and no thanks.

contrast · Post by **contrast** » Thu Mar 27, 2014 3:53 am

You are making up a problem where there is not one. The GUI part is a 32 bit process. The parts that handle all the stuff that could possibly run out of memory are 64 bit processes as long as you have a 64 bit OS.

If you can't conceive of how it might still use all your RAM, that's ok; just don't worry about it; it will use it.

panten · Post by **panten** » Thu Mar 27, 2014 9:03 am

Thanks for the replies. Guess it's hard to put the demo through proper stress tests without being abLe to save, but this is good info guys, cheers.

HamHat · Post by **HamHat** » Thu Mar 27, 2014 10:17 am

contrast wrote:You are making up a problem where there is not one. The GUI part is a 32 bit process. The parts that handle all the stuff that could possibly run out of memory are 64 bit processes as long as you have a 64 bit OS.

If you can't conceive of how it might still use all your RAM, that's ok; just don't worry about it; it will use it.

How do you figure? 30 tracks deep with full audio and midi, a few x32 and bitwig tools. seems like you might need the extra ram.

ZenPunkHippy · Post by **ZenPunkHippy** » Thu Mar 27, 2014 10:21 am

HamHat wrote:How do you figure? 30 tracks deep with full audio and midi, a few x32 and bitwig tools. seems like you might need the extra ram.

Until you've actually run out of RAM there is no problem ... and I suspect that if you test a huge project like suggested here, you will not run out of RAM.

Bitwig is not coded the same way as older hosts such as 32-bit Live + Cubase ...

Peace,
Andy.

ThomasHelzle · Post by **ThomasHelzle** » Thu Mar 27, 2014 12:01 pm

EvilDragon wrote:Again... GUI is hosted in a 32-bit process, but all plugins are hosted in their own processess, so if it's a 64-bit plugin, it gets a 64-bit process, 32-bit plugin gets bridged.

It's a bit more involved (and forward looking) than that:

There is one 32 Bit process - the GUI.
4GB should be plenty for that

Depending on what system you are running, this loads a 32 Bit or a 64 Bit engine that does the hard work (audio and midi processing etc.) and can use all the memory that the system has (I have 32 GB too

).
You can see it in the file system. There is an "engine-x86" in the bin folder and an "engine-x64" in the x64 subfolder.

And finally you have the plugin hosts that are available in both 32 and 64 Bit, depending on your settings in preferences either one of each for all plugins together or one for each plugin, with as much fine control as you want.
So you could run all your (stable) small plugins with little ram needs in one process and for instance Kontakt in another, so it has full 4 GB even if it's 32 Bit (in a 64 Bit system of course).

Full sandboxing is at work if you activate "Independent processing for each plugin", only then each plugin can crash independently and be resurrected at will without dragging down the others.
I personally have this activated.

So this boils down to the user not having to bother about x86 or x64 at all.
I personally love it.

I hope this helps,

Cheers,

Tom

fedexnman · Post by **fedexnman** » Fri Mar 28, 2014 2:12 am

Call me Stupid ! But do I install BWS to c: program files x86 using windows 7 64 ?

contrast · Post by **contrast** » Fri Mar 28, 2014 2:24 am

Yes, Program Files x86 is what it defaults to and is correct.

HamHat · Post by **HamHat** » Sat Mar 29, 2014 3:24 am

I would like to see an official Bitwig reply or at least read it in their faqs as to why one doesn't need x64 software.

Ogopogo · Post by **Ogopogo** » Sat Mar 29, 2014 3:30 am

HamHat wrote:I would like to see an official Bitwig reply or at least read it in their faqs as to why one doesn't need x64 software.

What these guys are trying to tell you is that Bitwig is 64 bit. When the audio engine boots up it detects if you are running 32 or 64 and loads which one is appropriate. If you are on a 64 bit system it is loading the 64 bit version automatically. Make sense? They never said you didn't need 64 bit. You are not limited to 4 gigs of ram.

Bitwig

KVR Audio

Bitwig x64?