Imagine you have the MuSynth open and you would map CC1 to the cutoff of filter 1. If you map a MIDI CC by right-clicking a parameter (as explained above), then the mapping is stored into the module that currently has MIDI input focus, which is not necessarily that parameter's module itself. So MIDI CC mappings can exist on any modular level in the modular tree structure. You can see it as a tree structure with the root being the Project Modular Area.Įach module (also VST plug-ins are modules) has its own MIDI controller map. MUX Modular is constructed in a modular way. There you'll find "Map MIDI Controller" and you'll see that the last tweaked parameter is already set as the target parameter. Instead of right-clicking a VST parameter you give it a little tweak and then open the VST plug-in context menu via the Options button at the top of the VST editor, This will open a dialog panel and when you tweak your MIDI controller it will automatically be recognized as the source.įor VST plug-ins the procedure is similar but because MUX Modular has no access to the VST editor itself, The easiest way to map a MIDI CC to a MUX module parameter is to right-click the parameter knob -> "Map MIDI Controller".
For example you could map the modulation wheel on your MIDI keyboard to the cutoff of the lowpass filter of a synth. Besides the fact that you can use MIDI events (including MIDI control change events (MIDI CC)) to trigger context functions (see Function Shortcuts) you can also use MIDI CC events to control module parameters.
0 kommentar(er)
