This is helpful....but how about the good old phrase “have listen to what happens when I enter....etc,” then play an example without talking over it? I thought there was too much talking without clearly audible examples of the actual part being used. It felt like a rather rushed explanation of expression maps...helpful, but not as helpful or clear as it could of been....
After years of using Cubase Pro I never knew about VX till today.. Pulldown Strings and Brass is great.. Thank you for a good tutorial.. It's a big thumbs up !!
I appreciate that you've called out the basics on this feature, but I think this conflating complexity with usability. I have made plenty of simple and complicated expression maps and it is in principle easy to understand, but the interface and user experience of editing them is the reason people don't use the feature it in my opinion. As examples: the window is frustratingly small and doesn't scale correctly, especially the output mapping; the difference between direction and attribute is not explained; the layering of different articulations in up to 4 articulations is not explained; there is no ability to copy and paste; there is no explanation that the first articulation slot in the map is the default and is reverted to; the slot does not rename automatically, unless it is empty; that the output mapping window sends the MIDI data out in an unexplained order. Also what do the colours even do? There doesn't seem to be any reflection of setting them in the expression map in any editor. The feature needs some love. It really needs to be using some inheritance and overrides rather than this method of defining the exact interaction of MIDI data for every combination. Additional requests would be to define the length addition in ms, rather than % (which is really odd), adding more symbols.
Yeah, it's the spreadsheet feel that makes people hesitate I guess. I kind of like Excel haha but most sane people don't... I guess the Expression Map Setup could benefit from an overhaul, after a thorough collection of feature requests from the user base.
I so much agree. Expression maps are great on paper. But if you really work with them extensively there are so many bugs, weird behaviours and missing features. Steinberg, please instead of changing the color scheme of Cubase for every version, look at improving the existing features.
For those without the expensive full Cubase version (the lower versions do not have expression mapping) it is still easy: In your key editor, paint in the articulation key as illustrated in the sample's key array. For example in this video's loaded sample the articulations are triggered using the keys A-1 to A0. Paint a quaver or other note value just before the point where you want the articulation and that expression will sound. You can create a SEPARATE track with the same channel just containing the articulation trigger notes.
That’s because it’s not a showcase of what articulations are and what they sound like. Different libraries come with different articulations and most sample libraries have walkthrough videos or audio demos to demonstrate. This is just about how to use expression maps. This is basicly info for people that already know what articulations are. So I highly recommend to explore different instruments articulations and sample libraries of those instruments that include (some or many of) those articulations. I used to just use the keyswitches by playing/drawing the midi notes that trigger them in the past but this way is very handy and imo a way better workflow. Basicly just a ‘better’ way to get you to your destination.
Can you add the ability to switch articulations and all these expressions depending on the color of notes, like in the BRSO Articulate? Instead of having to paint in this huge expression map window. That would be 10 times more convenient!
That's a horrible way of doing it, always have to note the expression maps on a piece of paper or open the kontakt instance to see which note does what. It's just that Cubase's implementation is horrible. Digital Performer introduced expression maps in the latest version and it's so much better and much easier to set up.
Thanks for this vid. I have looked into VST expressions a bit, and I find that unfortunately it doesn't save you that much time and hence I don't use it. It does help with scoring though, if you don't want the keyswitches in your score. (if you use the midi data for the scoring, that is). Otherwise the setup procedure, creating a map from scratch. and editing the midi track takes longer than just recording the keyswitches as you go. And a map mostly only works with one instrument anyway, because most patches instruments and patches are laid out differently, and even different maps has to be applied to different patches in the same instrument. Another more advanced problem is that most high end samples don't work well when triggered exactly on the dot (grid), but often need to be triggered a bit before the beat. This makes it a hassle when using maps since they work better if they are following the grid, especially if you have a lot of quick changes. At least I don't see it a more optimized way than just using keyswitches. I like the idea though, and have tried quit a bit to make it work. I am wondering how this could be applied in a better way so that it will help the workflow? My solution is to map the keyswithes to a controller so that they follow a similar pattern, so that the controller is always laid out the same way, making workflow faster. Perhaps editing each instrument so that their keyswitches follow the same pattern in the expressions could be a solution. In any case, you need some work to set it all up.
You can use the info line at the top and adjust the start position of the selected articulations by using the mouse wheel or type in a value in order to have the articulation events happen before the notes. Select all of them and do it all in one swell foop.
Yup! You can use the approach demonstrated here in this vid to map any key-switched instrument. Another really useful method is simply to load up any single patch instruments you have on to their own respective midi tracks and then hide them away in a folder (like a clarinet patch for legato, another one for staccato, etc) then make a 'master' clarinet midi track and create an expression map that will direct midi input to the appropriate patch on those hidden tracks. So you only see one Clarinet track, and can keep adding as many different patches to it as you want over time, hiding them away in a 'mapped' folder and updating your expression map to include the newly added articulations. This revolutionized my template - fyi Junkie XL has a fantastic video detailing how to do this - ua-cam.com/video/1gVWW2tKN8c/v-deo.html Biggest thing to keep in mind is you can be creative and make it work however you want it to.
Something this VIDEO DOES NOT POINT OUT is that there are already pre-built expression maps for most of the popular orchestral libraries out there. Sadly UVI WORKSTATION's ORCHESTRAL SUITE is not among those, but building your own doesn't take that long.
This is one of the many half baked features of Cubase. We are supposed to be able to create our own expression “maps” (this isn’t just for showing the articulations in the key editor and switching them in a convenient way…), but unfortunately this is still not working in 2022. In the Output Mapping section, we can set multiple articulation keyswitches for a single Slot, and sort them by velocity so that it plays a certain articulation between let’s say 0 to 20, another articulation between 21 to 50, etc. This is what the Data 2 column is for when the lane is set to Note On. And for some reason this doesn’t work at all, only the topmost output lane takes effect regardless of the velocity. And not to mention that the Expression Map window itself is badly made : super tiny add/remove buttons, text is cropped, value fields are buggy, and the output mapping cannot even be linked with the slots (create a lane with the same keyswitch automatically). I’m sorry but to me this is currently one of the most badly designed part of Cubase, if not the worst. I hope this will be greatly improved in Cubase 13.
Firstly, the voiceover is way way too loud compared to anything else, tone it down for Gods sake. Secondly, in my experience of using expression maps, it takes absolute ages to create them, and sometimes they fail to connect to the key switching first time, very annoying. Thirdly, if you are going to have working examples, then isolate the violin part, so that we can hear the expression changes on just THAT part, don't play the bloody counter melody too.
Great Vid . But it is true. The best video Tutorial I really like and I'm sure everybody else is feeling is the same. When they and I can hear what it does. This Teritory. Most people have never seen or know what it is. Let a lone know how it works or even what you could use it for and describe how to work it in the order you explain. It is getting to see how it should sound ounce you do this new way of Mapping out scenario's. Or Presets to make different rythem changes on how the rythem can be played, and mapped out to make it run in a order your describe it to do. We all would like to see a finished change and how it sounds . So we know if we are following your direction correctly. Also knowing the sounds that the two different styles will sound like. So we know what to look for in the sounds of the Presets your Changing and how the differences sound in full "before and After." So we can all tell the differences between the two or All of them. So we know what to look for and how it should sound Before and After your Adjustment. I really love how your doing vids on things that Nobody else knows of or is covering. You have a wide selection. Also you have shown me more than I could fathem I could do with Cubase. KEEP THEM COMING. THis is just to help you understand what we all would like you to show us. It all boils down to how we all were taught how to learn from somebody teaching us anything new. Some people . They learn better by pictures and Discription. Some people you can just tell them simply, and they will know by association. And some take more than 2 times to learn by branding it it after multiple play backs. It's just we all want to hear the reactions as well as the Directions. Not meant to Unapreciated. Just need more Clearity in hearing the reaction as well as the Direction. Thanks Cubase For the Great Vid Share on VST Expression Maps. And how to Use Them. Cheers Cubase!
We can't hear the things you are doing so we can see how valuable what you are doing is. I would have given you a thumbs down, but I will just thank you for the effort.
There is no way to sort expression maps ? What if you have a few hundred ? Can't even sort in alphabetic order, lol. Steinberg really disappoints, and they should learn from Presonus.
I appreciate these videos, but must say they are not really helpful. The reason is the explanation is so rushed and haphasered. So many crucial steps are skipped. I had to refer to random UA-cam videos to start working with this feature. Steinberg, you have great products but very poor tutorials. Please go through every step and show the functions in action.
This is helpful....but how about the good old phrase “have listen to what happens when I enter....etc,” then play an example without talking over it? I thought there was too much talking without clearly audible examples of the actual part being used. It felt like a rather rushed explanation of expression maps...helpful, but not as helpful or clear as it could of been....
After years of using Cubase Pro I never knew about VX till today.. Pulldown Strings and Brass is great.. Thank you for a good tutorial.. It's a big thumbs up !!
It'd be easier to hear what you're doing if you didn't talk all over the music or it was at least louder.
my thoughts exactly!
I appreciate that you've called out the basics on this feature, but I think this conflating complexity with usability. I have made plenty of simple and complicated expression maps and it is in principle easy to understand, but the interface and user experience of editing them is the reason people don't use the feature it in my opinion.
As examples: the window is frustratingly small and doesn't scale correctly, especially the output mapping; the difference between direction and attribute is not explained; the layering of different articulations in up to 4 articulations is not explained; there is no ability to copy and paste; there is no explanation that the first articulation slot in the map is the default and is reverted to; the slot does not rename automatically, unless it is empty; that the output mapping window sends the MIDI data out in an unexplained order. Also what do the colours even do? There doesn't seem to be any reflection of setting them in the expression map in any editor.
The feature needs some love. It really needs to be using some inheritance and overrides rather than this method of defining the exact interaction of MIDI data for every combination.
Additional requests would be to define the length addition in ms, rather than % (which is really odd), adding more symbols.
Yeah, it's the spreadsheet feel that makes people hesitate I guess. I kind of like Excel haha but most sane people don't...
I guess the Expression Map Setup could benefit from an overhaul, after a thorough collection of feature requests from the user base.
I so much agree. Expression maps are great on paper. But if you really work with them extensively there are so many bugs, weird behaviours and missing features. Steinberg, please instead of changing the color scheme of Cubase for every version, look at improving the existing features.
For those without the expensive full Cubase version (the lower versions do not have expression mapping) it is still easy: In your key editor, paint in the articulation key as illustrated in the sample's key array. For example in this video's loaded sample the articulations are triggered using the keys A-1 to A0. Paint a quaver or other note value just before the point where you want the articulation and that expression will sound. You can create a SEPARATE track with the same channel just containing the articulation trigger notes.
I was wondering why he didn't at least show that as an alternative way to do it cos it seems to be a quick and dirty way to get the job done. Thanks.
Talking too much,can't hear the example of expression in action
totally agree
That’s because it’s not a showcase of what articulations are and what they sound like. Different libraries come with different articulations and most sample libraries have walkthrough videos or audio demos to demonstrate. This is just about how to use expression maps. This is basicly info for people that already know what articulations are. So I highly recommend to explore different instruments articulations and sample libraries of those instruments that include (some or many of) those articulations. I used to just use the keyswitches by playing/drawing the midi notes that trigger them in the past but this way is very handy and imo a way better workflow. Basicly just a ‘better’ way to get you to your destination.
You just answered alot of questions i had regarding the use of expression maps in Halion sonic se,thanks heaps!!Keep these turtorials coming🙏
There is a way to do something similar with articulation when the instrument doesn't have keyswitch? By loading different articulation?
It’s possible. I found how to do it
very very helpful
Is it working with omnisphere ?
Feature only available in the Pro version of Cubase
Great video. Thank you!
Begin before the note?
Are you saying that "chase MIDI" functions won't work for key switching?
Do you have a problem letting us hear the music alone for a second?
Can you add the ability to switch articulations and all these expressions depending on the color of notes, like in the BRSO Articulate? Instead of having to paint in this huge expression map window. That would be 10 times more convenient!
Thanks.
I find drawing articulation notes in piano roll is even faster than spending insane amount of time building expression maps for each library.
That's a horrible way of doing it, always have to note the expression maps on a piece of paper or open the kontakt instance to see which note does what. It's just that Cubase's implementation is horrible. Digital Performer introduced expression maps in the latest version and it's so much better and much easier to set up.
Thanks for this vid. I have looked into VST expressions a bit, and I find that unfortunately it doesn't save you that much time and hence I don't use it. It does help with scoring though, if you don't want the keyswitches in your score. (if you use the midi data for the scoring, that is).
Otherwise the setup procedure, creating a map from scratch. and editing the midi track takes longer than just recording the keyswitches as you go. And a map mostly only works with one instrument anyway, because most patches instruments and patches are laid out differently, and even different maps has to be applied to different patches in the same instrument.
Another more advanced problem is that most high end samples don't work well when triggered exactly on the dot (grid), but often need to be triggered a bit before the beat. This makes it a hassle when using maps since they work better if they are following the grid, especially if you have a lot of quick changes. At least I don't see it a more optimized way than just using keyswitches.
I like the idea though, and have tried quit a bit to make it work. I am wondering how this could be applied in a better way so that it will help the workflow?
My solution is to map the keyswithes to a controller so that they follow a similar pattern, so that the controller is always laid out the same way, making workflow faster. Perhaps editing each instrument so that their keyswitches follow the same pattern in the expressions could be a solution. In any case, you need some work to set it all up.
You can use the info line at the top and adjust the start position of the selected articulations by using the mouse wheel or type in a value in order to have the articulation events happen before the notes. Select all of them and do it all in one swell foop.
So after hours of not getting this... is it because i have Cubase 11 elements? It just dont have the feature built in?
Pro only
Very helpful, thanks. Can these be applied to multiple tracks at once, or at least copied-and-pasted?
Ask Greg is the next Cubase Live Stream.
very cool, I wonder if this will work with EW Samples that have key switches
Yup! You can use the approach demonstrated here in this vid to map any key-switched instrument. Another really useful method is simply to load up any single patch instruments you have on to their own respective midi tracks and then hide them away in a folder (like a clarinet patch for legato, another one for staccato, etc) then make a 'master' clarinet midi track and create an expression map that will direct midi input to the appropriate patch on those hidden tracks. So you only see one Clarinet track, and can keep adding as many different patches to it as you want over time, hiding them away in a 'mapped' folder and updating your expression map to include the newly added articulations. This revolutionized my template - fyi Junkie XL has a fantastic video detailing how to do this - ua-cam.com/video/1gVWW2tKN8c/v-deo.html Biggest thing to keep in mind is you can be creative and make it work however you want it to.
This was VERY helpful. It was exactly what I needed to get my orchestral compositions a level further. Thank you
Is it possible to do the same thing with Halion Sonic SE3 on Cubase Pro 10? Cheers!
Yes..It works with any instrument that come up when searching VX in HalionSonic 3... 08:30 mark in the video
@@howlerbike Thanks!
Something this VIDEO DOES NOT POINT OUT is that there are already pre-built expression maps for most of the popular orchestral libraries out there.
Sadly UVI WORKSTATION's ORCHESTRAL SUITE is not among those, but building your own doesn't take that long.
I heard him point that out though
This is one of the many half baked features of Cubase.
We are supposed to be able to create our own expression “maps” (this isn’t just for showing the articulations in the key editor and switching them in a convenient way…), but unfortunately this is still not working in 2022.
In the Output Mapping section, we can set multiple articulation keyswitches for a single Slot, and sort them by velocity so that it plays a certain articulation between let’s say 0 to 20, another articulation between 21 to 50, etc. This is what the Data 2 column is for when the lane is set to Note On.
And for some reason this doesn’t work at all, only the topmost output lane takes effect regardless of the velocity.
And not to mention that the Expression Map window itself is badly made : super tiny add/remove buttons, text is cropped, value fields are buggy, and the output mapping cannot even be linked with the slots (create a lane with the same keyswitch automatically).
I’m sorry but to me this is currently one of the most badly designed part of Cubase, if not the worst. I hope this will be greatly improved in Cubase 13.
Thank you!
Thanks... 🍻
Literally had no clue this existed.
Firstly, the voiceover is way way too loud compared to anything else, tone it down for Gods sake. Secondly, in my experience of using expression maps, it takes absolute ages to create them, and sometimes they fail to connect to the key switching first time, very annoying. Thirdly, if you are going to have working examples, then isolate the violin part, so that we can hear the expression changes on just THAT part, don't play the bloody counter melody too.
"trilli" al pianoforte?
Así sea más largo el vídeo... pero dejen escuchar los ejemplos. Por que sus tienen que ser sus vídeos de tal forma?
Great Vid . But it is true. The best video Tutorial I really like and I'm sure everybody else is feeling is the same. When they and I can hear what it does. This Teritory. Most people have never seen or know what it is. Let a lone know how it works or even what you could use it for and describe how to work it in the order you explain. It is getting to see how it should sound ounce you do this new way of Mapping out scenario's. Or Presets to make different rythem changes on how the rythem can be played, and mapped out to make it run in a order your describe it to do. We all would like to see a finished change and how it sounds . So we know if we are following your direction correctly. Also knowing the sounds that the two different styles will sound like. So we know what to look for in the sounds of the Presets your Changing and how the differences sound in full "before and After." So we can all tell the differences between the two or All of them. So we know what to look for and how it should sound Before and After your Adjustment. I really love how your doing vids on things that Nobody else knows of or is covering. You have a wide selection. Also you have shown me more than I could fathem I could do with Cubase. KEEP THEM COMING. THis is just to help you understand what we all would like you to show us. It all boils down to how we all were taught how to learn from somebody teaching us anything new. Some people . They learn better by pictures and Discription. Some people you can just tell them simply, and they will know by association. And some take more than 2 times to learn by branding it it after multiple play backs. It's just we all want to hear the reactions as well as the Directions. Not meant to Unapreciated. Just need more Clearity in hearing the reaction as well as the Direction. Thanks Cubase For the Great Vid Share on VST Expression Maps. And how to Use Them. Cheers Cubase!
Yes, less voiceover, and the controlled track should be solo'd perhaps, quite difficult to hear articulations!
Voice sounds great tho...
This is a huge ‘weapon’ to use for advocating Cubase. A huge + for Cubase in comparison to other DAWs. Cubase for life!
We can't hear the things you are doing so we can see how valuable what you are doing is. I would have given you a thumbs down, but I will just thank you for the effort.
There is no way to sort expression maps ? What if you have a few hundred ? Can't even sort in alphabetic order, lol. Steinberg really disappoints, and they should learn from Presonus.
I appreciate these videos, but must say they are not really helpful. The reason is the explanation is so rushed and haphasered. So many crucial steps are skipped. I had to refer to random UA-cam videos to start working with this feature. Steinberg, you have great products but very poor tutorials. Please go through every step and show the functions in action.