I think semantics are clouding the issue, I will give a shot to clarifying.
A problem with what follows (in the sample set I’m working with, Xsample Chamber Orchestra) is that it only works for direction, and not attribute. Possibly Mogular needs them to work as attributes. It would seem that it would work that way though.
Anyway, I think you can do as follows (I am using string articulations, but a sample is sample…)
Let’s say I am setting up a map for a keyswitch which, combined with one of three CC values, gets three kinds of pizz. I have to set up three sound slots. All share the keyswitch, each have different CC values.
One slot just has ‘pizz’ in Art. 1, and has the keyswitch and a CC for pizz
The second slot has pizz in Art 1, and ‘Bartok’ in Art 2, and just the CC for the bartok pizz
and the last has ‘pizz’ in Art. 1 and ‘Behind Bridge’ in Art 2, and just the CC for that kind of pizz.
In the Articulations lane and in Score edit you now have three articulation marks. Pizz, bartok, and behind bridge. I insert pizz; or pizz & bartok; or pizz & behind bridge, to get each of the respective articulations.
If I just place the 2nd or 3rd (bartok or behind) the result is a CC gets sent to the track without the keyswitch.
The point is that regardless of all else, a sound slot can only send the message in its Output Mapping pane, but by combining articulation marks you can get more data sent to the instrument. So if Mogular has staccato+fall he creates the staccato, and creates the fall articulations, and simply places fall right after staccato in Score or Key edit. Hope that makes sense. (It also seems to me that if they are both attributes the two switches will get sent simultaneously, but I can’t test that)
Writing this was as much an exercise to learn how to use expression maps as it was to help out (maybe more) so thanks for that!
Also thanks and props to vic_france and his post in the old forum (linked above) for helping me get my head around this. It definitely is not intuitive for me.