Combining VST Expression and VSL Flexibility

[Plougot]

Hi everyone !

I found a way to combine VST Expression and the flexibility of VIPro in Cubase 5.5. It's a bit tricky, and it would take a while to explain, so i ask first : Is anyone interested ? ^^

To make it quick : I read a post about two weeks ago of someone (don't remember the name, sorry) explaining that he had 2 tracks for each instruments, one with and one without vst expression. Even though it's a nice idea, I found it too messy. So I tried several things, and finally, i managed to use VST Expression in a different way, like a KeySwitches system apart from the midi notes.

One of the main drawback is that I have 2 tracks of KS informations for one instrument track, but it's really organized, and much more flexible (i can easily create new matrices in vipro, and choose precisely patches in any matrix.)

In a word : it's like using keyswitches, without using (directly) keyswitches. in order to be at the same time organized and flexible.

[Dominique]

Hi there

Sounds interesting. Would you mind explaining it? I'd sure like to know

[Plougot]

Hi Dominique.

First, let's explain why I bothered making a slightly complex system with 3 tracks per instruments. We all know the main issue of VST Expression : once it is put on a track, nothing else that notes can be send manually (I think in cubase 6 you can send 1 CC, but it's not enough). And creating a VST Expression map is such a pain... that we all end up using vsl presets only. 

One solution is to create two instrument tracks, one with VST Expression (the main one) and one without (for custom stuffs). But it can quickly become messy.

My idea is to use this really good method a bit differently : my main instrument track (where i put my midi notes) stays free from VST Expression (I don't know if this sentence is correct, but anyway... :p), while my other tracks, which do not contain any notes, have special maps i did, allowing me to choose patches just like keyswitches.

I know, you're going to tell me "well, if you had to design your own vst expression maps... No thanks"

Yes and No. Yes, I had to create my own expression maps, but they're way easiest to create and understand than normal maps. Because I don't use them the same way.

Currently, I have 2 KeySwitches track. One is called "matrices", and the other "Cells". So the first one allow me to choose my matrix, and the second one, to navigate in the matrix i chose. I Think screenshots would be much more precise than myself, so i'll post some as soon as I can.

So, my system has several advantages :

-midi notes and KS are not mixed.

-You can send CCs, and Keyswitches on the keyboard still work (can be handy when you're not recording)

-More flexible than normal VST Expression. (adding a new matrix can be done without touching the VST map if it's correctly prepared)

-Less messy than KS. You always see what's going on, and it's not possible to have useless informations all around.

-Setting up is easier than with normal vst expression. And can easily be shared.

But it also has drawbacks :

-3 Tracks for one instrument

-Slightly Tricky way to edit (and one very silly cubase bug to avoid)

-not as handy as normal VST Expression maps : you still have to know how your matrices are organized

-Notes and KS being separated, copying and pasting is sometimes easier, sometimes trickier, depending on how you organized your whole library. basically, if your keyswitches mapping is identical, normal keyswitches would be faster (copying and pasting everything at the same time), and if they're not, my system will automatically map them.

-Even though setting up is easy, it has to be done.

[TFIS]

 I've built my own expression maps, based on modified preset matrices.

I changed the H-span to starting at C~ and V-span to CC74.

Modwheel controls the volume (i makes  no sense to control the volume with velocity, which makes cresc./decresc. very difficult).

CC72 controls the cell X-Fade (only used when blending from sustain to tremolo).

The vst expressions (i've made 3: strings, brass, wood) are all set to directional mode, so i see immediately which cell is active and can delete the expressions without deleting the notes (which happens, when the expression is set to articulation),

There are som glitches

There is a release bug in some string sounds, when selecting the crosfade cell sustain/tremolo, the sustain sound stops sometimes. But this happens without vst-expression, too. So there are 2 sustain expressions: sustain (normally used) and sus/trem xf (only used if i want to fade to tremolo).

I didn't try it, but i think my expression maps won't be very useful, when scoring.

If someone is interested i can upload them somewhere.

[Plougot]

 There is an easy way to delete only articulations : just left click on it with the pen tool (or alt-left click on it with the selection tool, pressing alt changes the selection tool into the pen tool). I know, this is a bit weird, like the whole VST expression system actually ^^.

By the way, i made several modifications to my idea to make it much more handy (I had misunderstood the way vst expression was working in a certain way). Now, I just have two tracks per instruments, and I think this "Keyswitches enhanced system" is really better than Normal Keyswitches. The main idea is still the same : you choose your matrix on one track, and then you choose your cells on the other track (your "notes track", now). What's really convenient is that I chose "articulation" for selecting cells, and direction for the matrix. So my X, Y and A/B controls stick automatically to the notes, while the matrix is defined globally.

The only last thing which is a bit annoying is to prepare your presets so that they have good X, Y and A/B Ks or controllers. Does anyone know what are the highest notes and the lowest note VSL instruments reach ? As for me, I didn't see anything below C0 (bosendorfer) or above C#8 (piccolo), but I don't have the whole VSL library. I ask this because setting everything up in one go would be really nice ^^. Then you would only have to map correctly your own preset, and everything would be ready to go.

[Dominique]

Hey Plougot and FTIS

Thanks for the input. I'll try when I find the time.It would be great if you could upload some screenshots or even presets, but I'll try to reproduce from your posts, so no need to hurry

[Plougot]

 Hi !

I've taken some screenshots of my two expression maps, and created 2 "example" maps.

http://dl.dropbox.com/u/4695665/Smart%20mapping/Smart%20Map%20-%20Matrices.JPG

http://dl.dropbox.com/u/4695665/Smart%20mapping/Smart%20Map%20-%20Cells.JPG

So, what you have to do is simple : create two tracks pointing on the same instrument. Apply to each one one of the two "smart map" (matrices on one, Cells on the other). Then, set your Vi pro like this :

X Keyswitch : C-1

Y KS : G8

A/B : CC79

And in the option panel, under Master Settings, choose Matrix CC : 127. I tried to choose my matrices with program changes, but it didn't work, so I used this other CC option.

http://dl.dropbox.com/u/4695665/Smart%20mapping/Vienna%20smart%20map%20conf.png

And here's a zip file containing the two example maps : http://dl.dropbox.com/u/4695665/Smart%20mapping/Smart%20mapping.zip

One question you could ask me. Why 2 tracks ? After all, this idea could work with one. Yes... But I have to make a HUGE map, combining matrices and cells, and once it is done, things become rigid. (adding a new matrix under cubase is not possible anymore, unless spending hours.). But i'm currently working on it, I may have an idea.

So, Basically, follow these steps, and you'll be able to control 5 matrices of 3*3 cells with the expression controls.

Let's finish with some editing tips. Create an empty container for you matrices track. When you want to edit articluations, select both container at the same time. This way, you'll be able to see your notes even while choosing your matrices (you can choose the container you are editing with a list, without having to close the midi editor). Don't forget to always choose your "notes track" before adding notes.

tell me what you think about it ! As for me, I find it pretty cool, because of my poor memory and organization, I kept forgetting Keyswitches everywhere in my midi container, resulting in poor articulation choices. Moreover, the "articulation" type for the cells makes the X,Y and A/B selection sticky, which is not the case with normal KS.