MIDI CC mapped to widget does not pass through Wiring to plugin

Gig Performer on Mac OS X
1

Hi everyone,

I discovered an important behavior in GP5 regarding MIDI CC routing that I want to share and get confirmation on.

Setup:

  • M-Audio Keystation MK3 + Korg NanoKontrol 2 + Launch Control XL3 → all connected via MIDI Rechannelizer → Omnisphere (Multi, 8 parts)
  • Widgets panel with faders and encoders mapped to controllers

Observed behavior:
When a CC message (e.g. CC29 from LCXL3) is mapped to a widget on the panel, it reaches the widget correctly BUT does NOT pass through the Wiring to the plugin (Omnisphere). The virtual cable shows zero activity for that CC (the indicator displays MIDI activity and the widget responds to encoder movements).

However, when the same CC is NOT mapped to any widget, it flows freely through the Wiring and reaches Omnisphere — confirmed by cable activity and successful MIDI CC Learn inside Omnisphere.

This means it appears to be impossible to simultaneously:

  1. Control a widget visually on the panel
  2. Have the same CC reach a plugin directly through Wiring

Questions:

  1. Is this the intended behavior in GP5?
  2. Is there a way to have a CC both control a widget AND pass through Wiring to a plugin at the same time?

Note: I’m on Mac OS X — not sure if this behavior is platform-specific or applies to all platforms.

Thank you!

2

Take a look at the widget property „Pass Through“

3

As @pianopaul mentioned:

000222
000222864×231 67.8 KB

4

Yes, it is.

The purpose of the widget is to control a plugin parameter via ‘host automation’. You do this mapping in the widget properties.

So this will usually achieve the same goal you are after, but just not by the midi message being directly received by the plugin in Wiring view.

5

Yes, it is intended. Most of the time, a message that is being used to control a widget should not also go directly to a plugin. That is the whole point of using widgets to control plugins via host automation.

I bet you are trying to control a plugin directly with a MIDI message…….in general, don’t do that.

6 
Is this for two-side exchange by "Host Automation"? I agree. Thanks for the tip! 

And what about use of NRPN in GP (I now see that CC is not anough)?
7

The point of using widgets as an intermediate between your controller and plugins along with the more modern approach to controlling plugins, I.e. host automation, is so that you are not locked into specific MIDI messages.

1 Like