64bit Windows XP Pro, if your hardware supports it, Cubase can
theoretically load the full 4GB, which for example, for me, means
about 3GB, before it most likely become
I mention 64 Windows XP Pro is free to try for 120days? It's
2.4GB to 3GB is still not a big difference; definitively not
something worth changing your OS. Although maybe you'll get better
results yourself. Check it out!
what I'm going to show you was first inspired by forumers posts at
SoundsOnline-Forums.com, especially LEX's, who mentioned this
technique once or twice.
going to show you how to exceed that damn 3GB barrier, and be able to
load more samples into your favorite template.
PREPAIRING YOUR OS
of all, let's install Windows XP x64 on a different partition to your
main system. Installer will automatically create a boot-menu, so
you'll be able to pick the system you want to run. Install proper
64-bit drivers and your favorite software. Don't forget to install
the latest updates… most of the time, they don't do much hurt
not saying you cannot do this on Vista 64 bit. I'm simply, not sure
whether all this stuff will work with Vista or not :) If you already
have it up and running, feel free to try!
Teleport is a very cool small application. A DAW networking software,
designed to allow you to use multiple slave PC's under command of a
main host machine. Basically, what you can do with it is open a VSTi
(such as PLAY or Kontakt) on a slave machine remotely from your host
machine, and use it as if it was there in your sequencer. All the
MIDI and audio routing is done via LAN cable.
if you already knew that, you probably didn't know that you can
actually install both FX Teleport Host AND
Slave on your main machine and use it as if your PC was both Host and
download a 14-day trial from FX Teleport website:
let's install FX Teleport Host. Run the installer and pick „Master
now, on the same machine (could even be the same folder), run the
same installer again and pick „Slave (Server) installation”.
will probably run instantly after they are installed, if they don't
please run "Start Server" and "Install Effects"
from your FX Teleport folder (or Start Menu).
Effects" application is a simple program, installing our VST
Instruments as wrappers, so they are visible for FX Teleport Server
and can be used "remotely".
add our VST Plugins path, and let the application rescan it. After
it's done, let's click on "Install" and wait for results.
Now, our VST Plugins are ready to run with FXT Server.
IN CUBASE 4
you can see in your VST Instruments window of Cubase, Install Effects
has created a directory in our VST Plugin list, named "FX
Teleport". Inside, you can find all of your VSTi's. What now?
make sure you are running FX Teleport Server. If not, run "Start
Server" from your ‘FX Teleport’ folder. Now, click
to open one of FX Teleport-ed instruments, as if they were normal
plugins. Let's say, we pick Kontakt 3, and load couple of patches
from EWQLSO Platinum Pro.
first run, "remote" plugins will check and set a proper
latency for FXT, but don't worry about that too much, just click OK
and let it do its job ;) Now, as you can see on Windows Task Manager,
it's "Server" application loaded the samples, not Cubase 4
itself. It works! :)
let's open Kontakt 3 and load more samples, but this time locally -
in Cubase, not remotely in FXT Server. As you can see, Cubase 4 is
now using its own memory, and FXT Server its own. This way we are now
virtually able to load double the amount of samples we could load
with Cubase only. What’s very cool in FXT is that your project
saves with both - local and remote plugins, so you don't really have
to worry about anything - it simply saves and opens without any
more, very cool thing with FXT is that it’s multi-output
capable. So - you want some instruments in Kontakt 3 to be routed to
different audio channels? No problem, use it just as if it was
locally in Cubase, assign channels, activate outputs in the VST
Instruments window, and voila!
A COUPLE OF THINGS TO
good to know a few things, before you start setting up a large
template using this method.
never actually exceeded 6GB of samples without running into
instability issues, so after all, this may not be an ultimate
solution for some of you. My current orchestral template I used to
score a short 3D movie is over 5.1GB (Cubase and Server RAM in total)
and has 57 articulations in four Kontakt 3's (2 localy, 2 remotely)
and one Kompakt for choirs, with a couple of exceptions - all patches
have 3 mic positions, routed as described in my first tutorial. My
soundcard latency is set to 8ms, FXT plays with an additional 8ms,
but the effect is very nice, especially if you put Brass and
Percussion on FXT, and Strings and Woodwinds locally.
you make FXT route back to Cubase with too many audio channels, you
can run into additional latency or latency-inconsistency issues. FXT
will try to fix latency to compensate for large audio return. In my
template, FXT routes back 6 separate 24-bit audio channels without
aware, that this might not actually be the ultimate solution. Only
64bit sequencing is. I can't make use of the full 8GBs (maybe someone
else will get better results). If it was possible to run and operate
with two or more FXT Servers on one machine, the problem would be
solved, but as far as I know, it isn’t possible. However, if
anyone succeeds, then he's more than welcome, to give me (and others)
a hint :)
Download a PDF version: