MIDI CC Common Assignment Lookup

Bounded common MIDI 1.0 controller assignments; device implementation and channel-mode behavior may vary.

Description

Look up the names of supported common MIDI controller numbers.

MIDI Control Change messages identify controllers by number. This lookup provides names for the tool's supported common assignments, helping distinguish a controller number from a note or program number.

When to use this tool

Look up the names of supported common MIDI controller numbers. Use it when the input measurements and conventions below match the operation you need.

  • Prepare controller, respecting the measurement basis and boundaries below.
  • Compare the worked example with your intended operation before reusing its result.

How to use the tool and how it works

  1. Enter every field in the input table using the stated units and exact supported selector spelling where applicable.
  2. Run the tool. Correct input errors before interpreting an output.
  3. Read the result fields below; use accompanying flags and the stated sign, boundary or model convention when interpreting a number.

Choose an exact controller selector from the built-in table. The tool looks up that key and returns its stored reference text; unsupported controller values produce an input error.1

Input fieldMeaning and unitsAccepted input
controllerController.Exact value: "0", "1", "7", "10", "11", "32", "64", "65", "66", "67", "91", "93", "120", "121", "123"
controllerBuilt-in entry
"0"Bank Select MSB
"1"Modulation Wheel
"7"Channel Volume
"10"Pan
"11"Expression
"32"Bank Select LSB
"64"Damper Pedal
"65"Portamento On/Off
"66"Sostenuto
"67"Soft Pedal
"91"Effects 1 Depth (reverb)
"93"Effects 3 Depth (chorus)
"120"All Sound Off
"121"Reset All Controllers
"123"All Notes Off
Output fieldInterpretation
resultObject containing the following named result fields.
result.referenceThe stored entry for the exact selected key; its type may be text, a number or a list.
json
{
  "input": {
    "controller": "7"
  },
  "output": {
    "result": {
      "reference": "Channel Volume"
    }
  }
}

Limitations and assumptions

  • Only the listed assignments are covered. A device or patch can implement a subset or use its own mapping; no MIDI message is sent or observed.
  • Every declared field is required and unexpected fields are rejected. Numeric inputs must be finite; input errors are distinct from a valid false result or an explicitly qualified output.
  • Extremely large inputs and nonfinite or excessively large outputs are rejected. List positions reported by the tool use zero-based indices unless stated otherwise.

Alternative or Complementary methods

Check the intended score, tuning or device configuration before applying a numerical reference. Use notation-aware or audio measurement methods when the task requires interpretation of a score or actual sound. Compare the scope of the nearby tools below before substituting one.

References

  1. Tool behavior and example: MIDI CC Common Assignment Lookup — tool.io

Similar or alternative tools

  • Dynamic Marking MIDI Velocity Lookup

    Qualified caller-reference registry: actual instrument/patch and independently chosen dynamic-to-MIDI velocity mapping; not a MIDI standard mapping. Requires independently applicable source/context/date evidence; not an authoritative table, omitted predictive model, diagnosis, permission, safety or compliance determination.

  • frequency from midi

    Convert a MIDI note number to its equal-tempered frequency with A4 = 440 Hz.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies