One thing I do to speed up the expression map process is having a default file saved with about twenty or so empty articulations with their key switches already mapped. By and large all that remains for that first stage is naming. It's a small thing, but it makes it a little less tedious.
Man, HUGE thanks for this. I was really struggling trying to understand how groups worked in expression maps and how you'd set that up. This video got me to see the light. I always turn to your channel first when needing very well explained and comprehensive information. Thank you so much. You do not disappoint, sir!
Great Stuff! I haven't thought about vibrato myself, so I will add that. One thing to consider is using program change instead of keyswitches. You must obviously have a controller that can do this (some keyboards can). But using a tablet/ipad with OSC (free) or similar (touchDAW is cheap for example) works well. The reason I bring this up is because you won't be locked to an articulation by default, as is the case with attributute. Meaning, cubase will always select the first articulation in the list when you play on your keyboard. This can be annoying when you want to play shorts and you get legato, for example. Program change doesn't do this. I otherwise do a hybrid. Meaning, I have articulation maps, but ALSO the articulations divided to midi channels with ONE instrument track. All the midi tracks control ONE instrument track. This way, I get ONE output in terms of channel and mics, but I can still either jump with switches, OR midi channels. This way I can set up latency to be different on each articulation. Shorts usually trigger much faster than legato for example. Lastly, save your instruments as Track presets, so that you can recall the exact settings in ANY project, and not just a template
Alex, this has been a very helpful video. I just got a couple new VSL libraries and the expression maps are not programmed correctly and I have to reprogram them. Your video has helped me understand how expression maps can work in the advanced needs that I have so I can get the most out of my incredible libraries without having to start from scratch. Thank you, sir.
Using Cinematic Studio Series instruments, the user interface has 2 choices either by using the basic keyswitches or using the CC58 which is very similar to this expression map=)
Magisterial. You lost me a bit, however, when you started talking about making a default legato -- I even slowed down the playback speed and watched it a few times but still got a bit lost in there (I assume "ord" means "ordinary" which is synonomous with "normal" so I'm unclear why the redundant jargon Cubase employs here). Thank you very much :)
I used the word default legato because the OT instrument has multiple types of legato (ordinary/normal, and also fast/runs). I want the expression map to default to ordinary if I simply select 'legato' in my articulation window, because the ordinary legato will be used far more often than a runs/fast legato patch.
Thanks for this video, Alex. You do not explain the 'Groups' you created. Why are there 4 'Groups' of articulations and how does that help? And did you end up having only 'Direction' entries or some entries with 'Attribute'?
Using groups can make the expression map more efficient if you have dozens of articulations, as is the case in a lot of OT libraries or VSL libraries. For instance, if every sustain patch can also be a legato patch, and also has the option of either vibrato or non-vibrato, then I can establish groups that trigger 'legato on', or 'con vibrato'. This is only necessary because there are so many potential sound variations. I'm essentially copying VSL's articulation tree structure from their Synchron libraries if you're familiar. Ultimately it's saves a lot of space in the articulation lane in Cubase. You might instead use a CC number for things like vibrato or trill interval size.
the most complete and clear video on this topic on UA-cam
One thing I do to speed up the expression map process is having a default file saved with about twenty or so empty articulations with their key switches already mapped. By and large all that remains for that first stage is naming. It's a small thing, but it makes it a little less tedious.
Thanks! Very useful!
Man, HUGE thanks for this. I was really struggling trying to understand how groups worked in expression maps and how you'd set that up. This video got me to see the light. I always turn to your channel first when needing very well explained and comprehensive information. Thank you so much. You do not disappoint, sir!
Great Stuff! I haven't thought about vibrato myself, so I will add that.
One thing to consider is using program change instead of keyswitches. You must obviously have a controller that can do this (some keyboards can). But using a tablet/ipad with OSC (free) or similar (touchDAW is cheap for example) works well. The reason I bring this up is because you won't be locked to an articulation by default, as is the case with attributute. Meaning, cubase will always select the first articulation in the list when you play on your keyboard. This can be annoying when you want to play shorts and you get legato, for example. Program change doesn't do this.
I otherwise do a hybrid. Meaning, I have articulation maps, but ALSO the articulations divided to midi channels with ONE instrument track. All the midi tracks control ONE instrument track. This way, I get ONE output in terms of channel and mics, but I can still either jump with switches, OR midi channels. This way I can set up latency to be different on each articulation. Shorts usually trigger much faster than legato for example.
Lastly, save your instruments as Track presets, so that you can recall the exact settings in ANY project, and not just a template
Thanks, great tips all around! I'll definitely start saving track presets from now on.
Alex, this has been a very helpful video. I just got a couple new VSL libraries and the expression maps are not programmed correctly and I have to reprogram them. Your video has helped me understand how expression maps can work in the advanced needs that I have so I can get the most out of my incredible libraries without having to start from scratch. Thank you, sir.
Very good video on a subject that is not widely covered. Thank you.
FYI: Expression Maps are now also available as of Cubase Artist 13.
They were introduced in Cubase (Studio) 5.0.1 in 2009 aka Cubase Pro thereafter.
great instructions, thx!!!
Thanks that's very helpful.
I'm a Cubase user, but boy does Studio One make this process worlds easier. Really wish Steinberg would change to something similiar.
Using Cinematic Studio Series instruments, the user interface has 2 choices either by using the basic keyswitches or using the CC58 which is very similar to this expression map=)
I think the CC58 method is used in this video ua-cam.com/video/kbt6Uyul0xE/v-deo.html which explains articulation mapping in Logic.
Magisterial. You lost me a bit, however, when you started talking about making a default legato -- I even slowed down the playback speed and watched it a few times but still got a bit lost in there (I assume "ord" means "ordinary" which is synonomous with "normal" so I'm unclear why the redundant jargon Cubase employs here). Thank you very much :)
I used the word default legato because the OT instrument has multiple types of legato (ordinary/normal, and also fast/runs). I want the expression map to default to ordinary if I simply select 'legato' in my articulation window, because the ordinary legato will be used far more often than a runs/fast legato patch.
Is there a way to purchase these already set up?
Unfortunately I'm not selling these... yet. But you should check out Babylon Waves, they offer a ton of expression maps!
Thanks for this video, Alex. You do not explain the 'Groups' you created. Why are there 4 'Groups' of articulations and how does that help? And did you end up having only 'Direction' entries or some entries with 'Attribute'?
Using groups can make the expression map more efficient if you have dozens of articulations, as is the case in a lot of OT libraries or VSL libraries. For instance, if every sustain patch can also be a legato patch, and also has the option of either vibrato or non-vibrato, then I can establish groups that trigger 'legato on', or 'con vibrato'. This is only necessary because there are so many potential sound variations. I'm essentially copying VSL's articulation tree structure from their Synchron libraries if you're familiar. Ultimately it's saves a lot of space in the articulation lane in Cubase. You might instead use a CC number for things like vibrato or trill interval size.
Mahalo, Alex! I will experiment with this.
is this only for Pro version or all versions?
Pro only, according to the online manual
meanwhile also in Cubase Artist 13
👏🏻👏🏻👏🏻
These are articulations, not expressions FYI