Hidden Controls in MIDI Designer 1.5.1

Need for Hidden Controls: Super and Subcontrols

Supercontrols and subcontrols handle a lot of situations. Examples include:

  • button groups
  • supercontrols with a different number of steps or ticks
  • supercontrols that “gang” together several subcontrols
  • supercontrols that snap subs to a different value

Example: Button Groups

For instance, to get radio buttons, called “Button Groups” in MIDI Designer:

  • make a relative controls (knob, slider, etc.) the supercontrol of two or more buttons
  • now turning one button on will turn the others off

Consider this example screenshot:

The Problem

The crossfader can change the buttons, but for many users, it’s not necessary.

The Solution: Hide in Performance

In design mode, select Hide in Performance

Now when you switch back to performance mode, the crossfader is hidden.

Other Use Cases

In other situations, or most situation, it’s a subcontrol that you will be hiding in performance mode. While the subcontrol does the actual sending of MIDI messages in most cases, the user does not interact with it.

Take Away

Use Hide in Performance for any situation in which a super- or subcontrol does not need to be presented to the user in performance mode.

Comment on Facebook