Dude, just run it in a 64-bit OS and load an ton of samplers, way more than 4gb, and see what happens. There's nothing to explain other than maybe why you just haven't done that yet.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.
Bitwig x64?
-
- KVRAF
- 6159 posts since 4 Dec, 2004
-
- KVRer
- 6 posts since 28 Jul, 2015
This is a bad idea.
it use more RAM .
in other daws when u have a kontakt and a librabry , when u use it on another track it wont use more ram for samples.and it load samples fast cuz already it loaded.
but in bitwig for every kontakt it loads their samples and duplicate them in the Ram and use too much ram.
it use more RAM .
in other daws when u have a kontakt and a librabry , when u use it on another track it wont use more ram for samples.and it load samples fast cuz already it loaded.
but in bitwig for every kontakt it loads their samples and duplicate them in the Ram and use too much ram.
- KVRAF
- 6540 posts since 9 Dec, 2008 from Berlin
As for the 64 bit Topic:
http://www.kvraudio.com/forum/viewtopic ... 9&t=450443
As for Kontakt: you can route the midi from several tracks to one instance of Kontakt so it will be just as efficient as in other DAWs.
In case you missed it: This thread you resurrected is 2 years old and mostly contains wrong impressions about the 64 bit topic.
Cheers,
Tom
http://www.kvraudio.com/forum/viewtopic ... 9&t=450443
As for Kontakt: you can route the midi from several tracks to one instance of Kontakt so it will be just as efficient as in other DAWs.
In case you missed it: This thread you resurrected is 2 years old and mostly contains wrong impressions about the 64 bit topic.
Cheers,
Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube
UrbanFlow.art · Instagram · YouTube
