Standard all

[calaf5]

(I know this may not be the right forum for this but my post hasn't gotten any feedback in other places so...)

When I first bought Opus 1 I asked for a good set up and someone from the company said to load a "standard all" and a "legato" program for each instrument of the orchestra.

I would love to do that because then I would have a working set-up I could save and use for most projects...but the problem is that the "standard all" only include the forte samples. So its pretty useless for a running set-up.

My question is what is a good set-up that I can save and use over and over again? I hear these great classical mock-ups like "Jupiter" and it seems like every sample imaginable was used. How does one do that if there is a limit on how much you can have loaded at one time?

I use Sonar + Halion and with Halion I can never seem to get over 1 GB of samples loaded. Is that normal?

I would love to have at the very least the following loaded for each instrument:

stac
sus
leg p
leg f
and a percussion sect.

Is there a way?

calaf

[Peter Brown]

Hi Calaf,

I think for a mockup of a work such as Jupiter, it's not always important to hear everything at once - after all, the work is standard repertoire, and you know how it goes.

here's one way:
after you have all the notes in the sequencer (without audio, or with cheap quicktime/creative GM playback as reference), you can adjust the tempo mapping to get an organic feel (conduct it with only a click track to get an idea - the music should be in your head by this point).

then load in, for one instrument at a time, all the patches you need to get a realistic enough sound. bounce it to audio and save your .fxb for that instrument so you can use it at a later date.
do this for all your instrument tracks, until you have built up the entire score as audio stems.
mix (with similar reference audio)
sleep
master
sleep again
do a final listen
upload.


Get used to the 'bread-and-butter' patches such as _sus+RS and perf_leg/rep etc and add to your experiments (in between projects!) the other dynamics and variations of note-lengths.

soon you'll have .fxbs saved with a Gig of samples just for violins - which is great. and you can break a line of Jupiter up into dozens of MIDI tracks for the different patches to handle. doubtless to say that my Cubase files are full of folder tracks, mostly with more folders inside! hopefully Sonar can handle that...

granted, I'd love to load in the entire orchestra to try different patches at a whim - but it's not feasible yet. I think there's an issue with 'more than 1Gb' in HAL3 - check the cubase.net forum - I'm sure I've seen something...

apologies for the long post - I'm not advocating this as the only way to work, but for a known classic, I think it makes logical sense...

best
Peter

[calaf5]

This is a brilliant idea! I've been asking this question for a long time now with no solutions. Thank you so much for your input.

For classical mock-ups this will be perfect, but I don't know if it will work as nicely for writing my own stuff. Having a huge pallet of realistic sounds at your finger tips really helps a lot in the improvisation of a new piece. I think instead of GM I might use a select few of the VSL patches and then use your tips and tricks to go from there!

Thanks again Peter...I've found using VSL is an on going learning process and that you can keep learning more and more new things. [:D]