If I buy Vienna Ensemble 3 how will I be able to access more then 4GB of RAM?Confused

[adg21]

I am on Window 7 64 running Cubase 32. If I buy Vienna Ensemble will I be able to access additional RAM (up to 24GB) by loading Vinna Ensemble as VST's in Cubase 32 (accessing 4GB of ram for each instance I load)? Or do I have to run as Rewire or in a 64 bit host DAW? I'm confused, as I know you have to run Kontakt (32 OR 64) outside of Cubase 32 to access extra more than 4GB ram (via Bidule) - or am I wrong about that too?

I know that mac users can use enable Kontakt's memory server - this is not an option on PCs - so I'm looking for an alternative.

What is the most sensible way of getting instances of Kontakt to access more than 4GB of Ram in Cubase 32 on a Windows 7 64 bit system other than using the 64 bit version of Cubase?

Pulling my hair out

Thanks

[Krzysztof]

Hello
I assume you have looked here:

Vienna Symphonic Library

The part that you want to look at is the server option that VE Pro offers. You run an external (external to Cubase) instance of VE Pro on your windows machine and load up a instance of VE Pro in Cubase.....then you link them up. Works very well over here in macland see no reason it won't work for you in windowsland. Download the demo (above link) and try it out.

Regards

Krzysztof

[DAW PLUS]

What issues do you have with Cubase 64 bit?

[joris de man]

Originally Posted by adg21

I am on Window 7 64 running Cubase 32. If I buy Vienna Ensemble will I be able to access additional RAM (up to 24GB) by loading Vinna Ensemble as VST's in Cubase 32 (accessing 4GB of ram for each instance I load)? Or do I have to run as Rewire or in a 64 bit host DAW? I'm confused, as I know you have to run Kontakt (32 OR 64) outside of Cubase 32 to access extra more than 4GB ram (via Bidule) - or am I wrong about that too?

I know that mac users can use enable Kontakt's memory server - this is not an option on PCs - so I'm looking for an alternative.

What is the most sensible way of getting instances of Kontakt to access more than 4GB of Ram in Cubase 32 on a Windows 7 64 bit system other than using the 64 bit version of Cubase?

Pulling my hair out

Thanks

VE Pro rocks, and I can't recommend it highly enough.
I work in a similar fashion on similar specs (dual quad xeon, 24gb of mem, W7 64 and Nuendo 5 32 bit version), and it works as follows:
-Install 64 bit versions of your sampler/rompler plug-ins (Kontakt, Omnisphere etc.)
-Install Ve Pro; this will install the Server (both 32 and 64 bit versions), and VST2/VST3 host plug-ins. You'll want to use the VST 3 version, as it can access multiple midi channels (not just 16 channels but 8x16 per plug-in instance).
-Start the 64 bit version of VE Pro; it will find your 64 bit VST's.
-Start your 32 bit Daw
-Instance the VE Pro Vst3 plug in your Daw. It will ask you to connect to a server; take note that servers can both be local or on a networked machine (gigabit ethernet recommend).
-A VE Pro server session will now be created, in which you can instance a 64 bit Kontakt plug-in and start loading instruments.

You can load multiple instances of Kontakt in VE Pro until you run out of midi channels for that instance, and just create another session which will open another Server Instance of Ve Pro.
For each VE Pro server Instance you would have also instance a VE Pro Vst3 instance in your vst rack to connect to it.

At the start, it will take a bit of setting up, as for each individual output pair of Kontakt you'll need to create a channel in Ve Pro to route it to the Ve Pro vst plug-in, so that it will appear in your Daw.
But there are a lot of pros for working this way:
-access to 64 bit plugs from your 32 bit daw
-Ve Pro sessions get saved with your daw session, meaning that it will automatically connect when you load your session and saved with it as well! (even over networked instances!)
-faster loading times (kontakt seems to load notably faster in Ve Pro)
-if for some reason Kontakt or any other 64 bit plug hangs, you can just quit VE Pro and restart it, it won't take your Daw with it
-You can preserve your Ve Pro setup between sessions..meaning that with the press of a button, VE PRo will keep its setup when you start or load a new session in Cubase; this can be a huge timesaver.
-Offline bounces, also over the network!

In my experience VE Pro's performance (both cpu wise and diskstreaming wise) is vastly superior to plogue.
I used to have issues with Plogue with heavy sessions; hanging notes, or sound dying, and having to manually manage the setups.
Don't know if that's to do with rewire, but VE Pro has none of those issues.

So, imho, well worth it, and if you managed Plogue, you should have no issues setting this up.
And to answer your question, yes, it does mean you can access 64 bit Kontakt from your 32 bit Cubase, and it works a treat.

Best,

Joe

[PaPi61]

I don't understand why people make their lives so complicated just to stick with 32 bit. If you intend to work with VEP, you're obviously running large libraries and your entire rig should be 64 bit. What's wrong with Cubase x64?

[oceantracks]

Originally Posted by PaPi61

I don't understand why people make their lives so complicated just to stick with 32 bit. If you intend to work with VEP, you're obviously running large libraries and your entire rig should be 64 bit. What's wrong with Cubase x64?

Not a thing, nor Logic...but many enjoy working in Pro Tools, which is not going to be 64 bit for a while...

TH

[joris de man]

Originally Posted by PaPi61

I don't understand why people make their lives so complicated just to stick with 32 bit. If you intend to work with VEP, you're obviously running large libraries and your entire rig should be 64 bit. What's wrong with Cubase x64?

No quicktime support, no full plug-in compatibility (waves being one of them), afaik no 64 bit eucon drivers, and the fact that bitbridging is still flakey (steinberg's bitbridge) or cumbersome (jbridge), whereas Ve Pro is a pretty solid solution that gives you the best of both worlds.

In general, 64 bit is mainly useful for large sample library use (and in some rare cases, really really long recording sessions), and this offers a solution that is in a way even better than running the 64 bit vsti's in your session, for the aforementioned reasons.

Obviously if all plugs, drivers etc. were running properly at 64 bit there would be no reason to stick to 32 bit, but unfortunately that is not yet the case...we're getting close though.

[Clint SwanK]

VE Pro looks amazing, but...I haven't worked with LANs as yet--how complicated are they to set up, and how important is having Gigabyte ethernet? One of the computers I'd be using has PCI-E fast Ethernet controller. Will that work?

[vfr]

Originally Posted by Clint SwanK

VE Pro looks amazing, but...I haven't worked with LANs as yet--how complicated are they to set up, and how important is having Gigabyte ethernet? One of the computers I'd be using has PCI-E fast Ethernet controller. Will that work?

Small LANs are pretty easy to setup, and there are lots of resources out there if you google them. I don't think gigabit ethernet is that important. It is unlikely you will saturate a 100 megabit connection with most scenarios. Gigabit ethernet with jumbo frames does speed up massive backups on high-end storage solutions; if that matters to you... All modern gear is gigabit though. In any case adding a gigabit NIC is inexpensive, if you wanted to go that route.

[EddieTheRed]

Originally Posted by joris de man

in some rare cases, really really long recording sessions

Pardon?