Yes - all for it. One pet peeve is is that I would like the ability to have the midi channel default to the channel for the instrument the track is on. For example - I have a 1st, and 2nd violin. They are both on the same single instance of a VST in the rack, and they are loaded as violin 1 in slot 1 and and violin 2 in slot 2. So they also use midi channels 1 and 2 consecutively. Allow me to use the same expression map on both, but make my articulations appropriate to the midi channel they are coming from.
Studio One 5.2 really has surpassed Steinberg with Expression Map functionality. Please allow Expression maps to all load into Cubase globally, not per project, allow to import multiple expression maps at the same time, and also allow sample library makers to embed their expression maps in Cubase/Nuendo like Studio One! Really feel Steinberg has been lacking with refining expression maps. Please guys! Thank you.
By this do you mean, tell Cubase where to look for Expression Maps when loading a project?.
Cubase needs to load EM data from an independent location, not save/load EM data with the project file.
Because what gets old really quick is when I edit an Expression Map and then have to go and reload it in all my previously started projects.
Yes, that would be good too.
Basically, my thought process is when started from scratch in project, you don’t have to select to load each expression map you want one by one. It would be much better to have a directory where you tell Cubase where the Expression Maps are stored and then you can simply click on whichever expression map you wanted, not need to import them one by one. Also, I think it would be great for Sub Folders to be available in an expression map so for libraries that have many patches, you could have a “long” folder which could have variations in there to find. If you have too many articulations, the expression map lane gets too hard to read/see properly. Studio One 5.2 that just came out has some great improvements and Expression Maps really need an overhaul.
Ok gotcha. Re: Sub Folders, there is the group feature in the Articulations list on the right side of the EM setup. If we could get a key command to show/hide particular groups, that would solve some of the overcrowding issues in the EM lane. EM’s need some serious lovin’.
This would likely have to be a purely additive feature and not an alteration of the current implementation.
Case in point:
I work extensively with custom Expression Maps that I create. This generally involves creating an Instrument Track, loading VSTi presets and patches on it (ie: Kontakt patches, etc.), creating an Expression Map for it, then saving that track as a Track Preset so I can load it into new projects easily.
Having the Expression Map 1) saved inside the track preset and 2) saved inside the project, ensures that that particular configuration is preserved for years to come and the project will re-open and play back the same. As VSTi’s and sample library patches change over time this allows me to update them as needed to ensure stability of my projects. Sure, the point about manually having to update Maps when they change retroactively is not possible, but that’s a deep can of worms and not an easy problem to solve for developers or end-users alike. The same issue plagues things like Kontakt libraries. The Kontakt instance in the project stores the instrument and does not auto-update to the newest version of that instrument on disk if you’ve since updated the library.
What happens if Your Favorite Sample Library gets an update and they change keyswitches or controllers internally? Or you decide to add/modify that instrument and want to update your Expression Map for it? If Maps were stored only globally, your old project may erroneously load the new Map and not work correctly, causing hours of lost downtime chasing why X instrument track is not playing back correctly – assuming you even notice it is malfunctioning as you may not discover it until days, weeks, or months later. Then multiply this by hundreds of sample libraries, hundreds of track presets, dozens/hundreds of Expression Maps.
I would rather have control over where and when Expression Maps are stored and updated. If a global storage option is introduced, I would hope that current workflow does not regress in this area.
I just tried this with Studio One and VSL Synchron Strings and it really is amazing. I hope there are some expression map improvements in Cubase 11.5 too.
We need EM’s to be part of the Track Import functionality. Then, if I load an old project I have the old EM. But, if I want the new EM, I import it from the project/template that I recently saved with the new EM. Boom!
Also: Workflow enhancements for common mass-operations like “Generate 10 keymaps from C1 to D2” and so.