Bidule rewire's memory use not separate from PTHD?

[kirkgale]

I blindly assumed one of the reasons for running VI's via VST out of Bidule Rewire instead of directly via RTAS was to avoid the 4 giga RAM ceiling for PTHD users.


But with this 12 giga RAM system (Win 7x64 - sorry guys, no one on the windows side is seems to know), all sorts of anomolies (e.g., VI interface graphics not opening and crackly audio from Bidule into PT) appear when the system reports a total 3.9x gig of RAM in use (including windows itself).


Tell me its not true in your Mac Pros and I'll switch (back) in a second...

[IO Composer]

The only way I've found around the 4Gb ram limit is using Kontakt 3.5 in Bidule with the Memory Server option selected. I've got 12Gb of samples loaded. But.. I'm on a Mac. Have no idea how things are working on the Win7 side of things. Though, Bidule is 64bit on Win7 so it SHOULD be using 64bit memory. You might try posting your question on the Bidule forum.

http://www.plogue.com/phpBB3/viewforum.php?f=4

[kirkgale]

Thanks for the heads up IO...

although the system was brought to its knees by pushing ram use up close to 4 GB (w VI's running only in Bidule not directly in PT), now I'm also pushing the more stable VI's directly in PT (in the same session) and total ram use is reported as 4.8 GB...so the ceiling was apparently made of glass...


audio is crackly on the YellowTools VI's out of Bidule tho...I'll dig around on other forums as you suggested.


thanks again,