Midi controller mapping problem

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi, I'm new with Tracktion T7 and have question about midi mappin/midi learn.

In Reaper, I can set the mapping to only work with active plugin/track. For I can map pot 1 in channel 1 to all of my VSTs and it only changes value in active VST. I tried this in T7, but had no luck. I mapped pot 1 in channel 1 to two differents VSTs and it changes values in both even I only have other one active.

Can this be done in T7?

Post

mette1005 wrote:Hi, I'm new with Tracktion T7 and have question about midi mappin/midi learn.

In Reaper, I can set the mapping to only work with active plugin/track. For I can map pot 1 in channel 1 to all of my VSTs and it only changes value in active VST. I tried this in T7, but had no luck. I mapped pot 1 in channel 1 to two differents VSTs and it changes values in both even I only have other one active.

Can this be done in T7?
As near as I can tell, control surface mapping in Tracktion is on a global basis per MIDI input port for the DAW workspace. If you were to use CC16 on a MIDI controller knob #1 input for example, then any plugin parameter you learn to CC16 for that input will respond to any CC16 message seen on that channel. It seems that the concept of 'in focus' or 'active' plugin exclusive mapping is not implemented, like in some DAWs.

The only way around this I can find is to set MIDI input to only one track at a time (assuming your plugins are on separate tracks), or use separate MIDI controllers so that they are sending over different MIDI ports.
Windows 10 and too many plugins

Post Reply

Return to “Tracktion”