I thought I explained above. In this particular situation, if the plugin doesn’t provide a parameter for it, then you use the host automation support provided by the GP Midi In Block to generate the CC1 message rather than sending CC1 directly from hardware directly to the plugin.
This has many benefits:
-
you can use physical knobs, sliders or expression pedals to cause CC1 messages to be sent to the plugin even though those physical knobs, etc. are themselves generating completely different CC numbers
1.1 That means you don’t have to adjust your physical expression controller to actually send real CC1 messages. Your expression pedal can be sending out CC11 values, it doesn’t matter.
-
you can leverage widget scaling so, for example, moving your expression pedal through its full range will only cause a subset range of CC messages to be sent, i.e, sending CC values between 0 to 127 from your expression pedal might only cause values between 0 and 20 to be sent to the plugin. Heck, you can even invert the values so sending 0 to 127 from your expression pedal will send 127 to 0 (or 64 to 0) to the plugin
-
Using widget grouping, your single expression pedal can control multiple parameters simultaneously, for example speed up the LFO vibrato while increasing the filter cutoff frequency or do volume cross fading or morphing, etc