![]() I don’t know if Bill had W7 32 or 64 bit but you may want to ask him that. ![]() 32 on 64 with J-bridge will allot 2G of RAM per instance of VSTs and plugs up to your OS limitation or how much physical RAM installed, whichever comes first. That’s when the Cubase bit bridge comes in or in the alternate case, J-bridge. The problem usually starts to occur when using a 64 bit Cubase version and 32 bit VSTs and/or plugs. Whether it’s a 32 or 64 bit system shouldn’t matter as the 64 bit system addresses Cubase 32 bit with no problem. If VST 5/32 only wants to work well on a 32 bit OS - and maybe/hopefully that’s not entirely true - one may as well use a 32 bit OS computer for that Cubase version.įrom what I can see, you were in a conversation with Wild Bill who at the time was running his VST 5 version with W7 Premium. If not, than there’s no benefit to going 64 bit…not with a dedicated music machine anyway…dual duty & general purpose maybe, like a gaming/music machine. One I ‘thought’ I read that newer versions of Cubase has some ability built in?The other is something called ‘J-bridge’? Thing is, an older Cubase version like VST 5/32 … how well does it jive on a 64 bit system, that’s beyond my own experience.Īnother thing I was never quite clear on was, if using 32 bit Cubase & 32 bit VSTi’s on a Win 64 bit platform, whether the benefit of having more ram installed on a 64 bit system, is cut back down to being only able to access 4 GB while using 32 bit programs. I’m unclear about this but I believe there are two ways to do this. I have read some people here using 32 bit software (Cubase & VSTi’s), on a Win 64 bit system. While I was part of that discussion, I have never used VST 5/32 on a Win 64 bit system, only 32 bit Win XP myself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |