# Inputs

Inputs are MIDI signals detected from your physical controller. Each input represents one control.

In beta there is less UI distinction between what is CC, NRPN, SysEx etc. but compatibility for all your usual MIDI controls is in there, and better distinction/recognition is in the roadmap.

When you press a button or move a fader on your controller, MIDI Mimic automatically detects the signal and creates an input tile.

### Control types detected

**Button**

* Binary on/off signals
* Can be CC (e.g. CC64) or Note (e.g. Note On/Off)

**Continuous**

* Signals with a range of values
* Faders and rotary knobs both appear as Continuous in beta
* Usually CC signals with values 0-127

**NRPN**

* 14-bit parameter sequences (CC99 → CC98 → CC6 → CC38)
* Detected automatically and displayed as Channel + NRPN parameter number

**SysEx**

* System exclusive messages are received and logged internally
* Not surfaced as tiles in beta
* One-way Passthrough is supported in beta

#### System messages (no tiles)

MIDI system messages (Clock, Active Sensing, Start, Stop, etc.) pass through silently and never create input tiles.

### Input tile anatomy

<figure><img src="/files/t1krW8AC0DArHRMazzmC" alt=""><figcaption></figcaption></figure>

Each input tile shows:

* **Control type icon**: Button or Continuous
* **Device name**: e.g. "Faderfox EC4"
* **Signal type label**: CC, Note, or NRPN
* **CH / CC / VAL readout**: Current channel, CC number, and value
* **+ADD MACRO button** (if unlinked) or Macro name if linked

### Rules

* **One input, one macro:** Each input can only be linked to one macro at a time
* **Read-only in Session View:** Input properties (device, CC number, etc.) are read-only here. Editing happens in the Macro Editor
* **Unlinked inputs pass through:** An input with no macro attached passes its signal through unchanged

### Next steps

Click **+ADD MACRO** on any input to start creating a macro. See the [Macro Editor](/midi-mimic/macro-editor.md) guide for next steps.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://midi-mimic.gitbook.io/midi-mimic/inputs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.