Expression Map - Helpful Additions

[reztes]

@raino

@reztes

Yes, they need to be improved.

I would add the ability to change which expression is used by default when recording. Currently is the first one, but it would be nice that you could choose. For instance, I have Violins and some times I want to record with sustain and others with shorts. It would be as easy as allow to click in the panel in the left and select the default articulation (the green triangle).

Expression maps could be a killer feature, but they are like an eternal promise, never fullfiled.

I think if you drag a slot to the top of the list it will use that as the default.

Also if you have a blank slot at the top, nothing becomes the default (or rather that slot is the default and it does nothing).

I know, but it is not exactly what I’m asking for.

Currently, you can change it but you have to edit it through the Expression Map menu, which is not the most accessible one.

What I’m asking for is the ability to change it easier and faster in each track. Now I want to record staccatos mainly, then I set the default to staccato. If I want to record sustain, I change the default to sustain again. This way, I can record using the expression maps in a much better way. I think that now you have to stick with the default one when using attributes. I would like this to be more flexible.

[fbeauvaisc]

+1

[Stephen57]

the first of what may become an annual +1

[jcbfoos]

+1,000,000,000,000,000,000,000,000,000,000

[maxliefkes]

+1 zillion, especially the per articulation delay option

[T-bag]

Just read this after a day at the coalface of preparing some new expression maps - to all of the above + 1 Googol

[Frank_Heller]

What a great list of excellent
suggestions. If you use Expressions, how could you not plus one this?

+1

[reztes]

Also, folders for keeping your project Expression Maps organized!

[jcbfoos]

Also if this bug could be fixed.

https://www.steinberg.net/forums/viewtopic.php?f=253&t=117118&p=637311&hilit=expression+map+retro#p637311

It’s been reported before but never addressed. =(

[composingkeys]

+1

[EmmCeeSq]

+1 - Essential!

[ecolvin]

+1 to the original post. Great ideas!

[Puma0382]

+1 - the users have spoken.! In great numbers.! With great ideas.!

[JBuck]

There is an issue when deleting Expression Maps in the Exp. Map setup. It seems to change the order and thus reassigns Exp. Maps to different tracks.

[Robert_Kooijman]

@orchetect

Steinberg, please consider adding some basic useful features to setting up/maintaining Expression Maps that will go a long way to helping us save time and sanity.

In the Expression Map Setup window:

• Please allow us to duplicate a map. A ‘Duplicate’ button would suffice.
• Please let us reorder the maps in the list by drag & drop or at least sort alphabetically.
• Please add some sort of indication whether a Map is in use in the project. This could be as simple as adding a little icon next to it, or making the name of the Map in the list bold. (Massive bonus points if you add a way to see which track(s) are using each Map in a single table.)
• When deleting an Expression Map, PLEASE add code that checks if that Map is currently in use on a MIDI or Instrument track in the session, and ask for confirmation before deleting if that’s the case. It’s incredibly easy in large sessions to lose track of where Maps are being used (especially with different revisions of the same Map in use) and inadvertently delete one that is in use, and only discover the oopsie hours or days later.
• Ability copy and paste slots in the Setup window

In the Key Editor:

• A way to manage articulations when the viewing starts to get full in the controller lane
• When an Expression Map is assigned to a MIDI/Instrument track, add the ability to uniquely name controller numbers with useful names (such as CC21 = “Vibrato”) - these custom names should appear in the Key Editor’s CC lanes. These names should be stored with the Expression Map since they can vary for each sample library.

Bonus:

• Independent MIDI offset (like milliseconds offset on MIDI tracks, + or -) per articulation; many sample libraries have varying note attacks/pre-laps that vary by articulation.

Cheers

+1 for these great and long overdue improvements!

[davaakhuudson]

+1

[JBuck]

Often times one needs to transpose key switches to an higher or lower octave. The VSL Vienna Instruments player has the ability to transpose all key switches by a simple click and drag. This would be great in the Expression Map setup. There is this sort of but it only works for one note at a time. To be able to select e.g everything from C0 to B1 and then transpose them up and out of the conflicting range while leaving everything from C-2 to B-1 would be great. Even if there was a keyboard in the UI to indicate the range as well.

[EmmCeeSq]

+1000

Expression maps need a LOT of love. Great concept, implemented pretty well, just really need some updating now they’re really catching on.

Sorting by name would be a good start, and duplicate.

[JBuck]

@EmmCeeSq

+1000

Expression maps need a LOT of love. Great concept, implemented pretty well, just really need some updating now they’re really catching on.

Sorting by name would be a good start, and duplicate.

Please consider liking my post it is called ‘Expression Maps Overhaul’ it is in the Cubase 10 forum.

[BenjaminParis]

+1