Kontakt memory for orchestral slave

[dru0013]

I'm new to Bidule and am trying to use it for a big orchestral slave on a PC (Win 7 64 bit Pro), which is also new for me, as a long-time Mac user.

When I start loading Kontakt 4 instruments into Bidule, I quickly run out of memory. On the Mac you can use Kontakt's Memory Manager, but it doesn't seem to exist in the PC version. I have 12 GB of RAM in the PC - can I access all of this from one instance of Bidule, or do I have to run several instances (is that even possible?)? I think I'm running out of memory at about 3 - 4GB.

Can anyone help?

[xsys]

I am relatively new to Bidule as well, but I believe it is 32 bit only.

JR

[dru0013]

Ah, thanks. I guess that means a single instance would only use 4GB max? So could I run at least one more instance and send the audio out through the same device?

I guess I may need to add PCs in order to get the whole library running, which I was hoping to avoid.

[seb@plogue]

There is a 64 bit version of Bidule on Windows that will work with Kontakt, if you have a 64-bit version of Kontakt. Otherwise in 32-bit land on Windows the actual limit is either 2 or 3 GB depending on the setup.

[dru0013]

Thanks Seb,

My version says x86-32, so I must have the 32 bit version. I'll also check Kontakt. So, if I install the correct versions (duh!) should I be able to use all available RAM? That would be awesome!

[scope4live]

I played with a DAW Slave that was running Windows 7 32bit and it loaded much more than XP 32bit using the 3 GB PAE Switch.
I will be switching over to WIndows 7 on my vacation since I never trust new updates or apps for live work.
But Kontakt 4.0 using NCW developed libraries and instruments in Windows 7 32bit seems like a safe bridge before going 64bit.
What's nice to know is when I do decide to try 64bit, Kontakt and Bidule will be somewhat matured by then.