When using Program Changes to trigger Expression Maps, it seems that Program Changes are routed to the Expression Maps before the input transformer of a channel. This is a problem for a variety of use cases, but essentially it means that Program Change messages can’t be filtered out by MIDI channel, they spam the entire port even if the Channel is filtered in the track through the input transformer. This needs to be fixed because this kind of Port/Channel routing happens often with Orchestral setups and more intricate synthesizer setups. Does anyone know of a workaround to contain Program Change messages to Port/Channel when dealing with Expression Maps? Major design issue!
UPDATE: I did some further tests and it looks like the same applies to Key Switches if you are using them for the Expression Map remote. It seems like MIDI is routed to the Expression Map on a per-port basis before it hits the track input transformer.
I use Expression Maps because its a great concept for Composers with large templates or those that benefit from the workflow. But using them is a major headache that requires so many odd workarounds and fixes. Expression Maps really need to be re-designed.
Hi and welcome to the forum,
You write, it’s broken. When was it working correctly (according to your expectations)?
Or is this post a feature-request?
No, it is not a feature request. It is a report of a broken behavior as explained in the beginning of the post >> Program Changes are routed to the Expression Maps before the input transformer of a channel. This is a problem for a variety of use cases, but essentially it means that Program Change messages can’t be filtered out by MIDI channel, they spam the entire port even if the Channel is filtered in the track through the input transformer.