Control your rig from your Stream Deck
MIDIRover is a free Stream Deck plugin that sends MIDI to Neural DSP and any MIDI-enabled plugin or DAW. This guide covers everything — installation, every action, Learning Mode, and a Neural DSP walkthrough.
What you need
- A Stream Deck — the key actions run on any model with keys (Mini, MK.2, XL, Neo, Stream Deck + and + XL, the Pedal), the dial actions on any model with dials (Stream Deck +, + XL).
- The Stream Deck app installed (Elgato, free).
- Windows: a MIDI port has to exist already, because MIDIRover cannot create one — the free loopMIDI is the usual way to have one. macOS: nothing extra to send — MIDIRover makes a port of its own, named
MIDIRover, whenever the port is left on Auto or the one you picked is missing. That port is one your software reads from, so nothing can send back into it: the optional Feedback input therefore has to arrive on a different bus, and an IAC Driver bus switched on in Audio MIDI Setup is the usual one. - The software you want to control — Neural DSP (any plugin), another amp sim, a synth, or a DAW that accepts MIDI.
Install & first run
Install the plugin
Add MIDIRover from the Elgato Marketplace. It appears in the Stream Deck app under the MIDIRover category.
Set up a MIDI port
Windows: open loopMIDI and create a port (the default “loopMIDI Port” is fine). macOS: skip — the port is automatic.
Pick the port
Drop any MIDIRover action on a key and open its settings. Choose your port under MIDI Port — or leave it on Auto (Windows: Auto-detect for every key (prefers loopMIDI); macOS: Auto for every key (virtual MIDIRover port)). The choice is shared by every key — which is what for every key in the label means — and the line just under the dropdown confirms where MIDI is actually going.
Make your first key
Drag Control Change onto a key. Set Channel and CC Number to whatever your software will listen on — and if you do not know yet, leave them: you will set them by ear in a moment when you MIDI-Learn. Nothing else on that panel is required to send. The Control Change reference explains the rest when you want it.
Check it works, before touching anything else
Press Send now in the key’s settings. It fires that one message and changes nothing else — a Toggle key does not flip, a Momentary key is not left held — so you can press it as often as you like. Then read the line under MIDI Port: grey means MIDIRover sent where you meant it to, which is the whole of what a plugin on this side of the cable can promise. Anything still wrong after that is downstream, and Troubleshooting starts exactly there.
Core concepts
- MIDI port
- The virtual cable between MIDIRover and your software. One port is shared across all your keys — set it once. A key can be pinned to a different port if you need two destinations, and Use the deck default puts it back on the shared one. Pinning works, but MIDIRover holds one port open at a time, so keys on two ports make it close and re-open between presses — fine on a virtual cable, less so on some hardware.
- Channel
- MIDI has 16 channels (1–16). Your key and your software must agree on the channel. Most setups leave everything on channel 1. New keys default to the channel you last picked, so once you move your rig to, say, channel 2, every key you add follows automatically.
- CC, Program, Note
- The three everyday message types. CC = a knob/switch (0–127). Program = recall a preset. Note = a musical note on/off.
- MIDI Learn
- Most plugins have a “MIDI Learn” mode: you arm a control, send it a message, and it binds. MIDIRover sends the message — you press the key to teach your plugin.
- Sends, and Send now
- Every action that puts MIDI on the wire shows a Sends line in its settings: the exact message a press will produce, in words and in hex, updated as you type. Beside it is Send now, which fires that message once — so you can verify your routing from the panel instead of reaching for the deck. Nothing is ever sent because you edited a setting. Picking a CC number to look at it is not the same as choosing to send it, and on a live rig an editor that transmits while you browse can fire a preset change at the band. The only ways MIDIRover sends are a key press, a dial turn, and this button.
It fires exactly what the Sends line promises — for a Momentary key that is the press and its release, so a test never leaves a control held on. It changes nothing else: a Toggle key does not flip, its light does not change, and clicking twice sends the same value twice rather than alternating, because testing a key should leave it exactly as you found it. Modes that send a stream rather than a message — Sweep and Fade — have no single press to reproduce, and the button says so.
Keys have it; dials do not. A key has one gesture and the button repeats it. A MIDI Dial has two, and the one you set it up for is turning — which is a stream of values across a gesture rather than a single message, so there is nothing for a button to fire. Receive-only actions have no Sends line and no button either. - Colour theme
- A shared Deck theme recolours every MIDIRover key and dial at once — pick one of six presets, or set your own two colours, in any action's settings. Each key can also override it: its This key setting follows the deck theme by default, or takes its own preset or custom colour, handy for colour-coding by function. The second box on both rows sets the key background — dark (the default) or light — deck-wide or per key; presets adjust their colours per background so both stay readable, and on light keys the key's Name is drawn in black as part of the face. (This reaches the Stream Deck + touch strip too, on every Key graphic — Bar, Knob and Level meter all follow the deck theme and a per-key override, because MIDIRover draws all three itself.)
| Control Change | B0type + ch 107CC 764value 100 |
|---|---|
| Program Change | C0type + ch 105Prog 5 |
| Program Change, with a bank | B0type + ch 100CC 000value 0thenB0type + ch 120CC 3202value 2thenC0type + ch 105Prog 5 |
| Note On | 90type + ch 13CNote 6064value 100 |
| Note Off | 80type + ch 13CNote 6000value 0 |
| Note On at Off velocity | 90type + ch 13CNote 6000value 0 |
- Windows
- MIDIRover cannot create a port — in either direction. One has to exist already, which is what loopMIDI is for.
- macOS
- MIDIRover creates one port of its own, named
MIDIRover, and it is an output: your software reads from it. Nothing can send back into it, so Feedback has to arrive on a different input — an IAC Driver bus is the usual one. - The same port can do both
- Where one port carries both directions, MIDIRover drops the copies it just sent — the same bytes arriving within 400 ms — so its own echo does not move the key. It matches bytes, not senders.
Actions reference
Drag any of these onto a key (or a dial, on a Stream Deck + / + XL). Give it a Name to label the key — or leave it empty, and the key names the message it sends: CC22 ch1, PC22 ch1, C4 ch1, or a Bank pair’s id and channel like A ch1. If you have already named that CC, program or note in its dropdown, the key uses that name instead, so you never type it twice — on every key type, dials included. A Bank key is the one that needs a word of explanation: in its usual Program Change mode it does not sit on one preset, it walks a range, so the preset name appears on the key’s value line as the counter reaches it (Lead instead of 3) while the top line keeps the A ch1 that tells one counter from another. In Control Change mode there is one controller, so its name goes on the name line with the id kept: Drive A. The box beside Name sets its font size in px — 10 to 30, 22 by default. MIDIRover draws the label into the key face itself, so it always matches the key's colours and its light or dark background. The Stream Deck app's own Title field still works and draws on top in whatever font and colour you choose — so use one or the other, or the label appears twice.
At a glance
What each action can do. Sends puts MIDI on the wire when you press it; Follows feedbackcan listen on a MIDI input and follow what it hears; Learn can capture an address from an incoming message instead of you typing it; Multi-Action can be used inside Stream Deck’s own Multi Action. This table is generated from the plugin itself, so it always matches the version you have installed.
| Action | Key | Dial | Sends | Follows feedback | Learn | Multi-Action |
|---|---|---|---|---|---|---|
| Control Change | ✓ | — | ✓ | ✓ | ✓ | ✓ |
| Program Change | ✓ | — | ✓ | ✓ | ✓ | ✓ |
| Bank Up / Down | ✓ | — | ✓ | ✓ | — | ✓ |
| Note | ✓ | — | ✓ | ✓ | ✓ | ✓ |
| Advanced MIDI | ✓ | — | ✓ | — | — | ✓ |
| MIDI Dial | — | ✓ | ✓ | ✓ | ✓ | — |
| Panic | ✓ | — | ✓ | — | — | ✓ |
| MIDI Readout | ✓ | ✓ | — | ✓ | — | — |
| MIDI Meters | — | ✓ | — | ✓ | — | — |
| MIDI Monitor | ✓ | — | — | ✓ | — | — |
| Tempo | ✓ | — | — | ✓ | — | — |
| Label | ✓ | — | — | — | — | — |
A Multi-Action tick means the composer will accept the action — not that every mode behaves there as it does on a key. Measured on hardware: inside a Multi Action the press and the release arrive about a tenth of a second apart however long you hold the button, because Stream Deck synthesises both of them after your finger is already up. Three consequences worth knowing before you build one. Momentary and Note Hold become a brief pulse rather than a hold, and Minimum hold is the only thing that can lengthen them. Sweep and Advanced’s Ride while held have nothing to ride: each press nudges the value a few steps and leaves it there, so pressing repeatedly walks the parameter instead of sweeping it. Everything else is unchanged — Fixed, Toggle, Note Tap, Program Change, Bank and Panic send exactly what they send on a key, and Fade to value is better in a composer than on one: it runs to completion on its own after the Multi Action has moved on to its next step.
Control Change
CCThe workhorse for stomp-style controls — drive, delay, reverb, boost. Toggle an effect on/off, send a fixed value, or make it momentary (on only while held).
| Toggle · Icon On / off each press — the key shows its state. Default display: the power icon. | |
|---|---|
| Toggle · Switch (vertical) The same on/off, drawn as a lever switch — up (on) / down (off). | |
| Toggle · Switch (horizontal) The same on/off, drawn as a lever switch — right (on) / left (off). | |
| Toggle · Play / pause The same on/off, drawn as transport — play (off) / pause (on). | |
| Fixed The same value on every press. | |
| Momentary On while held, off on release. | |
| Sweep · Slider Hold the key to sweep the value — a wah or volume ride. Default display: a linear slider gauge. | |
| Sweep · Knob The same hold-to-sweep, shown as a rotary knob with a value ring. | |
| Sweep · Value / Gauge The same hold-to-sweep, drawn by the Display row: the number alone, with its name, or as a Bar or Arc gauge — the MIDI Readout faces, on a key that sends. | |
| Fade to value One press and the value travels to its target on its own — a hands-free swell, both hands still on the instrument. The ramp is the shape, and it points the way the key will run — rising for a fade up, mirrored for a fade down. The fill is where the parameter is now, so a fade-out key starts full and empties as it runs. |
| CC Number | The controller number you map in your plugin (0–127). Controllers with a fixed job in MIDI are labelled for you — 122 · Local Control, 123 · All Notes Off — and you can rename any of them (22 · Gain), which shows on every key that offers a CC list for that channel — the MIDI Readout key’s Number list included, though renaming itself lives on the keys that send (see section 6). Every other number stays bare on purpose — and not because it has no conventional meaning. CC 1, 7, 11 and 64 are widely used for Modulation, Volume, Expression and Sustain, but nothing stops a plugin repurposing them, and a label that is right most of the time cannot be switched off. What is pre-labelled are the controllers that carry a function in MIDI rather than naming a destination for a value: the channel-mode commands (120–127), the RPN/NRPN parameter mechanism (6, 38, 96–101), and Bank Select (0, 32), which changes how the next Program Change is read. |
|---|---|
| Value On / Off | The values sent for the on and off states (default 127 / 0). |
| Release sends | Momentary only. Normally the release goes back to the same CC as the press. Set it to a different CC and one key can press one control and release another — press CC10 at 127, release CC12 at 64 — which no pair of keys and no Multi-Action can do, because both halves belong to one physical press. The key’s lights still follow the press CC. |
| Release CC | The control the release is sent to, when Release sends is set to a different CC. Leave it blank and it falls back to the press CC, so a half-finished key behaves exactly as it did before. It shares your CC names with the press control. |
| Minimum hold | Optional, and almost always best left empty. Some gear and hosts IGNORE an off message that arrives within a couple of hundred milliseconds of its on, and go on treating the control as held — Cubase’s Forward is the documented case, at 250 ms. Set a floor in milliseconds and a release sooner than that WAITS until the floor has passed. The message is delayed, never dropped: switching page or letting the deck sleep sends it immediately rather than waiting, so a note can never be left ringing. Momentary only on Control Change, Hold only on Note, and the two snap back press modes on Advanced MIDI — the three places a key sends a second message when you let go. |
| Latch group | Toggle keys sharing a group name act like radio buttons — turning one on turns the previous one off. Leave blank for independent toggles. |
| Sweep time / Range | Sweep mode: seconds for a full sweep (1–10) and the min–max span; the sweep bounces at the ends and remembers its position. |
| Fade | Fade to value mode: where a press heads (default Reverse each press). Reverse each press alternates — a press ramps to whichever end of Range is farther off, and the next press brings it back, so one key plays both halves of a swell — and the key face turns over as each fade lands, so it is already showing which way the next press will go. Out and In always head for the same end of Range. To a set value ramps to the number in Fade to and stops there — that row appears for this choice only, because the other three work the target out from Range themselves. |
| Fade to / Fade time | Fade to value mode: with Fade set to To a set value, the value the ramp travels TO — and, whichever direction is set, how long the ramp takes. One press and the value moves on its own — both hands stay on the instrument, which is what separates it from Sweep (where you hold the key for the whole move). Press again to stop it where it is; press once more and it carries on from there. Editing either setting mid-fade stops it too, since the ramp in flight was planned from the old numbers. Range clamps the target, so a target of 127 on a key ranged 40–90 ends at 90. Best on a continuous parameter — volume, mix, gain — because a switch-like one just flips somewhere in the middle. Fade time offers presets from 0.25 s to 8 s, plus Custom…, which reveals a Seconds box where you can type any value from 0.25 to 60. Longer is not smoother. A Control Change carries 128 values at most, so a longer fade spreads the same number of steps further apart rather than adding any — the send preview states the interval, and over a narrow Range it gets coarse fast: 8 s across 40–90 is one value every 160 ms, but 60 s across the same range is one every 1.2 s, which you can hear as steps. The panel warns you when it reaches that point. |
| Resolution | Any mode, and only for CC 0–31. A Control Change normally carries one 7-bit byte, so a sweep has 128 steps — enough for most things, and audible as a zipper on a slow filter ride. Resolution sends each value as a pair instead: the coarse half on your CC and the fine half 32 controllers above it, so CC 20 is joined by CC 52. That is the pairing the MIDI specification defines, which is why the row disappears above CC 31 — there the second controller is simply unrelated. The setting is kept rather than cleared, so moving back to a controller that can pair restores the width you chose — and while it cannot apply, the key says so in its own notes instead of leaving you to wonder. Your gear has to agree, and this is the whole risk. On a device that does not implement the pairing the fine half is not ignored: it moves whatever that controller does. Leave this on Standard unless your MIDI implementation chart says the parameter is high-resolution. Neural DSP does not pair, so leave it alone there. Two widths, because gear differs. 14-bit gives 16,384 steps; 8-bit gives 256 and is what Novation’s wide parameters use on the Peak and Summit. Picking the wrong width still addresses the right controller — it just sends a value your gear reads as too large or too small. Switching it on widens every value row — Range, Fade to, Value On and Value Off — and each becomes a type-in box rather than a list, because 16,384 options is not a dropdown. A row also becomes a type-in box while it is holding a number too large for the list, which is how a value typed at 14-bit survives the key being narrowed again — by moving the CC above 31, say. It stays, outlined in red, and the key's own notes say what the wire really carries, rather than the number being quietly trimmed to 127. An unset Value On means full scale, so it follows the width too. Format and Name these values switch off — both are built on a 0–127 scale and would describe a different control — The key still follows Feedback: MIDIRover reassembles an incoming pair, so a device moving the parameter at full resolution moves the key with it. It waits up to 50 ms for the second half, and a device that sends only the coarse half leaves the key where it is rather than jumping to a value 128 times too small. Why a Toggle needs it too. A sweep gains the finer steps, which is the obvious case. A Toggle, Fixed or Momentary key gains something different: on a device whose parameter really is a pair, sending only the coarse half leaves the fine half wherever your gear last set it, so the value lands near the one you asked for rather than on it. A Momentary key whose release goes to a different controller pairs only where that controller can — above CC 31 the release leaves as one 7-bit message, and an Off value above 127 is trimmed to fit it. |
| Pair order | Shown once Resolution leaves Standard: which of the pair’s two messages leaves first. MSB first is the convention and is what nearly all gear expects. LSB first exists for the exception its own manual is explicit about — a Nord Drum 2 wants the fine half first, and sent the usual way round it sets Tone Pitch and Echo BPM to a value you did not ask for, with nothing on screen to say so. The two messages are identical either way; only their order moves. This is the value pair. An NRPN key’s parameter pair is a different question with a different answer, and the two must not be confused — which is why they are not one setting. |
| Key graphic | Toggle mode: the Icon (power symbol), a lever Switch — whose axis you pick in the Orientation row below — or Play / pause transport (play when off, pause when on). Sweep mode: Slider draws a live linear gauge and takes the same Orientation row, Knob a rotary knob with a value ring, or Value / Gauge hands the face over to the Display row below. Where the fill STARTS — on the Knob, and on Display’s Bar and Arc gauges — is the Fill from row. (Fixed and Momentary each show their own icon.) |
| Orientation | Which way the graphic runs, vertical or horizontal. Appears under Key graphic for the two graphics that have an axis: the Slider in Sweep mode (the Knob is always round) and the Switch in Toggle mode. A vertical switch flips up for on and down for off; a horizontal one flips right for on and left for off. |
| Fill from | Sweep mode, on the faces that draw a continuous fill: the Knob, and Display’s Value + Bar and Value + Arc. Minimum (default) fills the ring from the low end of the Range — what you want for a volume, a gain, a wah. Centre fills it out from the middle instead, so the ring is empty at the midpoint and grows to the right above it and to the left below — which is how a pan, a balance, or any other control whose middle is the neutral position reads naturally. On Minimum a centred pan draws a half-full ring, which looks like half of something rather than like centred. The pointer tracks the value either way; only the lit part of the ring changes, and nothing about the message sent changes at all. This is the same setting, with the same two choices, as the MIDI Dial’s own Fill from row, so a key and an SD+ dial driving the same pan can be made to match. Keys saved before this row existed fill from the Minimum, exactly as they did. |
| Format | Sweep mode only. Display only — it changes the text drawn in the value slot and nothing else: not the byte on the wire, not the stored setting, and not how often the key repaints. Raw (default) shows the MIDI value 0–127. Percent is relative to this key’s own Range, so a key limited to 20–100 reads 100% at 100 — the number agrees with the full-looking gauge beside it. Pan reads L / C / R from the MIDI centre (64), which is absolute: a restricted range honestly never reaches L50 or R50 rather than pretending to. Approx. dB reads the value as a fraction of full scale (0 dB at 127, about −6 dB at half, -inf at 0) — called approximate on purpose, because without knowing your device’s own taper no single curve is right for every DAW. The value keeps one size. A key picks the size that fits the widest reading its format can produce and stays there, so the text does not grow and shrink as the value moves — a Percent key draws 0% at the same size as 100%, and an Approx. dB key draws -inf at the same size as -42 dB. Raw and Pan are unaffected, because every reading they can produce is short enough to share one size already. |
| Name these values | Print a word instead of a number for the values you list, written as 0:Clean, 5:Crunch, 12:Lead — the same list the Bank action uses for its steps, so one you have already written can be pasted straight in. Separate items with commas or new lines. Anything you do not name still shows its number, so a partial list is fine, and a bare 12 with no name after it names nothing. Display only: the byte on the wire, the stored setting and the repaint rate are unchanged. One size for the whole key — naming any value makes the display pick one size for the longest name you have given, so the text does not jump between sizes as the value moves. A long name therefore makes every number on that key smaller: on the default display a six-letter name such as Crunch draws every value at roughly half the height a plain number would. Past a floor the name itself is shortened with an ellipsis rather than shrinking further. If you want large numbers, keep the names short — or leave the list empty. |
| Display | Sweep mode, Value / Gauge graphic only: Value only, Value + Name, Value + Bar or Value + Arc. These four are shared with the MIDI Readout action, so a Sweep key and a Readout set to the same CC, channel and Range show the same picture — one sends it, the other watches it. (The Readout and the SD+ dial both offer a Level meter, which is not here: it exists for watching a signal arrive, and a key that sends already knows what it sent.) Bar and Arc fill across the Range, so give both keys the same Range or they will disagree. |
| Feedback | Optional MIDI input, shared by every action. For this key, an incoming CC keeps a Toggle's state and light or a Sweep key's value (and its on-key graphic — slider or knob) in sync with the MIDI your DAW sends back. Neural DSP is receive-only, so the source is your DAW's automation (or another controller), not the plugin itself. One virtual port is enough: MIDIRover recognises and discards its own output when a loopback port returns it, so the Feedback input can safely be the port it transmits on. Off by default. |
| Channel | MIDI channel 1–16. |
Recipes
Mute a track, and have the key know when you muted it in the DAW instead
Mode Toggle, the CC Number your DAW learned, and a Feedback port
Without feedback the key only knows what IT sent. With it, the light follows the DAW, so the two cannot disagree.
One key that always sends the same value — a scene recall, a fixed gain
Mode Fixed, Value On set to the value
There is no on/off state to drift. Every press is identical, which is what a recall should be.
Open a filter while you hold the key, closed the moment you let go
Mode Momentary, Value On open, Value Off closed
The release is the point: Toggle would leave it open if you walked away.
Program Change
PCJump straight to a saved preset or tone. Assign one program number per key — the fastest way to switch Neural DSP presets. (In Neural DSP, add a Program Change → Preset mapping for each preset first. In a DAW the host must forward Program Change — Ableton Live doesn't and Logic often doesn't, so the standalone app is the reliable path.)
| Program | The program number to recall (0–127). |
|---|---|
| Bank | Bank Select sent right before the program (coarse CC0 / fine CC32) — for gear whose presets live in banks. Optional to send: leave on “–” to skip it and transmit the Program Change alone. |
| Numbering | Display only — whether the Program dropdown counts from 0 (as MIDI sends) or from 1. Most hardware prints presets one higher than the byte, so pick 1-based if your device shows one more than you sent. The MIDI byte is unchanged. |
| Channel | MIDI channel 1–16. |
| Feedback | Optional MIDI input, shared by every action. For this key it drives an active-preset indicator: the card drawn on the key fills in when its program is the one currently active, and empties when another preset takes over — so a row of preset keys shows at a glance where your rig actually is. A press fills the key too, which means the indicator still works with no input selected: there it shows the last preset MIDIRover sent on that channel — including one sent by a Bank Up or Bank Down key, so stepping through presets with a Bank pair moves the filled card along the row with it. Nothing is filled until a preset is chosen, because before that the current preset is genuinely unknown. |
Recipes
Switch Neural DSP presets from the deck
One key per preset, Program set to its number, Channel matching the plugin
Map each preset to a Program Change in Neural DSP first — the plugin has to be told which program means which preset.
Your gear numbers presets from 1, but the key sends 0
Numbering → counts from 1
MIDI counts from 0 and most hardware prints from 1. This moves only what is PRINTED, so the dropdown matches the display on the unit.
Bank Up / Down
PC / CC stepperClassic preset scrolling, or in Control Change mode step a CC-Absolute value up/down (with wrap). Pair an Up key and a Down key with the same Bank id and channel — they share one counter and both show the current value.
| Output | Program Change (default) sends the classic preset PC. Control Change sends a CC whose value is the stepped counter (0–127) — cycle or nudge a CC-Absolute parameter. A Dec/Inc parameter instead needs a Fixed-value key on each of its inc/dec CCs. |
|---|---|
| CC Number | Control Change output only: the controller sent (0–127). A CC Up/Down pair must share it (as well as Bank id + channel) to move one counter. |
| Channel | MIDI channel 1–16. The step goes out on this channel whichever Output is chosen — a Program Change and a CC are both channel messages, so the same row serves both. |
| Direction | Whether this key steps up (next) or down (previous). |
| From / To | The ends of the range the counter walks (e.g. 0–9). In Program Change mode these are preset numbers, so they show any names you have given those programs (3 · Lead) — the same names the key face prints. In Control Change mode they are values 0–127 rather than presets, so they stay plain numbers. Renaming a preset is done on a Program Change key, where you address one; here you are choosing where the counter stops. |
| Bank id | Keys sharing this id + channel move the same counter. Use different ids for independent banks. It also shows on the key (A ch1) when you have not typed a Name, because it is what tells two independent counters apart — so a Program Change bank keeps showing it even once you have named the presets, and the preset name appears on the value line instead. In Control Change mode a named controller reads Drive A, name and id together, for the same reason. |
| Step | How many to move per press. |
| At ends | Wrap around loops past the end back to the start; Stop at ends clamps. |
| Display | Show the current value on the key, or the name only. |
| Steps | Optional ordered list (value:label, …) replacing From/To — the key shows each step's label; one list item per press (the Step size is ignored in Steps mode, but At ends still wraps/clamps at the list ends). Paste the same list on the paired key. Items the plugin would skip outline the field in red as you type. |
| Feedback | Optional shared MIDI input — with one set, the counter follows the outside world. Change the patch at the gear (or in your DAW) and an incoming Program Change on this channel updates the key's number without it being pressed, so the next press continues from where the device actually is instead of from where MIDIRover last left it. In Control Change mode it follows an incoming CC matching this key's CC number instead. Off by default; without it the counter only knows what it last sent. |
Recipes
Scroll up and down through presets with two keys
Two Bank actions, the same Bank id and Channel, one Direction Up and one Down
The Bank id is what makes them one control rather than two — they share a counter and both show the same number.
Stop at the last preset instead of looping back to the first
At ends → stop
Wrapping suits a short list you cycle; stopping suits a list where the ends mean something.
Note
NoteSend a MIDI note — for parameters that learn to notes, tap-tempo, or triggering things in your DAW.
| Tap Note-on then note-off on each press. | |
|---|---|
| Hold Sounds while the key is held. | |
| Toggle On / off per press — lights while the note is on. | |
| Note On only Lets the note sustain — end it with a Tap on the same note. |
| Note | The note number (0–127), shown with its musical name — 60 · C4 by default. You can rename any note (handy for drums: 36 · Kick), and your names appear on every key that offers a Note list — the MIDI Readout key’s Number list included, though renaming itself lives on the keys that send (see section 6). |
|---|---|
| Chord | Play several notes at once from one key. Leave it empty and the key plays the single Note above — which is what every key does until you type something here. Write the notes separated by commas or spaces, as numbers or as names — 60, 64, 67 or C4, E4, G4, flats like Eb3 included. Whichever you write is what stays: the box does not rewrite names into numbers or numbers into names.Names follow the Naming row above, so C4 means whatever note that row says it means — note 60 by default, note 72 on the Yamaha convention — exactly as the Note dropdown does. Behind the box MIDIRover keeps the note numbers as well, so changing the Naming row later re-labels your chord and never re-tunes it: the pitches stay where you put them and their names follow the convention you are now reading.Add :velocity to strike a voice harder or softer than the rest — 60:100, 64:90, 67, where the bare 67 uses the key’s own Velocity. A velocity above 127 is simply treated as 127; a note out of range is refused, because quietly moving a note you wrote would change the chord. The box turns red when something was dropped — a typo, a repeated note, a half-typed 60: — and the notes it did understand still play. What you typed stays on screen, mistake included, so there is something to find and fix; a box that silently tidied itself would leave you a red border and nothing to correct.Every mode plays chords. In Tap all the notes sound and release together; in Hold they ring until you let go; in Note On only they ring until something else stops them; in Toggle the first press sounds the chord and the second ends it. A Toggle key releases exactly what it latched — so if you change the chord while the key is lit, MIDIRover ends the notes that are actually ringing before the key re-arms on the new ones. |
| Naming | Which octave numbering the note names use — three choices. Middle C = C4 matches Roland gear and most DAWs; Yamaha calls the same note C3; C5 suits a few older sequencers. Display only — the note number sent never changes. This one setting applies to every key, and it also decides how an unnamed Note key labels itself: the same note reads C4 ch1 or C3 ch1 depending on this choice. |
| Velocity / Off velocity | How hard the note is struck (0–127), and the velocity of the message that ends it (default 0 — most gear ignores it, but see Release below, where it is the byte that says “off”). Velocity 0 is a Note Off by MIDI convention, not a very quiet note, so a Toggle key set to it neither lights nor latches: the byte still goes out exactly as configured, and the key does not claim to be holding a note that is not sounding. |
| Release | Which message ends the note. Note Off is the standard one and what every key sent before this row existed. Note On at Off velocity sends a second Note On instead, carrying whatever Off velocity holds. It is for mixing desks, not instruments. An Allen & Heath Qu, GLD or dLive mutes a channel with a Note On and its protocol document states that “Velocity 00 and NOTE OFF messages are ignored” — so a Toggle key built the standard way lights up and un-lights while the desk never moves, with nothing reporting a problem. Mute on and mute off are both Note On there; only the velocity differs. Set a non-zero Off velocity with it. Off velocity defaults to 0, and a Note On at velocity 0 is the conventional Note Off — the very message those desks ignore — so picking this row and changing nothing else sends something the target discards. The panel says so when you do. On an ordinary synth the standard Note Off is the right choice and this row can be left alone. It is one byte, and nothing else. The same note, the same velocity, released both ways: 80 3C 00 is the standard Note Off, 90 3C 00 is a Note On carrying the Off velocity. Only the first byte moves — which is why a desk that ignores Note Off never hears the first one. |
| Minimum hold | Optional, and almost always best left empty. Some gear and hosts IGNORE an off message that arrives within a couple of hundred milliseconds of its on, and go on treating the control as held — Cubase’s Forward is the documented case, at 250 ms. Set a floor in milliseconds and a release sooner than that WAITS until the floor has passed. The message is delayed, never dropped: switching page or letting the deck sleep sends it immediately rather than waiting, so a note can never be left ringing. Momentary only on Control Change, Hold only on Note, and the two snap back press modes on Advanced MIDI — the three places a key sends a second message when you let go. |
| Latch group | Toggle mode only. Give several Toggle keys the same group name and they behave as one switch, like a keyswitch set: pressing one sends Note Off for whichever member was on before sending its own Note On, so only one sounds at a time. Leave blank for independent toggles. Members may sit on different channels and ports — each is released on the channel and port it claimed, not the new key's. A member that was switched on by a previous run of the plugin is cleared without sending anything, because the note it names is no longer this session's to end. |
| Feedback | Optional shared MIDI input — an incoming note-on / note-off matching a Toggle action's note and channel keeps its state and key light in sync (e.g. when your DAW plays the same note). Off by default. |
| Channel | MIDI channel 1–16. |
Recipes
Trigger a drum sample or a clip
Mode Tap, Note set to the pad, Velocity to taste
Tap sends the note on and its off in one press, which is what a sampler expects.
Keyswitch articulations so only one is ever active
Mode Toggle on each key, and the same Latch group name typed on all of them
Pressing one releases whichever was held before it — the group behaves like a row of radio buttons, and the release goes out on the channel that key claimed.
A note that sustains until you press something to end it
Mode Note on only, plus a Tap key on the same note and channel
Note on only deliberately never sends the off. A Panic key nearby is worth having for the times you forget.
Advanced MIDI
AdvancedFor gear that needs more than CC / PC / Note. Pick one message type per key.
| Pitch Bend 0–16383 (8192 = centre, 16383 = full up, 0 = full down). Sent once per press — the bend stays there, unless you pick a snap back press mode, which returns it to 8192 when you let go. The key shows the value it will send, and reads centre at 8192 — so a key that would do nothing audible says so before you press it. | |
|---|---|
| Aftertouch Channel pressure, 0–127 — one value for everything on the channel. For per-note pressure, see Poly Aftertouch below. | |
Poly Aftertouch The same pressure message as above, addressed to one Note number (0–127) instead of to the whole channel — three bytes on A0 rather than two on D0. On a keyboard that is per-key pressure. On a lot of gear the note byte is not a note at all. It is a parameter address, which is the reason this mode exists: an Access Virus reaches an entire half of the synth this way — its Page B parameters have no CC option — and an Allen & Heath GLD selects a mix with it. In those cases Note picks which parameter and Pressure is its value, so take both numbers from the device's MIDI implementation chart rather than thinking of them as pitch and touch. The key prints the note number, not a note name, because that is what those charts print and what the Note row shows. Pressure defaults to 64 and the note to 60. | |
| NRPN 14-bit parameter + value, sent as CC 99 / 98 (which parameter) then CC 6 / 38 (the value). Data Entry decides which of CC 6 and CC 38 actually carries your number, and devices genuinely disagree — there is no safe universal answer, so take it from your gear's MIDI implementation chart. 14-bit — MSB + LSB splits the value across both and runs the full 0–16383. 10-bit — Korg puts the low three bits on CC 63 first and the upper seven on CC 6, running 0–1023 — a minilogue xd sent the ordinary 14-bit shape ignores CC 38 entirely. MSB only sends CC 6 by itself and no CC 38 at all, which is what Novation's synths expect and what Roland states as a family rule for its GS devices. In the LSB holds CC 6 at 0 and puts the value on CC 38, the way an Allen & Heath SQ sends a mute. Increment and Decrement send neither: the parameter pair, then one CC 96 or CC 97 — one nudge per press, which is the only way to reach an SQ mute toggle or a 1 dB trim. They are not offered on a dial, because which one to send depends on which way you turned and a dial reports where it got to rather than which direction it moved. With a fixed LSB is for desks that use CC 38 as a second address byte. Data Entry LSB is that second address byte, and it appears only for the last of those. Your value rides CC 6 and this byte stays where you put it. On an Allen & Heath Qu, Send Level uses it to choose the destination bus and a plain channel fader needs the literal 7 — without it, a key would be addressing a bus rather than setting a level. Getting this wrong is quiet, not loud. A device reading only the MSB sees “no change” for any value under 128 sent as 14-bit, and does nothing at all; there is no error and nothing comes back. If an NRPN key appears to be ignored, this row is the first thing to check. | |
| RPN The same four messages as NRPN on CC 101 / 100 / 6 / 38, but the parameter numbers are fixed by the MIDI specification rather than by the manufacturer — so a Bend Range key means the same thing on every device that answers at all, where an NRPN number means whatever one maker decided. That portability is the reason to prefer it where it fits. Parameter picks one of the five the specification reserves, by name: Bend Range (RPN 0), Fine Tune (1), Coarse Tune (2), Tuning Program (3), Tuning Bank (4). The number in brackets is what your gear's manual prints. The choice decides what the value row means, which is why that row changes its own label. The two data bytes are not one number split in half. This is the whole difference from NRPN, and the place a key goes quietly wrong if you assume otherwise. For Bend Range, CC 6 is whole semitones and CC 38 is cents — two independent fields. Typing 12 sends twelve semitones; a value split 14-bit would have sent “0 semitones, 12 cents”, which is a perfectly legal message leaving the bend range somewhere nobody asked for, with nothing to show for it. Only Fine Tune is a true 14-bit value, centred at 8192. And in practice most gear ignores the second byte entirely — Roland and Yamaha both document it as ignored on Bend Range and Coarse Tune — so the semitone field is the one that does the work. Bend Range is the one most gear implements, and it is the one most people want: it sets how far the pitch wheel reaches. 2 is the usual default, 12 is an octave, and 48 is what MPE controllers use for their per-note channels. The tuning parameters are far less widely supported, and a device that ignores an RPN gives no sign of it — nothing comes back either way. Every press deselects the parameter afterwards (CC 101 / 100 = 127), so a stray Data Entry from something else sharing the port cannot land on it later. | |
SysEx Raw hex bytes — F0/F7 are added automatically if you omit them. Each frame also needs at least one data byte after the manufacturer id: F0 41 F7 is a complete frame by the MIDI specification, but it asks Roland to do nothing, so MIDIRover refuses it rather than putting useless bytes on your cable — the field goes red and the key sends nothing until you add the command bytes. Separate bytes with spaces, commas, periods, colons, semicolons, or dashes; anything the plugin can't parse outlines the field in red and nothing is sent. You can write the message either way — paste the whole string, or pick the maker from the published ID list and type only the command bytes; see SysEx entry below. | |
Transport Start, Continue or Stop — the System Real-Time commands that drive anything slaved to external MIDI clock: a hardware sequencer, groovebox or drum machine, or the Run/Reset gates on a MIDI-to-CV converter. Start rewinds and plays from the beginning; Continue resumes from where Stop left off. Each press sends a single byte (FA / FB / FC) and carries no channel, so the Channel row disappears in this mode. Stop sends only Stop — it does not silence held notes; use the Panic action for that. | |
Song Select Tells a hardware sequencer, drum machine or groovebox to load a song by number — stepping a setlist from labelled keys. It loads the song; it does not start playback, so pair it with a Transport key. Two bytes (F3 plus the number) and no channel, so the Channel row disappears in this mode. Numbering starts at 0 on most gear and at 1 on some — if the wrong song loads, try one either side. The key shows the number it will send; give it a Name and it can read Chorus instead. | |
| Song Position Tells a device already following external MIDI clock WHERE in the song to sit — a locate, not a transport command. The number counts MIDI beats, which are sixteenth notes from the start of the song, so in 4/4 bar 5 is beat 64 and bar 2 is beat 16. Pair it with a Transport → Continue key: Song Position moves the playhead, Continue starts it from there. It needs a clock master that is not MIDIRover. This plugin deliberately does not generate MIDI clock — a Stream Deck plugin cannot hold the timing a clock needs — so this is for decks working alongside a DAW or hardware sequencer that owns the tempo. On its own it will move a playhead and nothing will run. Three things decide whether a device responds at all. It needs a timeline to locate on — a sequencer, groovebox, drum machine or DAW. A synth without a sequencer, an amp modeller or an effects unit has nothing to cue, and will ignore the message entirely. It usually needs to be switched to external MIDI sync first; many devices accept the message and do nothing visible until that is on. And by long-standing convention it should be stopped when the message arrives: you locate, then send Transport → Continue to roll from there. Start always returns to the beginning and discards the position. Expect a running device to ignore it, silently. Novation’s SL MkIII and Korg’s ESX-1 both state that a Song Position arriving during playback is ignored, and Apple notes it is “not normally sent in playback mode”, offering an opt-in setting to send it anyway. This is settled practice rather than something we can quote from the MIDI Manufacturers Association’s own text, so treat it as what gear does, not as what the specification demands. The limits are in the message, not in us. The count is a 14-bit number of sixteenths, so the finest you can cue to is a sixteenth note — 125 ms at 120 BPM, with triplets and anything off the grid simply not expressible — and the furthest you can reach is 16383, which is 1024 bars of 4/4, about 34 minutes at 120 BPM or 17 at 240. Past that the key cannot address the position at all. | |
Tune Request Asks analog synths to retune their oscillators — one byte (F6), no channel, and nothing to configure, so this mode has no settings of its own. Digital gear and plugins ignore it, so it does nothing on a Neural DSP rig; it is here for hardware that drifts as it warms up. |
| Press mode | Pitch Bend, Aftertouch, Poly Aftertouch and NRPN — the four types with a value to ride or return to. Four behaviours, as a press and a release: Send one value (default) is the original — one press, one value, and it stays there. Send one value, snap back adds the return: the value goes back to its resting point the moment you let go — centre (8192) for Pitch Bend, 0 for Aftertouch, Poly Aftertouch and NRPN — which is the stab or dive that used to need a second key at 8192. Ride while held sweeps it for as long as you hold the key and bounces at the ends rather than stopping, so you can come back down without letting go. It starts where the control rests — Pitch Bend at 8192 (centre), Aftertouch, Poly Aftertouch and NRPN at 0 — and, on release, stays where you stopped — the next hold carries on from there. The key sends about 33 values a second while held, and the wave on the face fills to show how far along the travel you are. This is the keyboard equivalent of the MIDI Dial's Pitch Bend mode, for decks without dials. |
|---|---|
| Ride time | Riding modes only (Ride while held, with or without snap back): the seconds for one end-to-end pass, a whole number from 1 to 60 (default 3). A longer time means smaller steps per tick, not a longer hold — the ride bounces and keeps going for as long as the key is down. |
| Minimum hold | Optional, and almost always best left empty. Some gear IGNORES a value that returns within a couple of hundred milliseconds of leaving, and goes on reading the control as held. Set a floor in milliseconds and a snap-back sooner than that WAITS until the floor has passed. The message is delayed, never dropped: switching page sends it immediately rather than waiting, so a bend can never be left stranded off centre. The two snap back press modes only. |
| Note | Poly Aftertouch only: the note number the pressure is addressed to, 0–127 (default 60). On a keyboard this is the key being pressed. On a great deal of other gear it is not a note at all but a parameter address — an Access Virus selects its Page B parameters this way and an Allen & Heath GLD picks a mix — so read it off the device’s MIDI implementation chart alongside the value that goes in Pressure. It is a plain number here, and the key face prints the same number, deliberately: those charts print numbers, and the shared note names you can set elsewhere in MIDIRover are a musical vocabulary that would be misleading on a parameter address. Use the key’s own Name row to call it Mix 5. |
| Data Entry | NRPN only: which of CC 6 and CC 38 carries your value. Devices genuinely disagree and there is no safe universal answer, so take it from your gear’s MIDI implementation chart. 14-bit — MSB + LSB splits the value across both and runs the full 0–16383. MSB only sends CC 6 by itself and no CC 38 at all, which is what Novation’s synths expect and what Roland states as a family rule for its GS devices. In the LSB holds CC 6 at 0 and puts the value on CC 38, the way an Allen & Heath SQ sends a mute. Increment and Decrement send neither: the parameter pair, then one CC 96 or CC 97 — one nudge per press, which is the only way to reach an SQ mute toggle or a 1 dB trim. They are not offered on a dial, because which one to send depends on which way you turned and a dial reports where it got to rather than which direction it moved. With a fixed LSB is for desks that use CC 38 as a second address byte. Getting this wrong is quiet, not loud. A device reading only the MSB sees “no change” for any value under 128 sent as 14-bit, and does nothing at all — no error, nothing back. If an NRPN key seems ignored, check this row first. 10-bit — Korg is a fourth shape again: Korg’s own manual asks for the low three bits on CC 63 first, then the upper seven on CC 6, giving a 0–1023 value — a minilogue xd sent the ordinary 14-bit shape ignores CC 38 entirely, so fine resolution is simply unreachable. |
| Data Entry LSB | Only with Data Entry: with a fixed LSB. A second address byte rather than a value, 0–127: your number rides CC 6 and this byte stays where you put it. On an Allen & Heath Qu, Send Level uses CC 38 to choose the destination bus — 0–6 for Mix 1–9/10, 8–11 for groups, 16–19 for FX sends — and a plain channel fader needs the literal 7. Without it a key would be addressing a bus rather than setting a level. |
| Data byte | Shown only for Increment and Decrement, and it is not a quantity. Those two shapes send the parameter pair and then a single CC 96 or CC 97 instead of a value — one nudge per press — and this byte tells the device what a nudge means. On an Allen & Heath SQ, 0 is one step: +1 dB on a level, one position on pan, or a toggle on a mute or mix assign — none of which any absolute message can reach, which is why these shapes exist. 127 is different in kind: the SQ protocol defines it as a read-back request, so the desk replies with the current value instead of moving. The panel says so when you type it. Other gear reads the byte differently again — a Yamaha S70XS applies it to the selected parameter's coarse half, and the MIDI spec's own recommendation makes the step depend on which parameter you picked. Take it from the chart. |
| Parameter MSB | NRPN only, and the same address as Parameter written the way most MIDI charts print it. CC 99 and CC 98 are the two bytes of that 0–16383 number, so these two boxes are a second view of it rather than a second setting — type either notation and the other follows, and nothing extra is stored. Use them when your chart gives two numbers. Allen & Heath is the clearest case: on a Qu or GLD, CC 99 carries the mixer channel and CC 98 the parameter ID, so they are not halves of one quantity and adding them into a single figure is arithmetic you should not have to do in your head — a slip of one addresses a different object, silently. Yamaha XG puts a drum note number in the LSB for a whole block of parameters, and Korg's minilogue xd table prints -- for every MSB, meaning zero. Both boxes stay empty until the parameter is set, so a key that never chose an address still says so in amber rather than looking like it chose 0. |
| Parameter LSB | The low half of the same address — sent as CC 98. See Parameter MSB above: the two together are the one Parameter number in the notation your chart uses, and a blank half counts as zero. |
| SysEx entry | SysEx mode only: how you want to write the message. Paste hex (default) gives you the single SysEx (hex) box — type or paste a string from your gear's manual, exactly as before. Build message swaps that box for four rows — Start byte, Manufacturer, Command bytes, End byte — so reading down the panel is reading the message in order. The first and last hold the F0 and F7 the MIDI specification fixes: they are shown so nothing looks missing, and they are labels rather than fields, because an F7 you could type would let a message end twice.Your message carries across both ways, and only one set of fields is ever on screen. Switching to Build message reads whatever is already in the box and fills the two fields from it; switching back shows the string those fields built. Either way there is one message stored — the builder is a way of writing it, not a second setting — so the red outline, the Sends line and the Bytes line all behave identically in both modes, and a key made before this row existed opens in Paste hex with its string untouched. If you paste something the panel cannot split — a manufacturer it does not recognise, or bytes it cannot read — Build message leaves Manufacturer blank and puts every byte into Command bytes. Nothing is dropped: you can still see and edit the whole message, and switch back to Paste hex to have it as one line again. |
| Manufacturer | Build message only: whose registered ID follows the opening F0. Choosing a company writes it into your message straight away — there is nothing to press, and nothing extra is stored. The two fields are two halves of the one string the key sends, which is why switching modes never loses anything.You must pick one. Until you do, the key sends nothing — and that is a deliberate refusal rather than a gap. The manufacturer's place in a SysEx message is simply the byte after F0, so building a message without one would slide your first command byte into that slot: type 41 10 with nobody selected and you would have addressed Roland, without choosing to. MIDIRover builds nothing instead. A message has exactly one manufacturer, so picking a second company replaces the first rather than adding to it. The Bytes line under Sends shows which bytes were read as the manufacturer, and names the company back to you — most IDs are one byte, but an ID that begins 00 is three, and that is the kind of thing worth seeing confirmed. That length is decided by the bytes themselves, not by whether the company is on the list: paste an ID nobody has registered and the line still shows the right three bytes, simply with no name beside them.The list is the MIDI Association's published Manufacturer SysEx ID table, snapshotted 5 October 2026, and shipped as published. It carried one correction until that date — the table printed Sonicware's ID as 00 48 00, which already belongs to sigboost, and MIDIRover shipped the real 00 48 04 instead, because two companies sharing one entry is something a dropdown cannot express. The MIDI Association has since fixed the page, so that value now comes from the source itself and the correction is gone. If your gear is not on it, switch to Paste hex and type the bytes from its manual — and note that Build message will refuse to open a message whose manufacturer it cannot show you, for the same reason: it has nowhere to put those bytes, so it would lose them — plenty of well-known instruments have no ID of their own, and several ship under a parent company: Boss under Roland, Nord under Clavia, Strymon under Damage Control Engineering, Line 6 under Line 6 (Fast Forward) (Yamaha). The three Universal entries at the end are not manufacturers at all — they are reserved by the MIDI specification, and 7E is what the GM System On message in the placeholder uses. |
| Command bytes | Build message only: everything between the manufacturer ID and the closing F7 — the part that actually says what to do, taken from your device's MIDI implementation chart. Separate bytes with spaces, commas, periods, colons, semicolons or dashes, exactly as in the SysEx (hex) box.It cannot be empty. A frame with a manufacturer and nothing after it — F0 41 F7 — is a complete message by the MIDI specification, but it asks Roland to do nothing, so MIDIRover refuses it: the field goes red and the key sends nothing until you add at least one byte.Every byte here is data, so each one must be 00–7F. F0 and F7 belong to the frame rather than to you: they are shown beside the fields instead of being typed, which is what stops a message from ending twice. |
| Display | What the key draws, beside its message glyph. Value + Name (default) shows both — the number this key will send, above, and the key’s Name, below. Value only drops the name, Name only drops the number, and None leaves the glyph by itself, which is worth it when a printed legend, or simply where the key sits, already says what it does. A key set to ride still fills as you hold it, so hiding the value loses the number and not the movement. SysEx, Transport and Tune Request send no single value, so for those three the list offers only Name only and None. Song Select does have one — the song number — so it keeps the full list. Note also that none of those four messages carries a channel, so an unnamed key of those types has no Bend ch1-style fallback to draw — a Song Select key still shows its number, but the others are wordless whichever you pick, and the setting starts doing something once you type a Name. The Stream Deck app’s own Title is a separate field, and hiding the name here cannot clear it: if you have set both, you will still see the app’s. |
| Channel | MIDI channel 1–16 — and it matters to only five of the Types. Pitch Bend, Aftertouch, Poly Aftertouch, NRPN and RPN are channel messages and go out on this channel. SysEx carries its own addressing inside the message, and Transport, Song Select, Song Position and Tune Request are channel-less by definition — so on those five the row is not shown at all. |
| Song position | Song Position mode only: where in the song to jump to, counted in MIDI beats — sixteenth notes from the start — from 0 to 16383 (default 0). In 4/4 that is sixteen to the bar, so bar 5 is 64 and bar 17 is 256. Other time signatures count the same sixteenths, so the bar arithmetic is yours rather than the protocol's: MIDI carries no time signature. 0 is a real position — the top of the song — not an 'unset' placeholder, which is why this row warns about nothing when you leave it alone. |
| Semitones | RPN mode only: the value, in the units the chosen parameter is defined in. For Bend Range that is whole semitones — 2 is the usual default, 12 is an octave, and 48 is what MPE controllers use. For Coarse Tune it is semitones with 64 as centre. For the two tuning rows the label changes to Program or Bank and it is a plain number, 0—127. For Fine Tune the label changes to Value and the range becomes 0—16383, centred at 8192 — the only one of the five that is a 14-bit number. Leave it empty and the key sends that parameter's 'unchanged' value — 2 semitones, 8192, or 64 — rather than zero. Zero is a real setting for most of these and a destructive one for some: coarse tune 0 is 64 semitones flat. This is NOT one 14-bit number split in half. Typing 12 for Bend Range sends twelve semitones, not a value whose halves happen to be 0 and 12. |
| Cents | RPN mode only, and only for Bend Range: a fine adjustment on top of the semitones, 0—100 (default 0). It is sent as a separate data byte, not as the lower half of the semitone number — the two are independent fields. Most gear ignores it. The MIDI specification defines this byte as cents, and MIDIRover sends it — but Roland (JD-Xi, XV-5080) and Yamaha (XG) all document the second data byte as ignored on Bend Range, and the same for Coarse Tune. So expect your bend range in whole semitones and treat a finer response as a bonus. The field is kept because the specification defines it and a device may honour it; what changed here is the promise, not the bytes. A related device limit worth knowing: Roland's JV-1010 accepts a bend range of 0–12 semitones rather than the 0–24 some gear allows, so a value this key accepts may still be clamped at the other end. It stops at 100, not 127. A device that does not implement cents is expected to have carried into the semitone count by the time cents reach 100, so the numbers above that have no agreed meaning and the field will not accept them. The row is hidden for the other four parameters, which have no second field at all. |
| Deselect after | NRPN and RPN only — the two types that leave a selection standing in the receiver; every other type is self-contained and the row is hidden for them. After the press finishes, the key closes the transaction with a Null — CC 101 = 127, CC 100 = 127 — which says that no parameter is selected any more. Without it the selection stands, and a stray Data Entry (CC 6 or CC 38) from a DAW, another controller, or one of your own keys pointed at those numbers lands on the parameter you just set. One Null serves both, which surprises people who know the controller numbers: it rides the RPN pair even for an NRPN, because Roland and Yamaha both document that pair as clearing RPN and NRPN together, and neither defines any Null on CC 99 / 98. On by default, since both recommend sending it. Switch it Off for gear that uses CC 100 and CC 101 for something else — some Waldorf synths map them to sound parameters, where the Null edits the patch rather than closing anything. The Sends line drops from six messages to four when you do, so you can see the change before you press. The same row is on the MIDI Dial in NRPN mode. |
| Song number | Song Select mode only: which song to load, 0—127 (default 0). 0 is a real song on gear that numbers from zero, not an 'unset' placeholder, which is why a key left at 0 sends song 0 rather than warning you. Out-of-range numbers are clamped and the Sends line says so. Gear differs in whether its DISPLAY starts at 0 or at 1, and this field is the number on the wire: a sequencer that shows its songs starting at 1 wants 7 here for the one it calls 8, while one that shows them starting at 0 wants 8. If the wrong song loads, try one either side. |
| Command | Transport mode only: which System Real-Time command this key sends — Start, Continue or Stop. Each is a complete one-byte message, so this key has no Channel. |
Recipes
Bend the pitch while the key is held
Type Pitch Bend, Press mode → Ride while held
It climbs from centre while held. On release it stays where you stopped rather than snapping back, so the next hold carries on from there.
Tell a recorder or DAW to play, stop or punch in
Type SysEx, paste F0 7F 7F 06 02 F7 for Play
MMC is SysEx with a reserved manufacturer id, so it needs no action of its own. The MMC guide lists every command as a paste-ready line.
Start and stop a drum machine or sequencer
Type Transport, then Start / Continue / Stop
These are single bytes with no channel — everything slaved to the same clock hears them at once.
MIDI Dial
Models with dials (Stream Deck + / + XL)Ride a parameter by hand — gain, mix, wah — on a rotary dial. The touch strip shows the name and the live value as a bar or a rotary knob. (The dial actions appear on any model with dials; the Stream Deck + and + XL are the two Elgato documents with a touch strip to display the value on.)
| CC Number | The controller the dial sweeps (0–127). |
|---|---|
| Turn mode | Absolute (default) sends the 0–127 value the dial rides. Pitch Bend sends the pitch wheel instead of a CC, so there is no controller number — it is one wheel per channel, and the CC Number row goes away. Its scale is 14-bit: Range runs 0–16383 and a press rests at 8192, the centre, rather than at the bottom. Step defaults to 128, which is one 7-bit unit, so it feels like a CC dial while the wire carries the finer resolution — type a smaller Step to use it. Values print as plain numbers for now, and a bend dial does not yet follow an incoming bend. NRPN addresses a numbered parameter rather than a CC, on the same 14-bit scale and with the same 128 default Step; it hides the CC Number row too and adds NRPN Parameter. One NRPN value costs three or four MIDI messages depending on that row — MSB only sends three — so while you spin, the dial sends at most one set every 30 ms and skips the values in between — where you stop is always sent. An NRPN dial does not yet follow an incoming NRPN. Relative sends +/− deltas for an endless encoder, so a DAW parameter never jumps on pickup — Range / Reset / Display and feedback don't apply, and the touch strip reports what the control IS and what it just SENT rather than a position it cannot know: the name (or the address) and what one detent sends — then the moment you turn it, the signed amount that went out, with the direction lit. It settles back after about a second. There is deliberately no value and no gauge: a relative dial has none, and a number with a scale behind it would imply a range MIDIRover cannot see. Program Change browses presets rather than riding a value, so it is the one mode that sends an identifier instead of a magnitude. A detent moves one preset — one entry of your Steps list, or one program number when that list is empty — and the message leaves about half a second after you stop turning rather than on every detent, because a preset change makes most gear reload a patch: spin through twenty and your rig changes once, at the one you landed on. The rows that answer questions a preset does not have go with the mode — Step / tick, Reset to, Format, Name these values and the whole Key graphic choice, since the strip draws a cursor at your position in the list instead of a gauge filling from a range. It does not follow an incoming message either: a preset number is not a CC value. The two setup caveats are the ones a Program Change key has: the host must forward Program Change (Ableton Live does not; Logic often does not), and in Neural DSP each program number needs its own Program Change → Preset mapping. |
| Encoding | Relative mode only: Signed bit, Two's complement, or Binary offset — match your DAW's relative-CC mode (Ableton / Reaper / Bitwig / Cubase all list these). |
| NRPN Parameter | NRPN mode only: the parameter number the dial writes to, 0–16383 — take it from your gear's MIDI chart. It is not a CC number, and it is sent with every value (as CC 99 and 98) so that nothing else sharing the port can leave the dial writing to the wrong parameter. Leave it unset and the dial addresses parameter 0, which is a real parameter on plenty of gear — the panel says so in amber. A dial with no Name of its own prints this number in its title, as NRPN1002 ch1, so two dials on neighbouring parameters are not the same picture. On a key the same message reads 1002 ch1 without the word: a key’s hash glyph already says NRPN, and a dial has no glyph that does. Take the number off the chart rather than trying numbers to see what moves. On some gear a parameter you did not mean is not harmlessly ignored: Waldorf's Blofeld maps most of the controller numbers this mechanism uses onto ordinary patch parameters, so a stray NRPN edits the sound, and Allen & Heath document a Remote Shutdown on the Qu at parameter 95 that needs a hard power reset to undo. Neither is a reason to avoid NRPN — both are the reason to look the number up. |
| Parameter MSB | NRPN only, and the same address as Parameter written the way most MIDI charts print it. CC 99 and CC 98 are the two bytes of that 0–16383 number, so these two boxes are a second view of it rather than a second setting — type either notation and the other follows, and nothing extra is stored. Use them when your chart gives two numbers. Allen & Heath is the clearest case: on a Qu or GLD, CC 99 carries the mixer channel and CC 98 the parameter ID, so they are not halves of one quantity and adding them into a single figure is arithmetic you should not have to do in your head — a slip of one addresses a different object, silently. Yamaha XG puts a drum note number in the LSB for a whole block of parameters, and Korg's minilogue xd table prints -- for every MSB, meaning zero. Both boxes stay empty until the parameter is set, so a key that never chose an address still says so in amber rather than looking like it chose 0. |
| Parameter LSB | The low half of the same address — sent as CC 98. See Parameter MSB above: the two together are the one Parameter number in the notation your chart uses, and a blank half counts as zero. |
| Data Entry | NRPN mode only: which of CC 6 and CC 38 carries your value. Devices genuinely disagree and there is no safe universal answer, so take it from your gear's MIDI implementation chart rather than trying them to see what moves. 14-bit — MSB + LSB splits the value across both, and runs the full 0–16383. MSB only sends CC 6 by itself and no CC 38 at all — what Novation's synths expect, and what Roland states as a family rule for its GS devices. In the LSB holds CC 6 at 0 and puts the value on CC 38, which is how an Allen & Heath SQ sends a mute. With a fixed LSB is for desks that use CC 38 as a second address byte — see the row below. Switching to one of the three single-byte shapes narrows the value to 0–127; 10-bit — Korg narrows it to 0–1023. 10-bit — Korg is a fourth shape again: Korg’s own manual asks for the low three bits on CC 63 first, then the upper seven on CC 6, giving a 0–1023 value — a minilogue xd sent the ordinary 14-bit shape ignores CC 38 entirely, so fine resolution is simply unreachable. |
| Data Entry LSB | Only with Data Entry: with a fixed LSB. A second address byte, not a value: your number rides CC 6 and this byte stays where you put it, 0–127. On an Allen & Heath Qu, Send Level uses CC 38 to choose the destination bus — 0–6 for Mix 1–9/10, 8–11 for groups, 16–19 for FX sends — and a plain channel fader needs the literal 7. Without this setting a ride would sweep the destination rather than the level, landing on a different bus on nearly every step. |
| Deselect after | NRPN mode only, and the same setting the Advanced MIDI key carries. About half a second after you stop turning, the dial closes the transaction with a Null — CC 101 = 127, CC 100 = 127 — which tells the receiver that no parameter is selected any more. Without it the selection stands, and a stray Data Entry (CC 6 or CC 38) from a DAW, another controller, or one of your own Control Change keys pointed at those numbers would land on the parameter you just set instead of doing what it says on the tin. On by default, because Roland and Yamaha both recommend sending it in the same documents that define it. Switch it Off for gear that uses CC 100 and CC 101 for something else — some Waldorf synths map them to sound parameters, so there the Null edits the patch rather than closing anything. With it off the transaction simply stays open; nothing else about the turn changes. |
| Steps | Program Change mode only, and the same list grammar as Bank Up / Down's Steps: the presets this dial walks, as number:name separated by commas — 3:Clean, 17:Crunch, 42:Lead. Four entries means four detents end to end rather than eighty-five, and the touch strip shows the name you typed in place of the number — a preset is something you recognise by name. A preset you have not named here falls back to the shared program name map, and then to its number, so naming your patches once names them on every dial and Program Change key at once. Leave it empty to step the Range below instead; if nothing in the list is a number the dial falls back to that range and says so under Sends.Hold the dial in while you turn to move four presets a detent — the same coarse gesture every turn mode has, described on Step / tick for the modes that have one. Program Change has no Step row, so this is where it is written down: it moves four entries along your list, or four program numbers when the list is empty. With At ends on Stop a held turn that would overshoot lands on the end rather than being refused, so the last preset is always reachable while holding. |
| Bank | Program Change mode only, and the same setting the Program Change key carries: Bank Select sent right before the program (coarse CC 0 / fine CC 32), for gear whose presets live in banks. MIDI has only 128 program numbers, so gear with more groups them into banks and you cannot reach past the first 128 without this. Optional — leave either on “–” to skip it and send the Program Change alone. |
| At ends | Program Change mode only: what a spin does at the first or last preset. Stop at ends (default here, where a Bank key defaults to wrapping) holds there and sends nothing further — a Program Change reloads a patch, so re-sending the one you are already on is not free. It stops at the end rather than before it: a coarse turn (holding the dial in) that would carry you past the last preset lands on it. Wrap around continues from the other end. |
| Resolution | Absolute mode only, and only for CC 0–31. Normally a Control Change carries one 7-bit byte, so a dial has 128 positions — enough for most things, and audible as a zipper on a slow filter sweep. Resolution sends the value as a pair instead: the coarse half on your CC and the fine half 32 controllers above it, so CC 20 is joined by CC 52. That is the pairing the MIDI specification defines, which is why the row disappears above CC 31 — there the second controller is simply unrelated. The setting is kept rather than cleared, so moving back to a controller that can pair restores the width you chose — and while it cannot apply, the key says so in its own notes instead of leaving you to wonder. Your gear has to agree, and this is the whole risk. On a device that does not implement the pairing the fine half is not ignored: it moves whatever that controller does. So leave this on Standard unless your MIDI implementation chart says the parameter is high-resolution. Neural DSP does not pair, so leave it alone there. Two widths, because gear differs. 14-bit is the common one and gives 16,384 steps. 8-bit gives 256 and is what Novation's wide parameters use on the Peak and Summit — on those synths every high-resolution parameter is a CC pair rather than an NRPN. Picking the wrong width still addresses the right controller; it just sends a value your gear reads as too large or too small. Switching this on widens Range and Step to match. Numbers you type at this width are kept if the dial is narrowed again — by moving the CC above 31, or switching Turn mode — rather than being trimmed: the box turns red to say the dial cannot send that value as it stands. The dial still follows Feedback: MIDIRover reassembles an incoming pair, so a device moving the parameter at full resolution moves the dial with it. It waits up to 50 ms for the second half, and a device that sends only the coarse half leaves the dial where it is rather than jumping to a value 128 times too small. |
| Pair order | Shown once Resolution leaves Standard: which of the pair’s two messages leaves first. MSB first is the convention and is what nearly all gear expects. LSB first exists for the exception its own manual is explicit about — a Nord Drum 2 wants the fine half first, and sent the usual way round it sets Tone Pitch and Echo BPM to a value you did not ask for, with nothing on screen to say so. The two messages are identical either way; only their order moves. This is the value pair. An NRPN key’s parameter pair is a different question with a different answer, and the two must not be confused — which is why they are not one setting. |
| Step / tick | How much the value changes per detent. Hold the dial while turning for coarse steps (×4). On a Resolution pair it defaults to one 7-bit unit of the wider axis — 128 on a 14-bit dial, 2 on an 8-bit one — so the dial feels the same as a plain CC dial while the wire carries the finer value. |
| Reset to | Press and release the dial (without turning) or tap the screen to jump to this value (clamped into Range). Holding while turning gives coarse steps and never resets. Relative and Program Change have no Reset row at all, and a press on either sends nothing: a relative dial has no position to return to, and a preset is somewhere you already are. |
| Range | Limit the sweep to a min–max span (default 0–127) — e.g. keep a wah between 20 and 100. The touch strip display follows the range. |
| Format | Absolute mode only — a relative dial has no absolute value to describe. Display only — it changes the text drawn in the value slot and nothing else: not the byte on the wire, not the stored setting, and not how often the key repaints. Raw (default) shows the MIDI value 0–127. Percent is relative to this key’s own Range, so a key limited to 20–100 reads 100% at 100 — the number agrees with the full-looking gauge beside it. Pan reads L / C / R from the MIDI centre (64), which is absolute: a restricted range honestly never reaches L50 or R50 rather than pretending to. Approx. dB reads the value as a fraction of full scale (0 dB at 127, about −6 dB at half, -inf at 0) — called approximate on purpose, because without knowing your device’s own taper no single curve is right for every DAW. |
| Name these values | Print a word instead of a number for the values you list, written as 0:Clean, 5:Crunch, 12:Lead — the same list the Bank action uses for its steps, so one you have already written can be pasted straight in. Separate items with commas or new lines. Anything you do not name still shows its number, so a partial list is fine, and a bare 12 with no name after it names nothing. Display only: the byte on the wire, the stored setting and the repaint rate are unchanged. Absolute 7-bit dials only, for the same reason the Format row is: a 14-bit dial runs to 16383 while this list only reaches 127, so it would name the bottom of the sweep and silently stop. |
| Key graphic | Bar (default), Knob (a rotary knob — where its ring starts is the Fill from row below), or Level meter. NRPN mode offers the first two but not the Level meter: its twelve segments exist to economise on repaints from incoming MIDI, which an NRPN dial never receives, and to divide 128 values into steps you can see — at 0–16383 one segment covers 1,365 values, so it would be twelve near-identical pictures printing no number. A dial saved as a meter before you switched it to NRPN quietly becomes a Bar, so the strip and this row never disagree. Program Change mode offers none of them and hides this row: all three fill from the value, and a preset number is a name for a patch rather than an amount of anything — with presets 59 and 43 in your Steps list, a filling bar would move BACKWARDS as you browsed forward. That mode draws its own face instead, with the preset’s name above it: a lit segment that takes one preset’s share of the track and moves one share per detent — half the bar with two presets in your list, a third with three, a sixth with six — so the face says which preset of how many before you have counted anything, and the last one ends flush with the right-hand end. With no Steps list there are 128 stops and a share would be barely a pixel, so there the segment keeps a readable size and slides the length of the track instead. A dial already set to Knob or Level meter keeps that choice for the other modes — it simply does not use it here. Level meter draws twelve segments across the Range, fed by incoming MIDI — the same segments, and the same twelve steps, as the MIDI Readout’s meter face, so a dial and a key watching one CC always light the same count. It shows no number, because it repaints only when the lit count changes and a number would sit a moment behind the signal; Bar and Knob are the displays that print a value. Turning the dial still sends as usual. Not available in Relative CC mode, which does not follow feedback at all. Unlike the key’s meter, a MIDI Dial does not show clipping: a dial stores the value it is sitting on, and that value is held inside the Range so that turning it continues from where it is — so by the time the face is drawn, a value above the Range has already become the top of it. That is a property of this action, not of the hardware: a MIDI Readout meter stores nothing and clamps nothing, so it does show clipping — on a key or on a dial. Put one on the same CC if you need to see it. |
| Fill from | Knob only. Minimum (default) fills the ring from the low end of the Range — what you want for a volume, a gain, a wah. Centre fills it out from the middle instead, right of twelve o’clock above the midpoint and left below, which is how a pan or any other bipolar control reads naturally. The pointer tracks the value either way; only the lit part of the ring changes. This was two entries in the Key graphic list until it became its own row, because one dropdown was answering two different questions — which face to draw, and where its ring begins. Keys made before the change keep the look they had. |
| Display | Value + Name (default) keeps the name on the touch strip, above the value — what every dial has drawn until now. Value only drops it and hands the whole strip to the face: the Knob grows noticeably wider, and the Bar and Level meter move up to sit on the middle of the strip rather than hanging below an empty title row. Worth it when a printed legend, or simply where the dial sits under your hand, already says what it rides. The row survives into Program Change, where none of those three faces does: drop the name there and the preset cursor recentres on the strip the same way. A Level meter prints no number, so on that face Value only honestly means the segments alone. The option names describe what the strip shows — and two of the three faces do print a value. Not offered in Relative CC mode. That face is a single line of text which falls back to the CC address when it has nothing recent to report, so hiding the name there would empty it rather than free a row. Dials made before this row existed keep their name: the default is Value + Name, and nothing on an existing key changes until you pick the other one. |
| Feedback | Optional shared MIDI input — an incoming CC matching this dial moves its value and touch strip display (e.g. when the DAW automates the parameter). Off by default. Absolute dials only. A Relative dial has no absolute value to be moved to; Pitch Bend and NRPN are 14-bit and the match is by controller number, which neither of them has; and a Program Change dial holds a preset number, which is not a CC value — so none of those four follow the port, whatever it carries. |
| Channel | MIDI channel 1–16. |
Recipes
A gain knob that does not jump when you first touch it
Encoding → a relative mode, and set the receiving plugin to the matching relative mode
Absolute sends where the dial thinks it is; relative sends which way you turned. Relative cannot jump, because it never states a position.
Push the dial to put a parameter back to its default
Reset to → the default value
The press is otherwise unused on a dial, and a reset is the thing most often wanted.
Read a mix control as a percentage rather than 0–127
Format → percent
Only the display changes; the wire still carries the MIDI value, so nothing downstream has to agree with you.
Panic
All notes offOne press clears a stuck note or hung sustain — it sends All Sound Off (CC120), All Notes Off (CC123) and Reset All Controllers (CC121). Especially handy next to Note keys set to Note On only / Hold / sustain, which don't release on their own.
| Send on | All channels (default, all 16), a single channel 1–16, or Selected channels… to list your own. |
|---|---|
| Channels | Only with Selected channels…: the channels to reset, as numbers and ranges — 2, 5, 9-12. The line underneath names exactly what will be reset as you type. Use it to spare a channel that must keep running, like a looper. If nothing in the box can be read as a channel, Panic resets all 16 rather than nothing — the whole point of the key is that it works when you need it. Numbers outside 1–16 are ignored, not rounded, so a mistyped 0 or 17 never resets a channel you did not ask for. |
| MIDI Port | Where the reset is sent. Panic reaches one port — this key’s own, or the shared port when it is left on Auto-detect. A note sounding on a different port is not silenced by it, because MIDIRover holds one output port at a time: opening this one closes that one. With every key on Auto-detect or a single shared port — the default, and much the commonest setup — one Panic key covers the whole deck. If you deliberately split keys across two ports, give Panic the port whose notes you need it to stop, or place a second Panic key set to the other one. |
Recipes
A note is stuck on and nothing will stop it
Drop a Panic key on the deck and press it
It sends All Sound Off (CC 120), All Notes Off (CC 123) and Reset All Controllers (CC 121) — between them these end almost every hung note.
Clear only the channel you are playing, not the whole rig
Channels → the one channel
A deck-wide panic on a multi-instrument rig stops things you did not mean to stop.
MIDI Readout
Display onlyA key that only shows a value — it never sends MIDI. Point Watch at the message you want to see and the key displays it live: a patch number, a fader position, a meter. It needs a Feedback port, and software that actually sends MIDI — Neural DSP plugins are receive-only, so use your DAW's automation or another controller. Until the first message arrives the key shows what it is waiting for (e.g. CC22 ch2), and it says Feedback off if no input is selected — so a blank-looking key always tells you which of the two to fix. There is a third message: if the port you picked later disappears (loopMIDI closed, an interface unplugged, the DAW quit) the key says Port lost, which is deliberately not the same words — one asks you to choose a port, the other to bring one back. When the port returns the key picks up again by itself. Note what is not a problem: a face that keeps showing its last value while nothing arrives is working correctly. A Control Change is a position rather than a stream, so a fader that has stopped moving sends nothing and the last value is still the truth. The Peak hold marker is the deliberate exception — it measures how high the signal reached RECENTLY, which does age, so it falls on its own while the value stays put. One more case that looks like a fault and is not: restarting the plugin clears every reading. If the Stream Deck app restarts, or the plugin updates or recovers from a crash, each watching key goes back to a dash until its next message — it has genuinely heard nothing yet, and a Control Change sender does not resend on its own. Move the fader (or send anything on the address) and the key fills again. A small RX in the top-left corner marks the key as a watcher rather than a sender, because the sending keys name themselves the same way — without it a Readout and a Control Change key on the same address would look identical.
It also runs on a Stream Deck + dial, drawn on the 200×100 touch strip instead of a key. There Key graphic offers four faces rather than five — Value only, Value + Name, Level meter and Needle — because Value + Bar and Value + Arc have no dial form, while Needle is the one face a key cannot draw; your choice is kept if you move the action between a key and a dial. The Name font-size box is hidden there, since the dial faces draw their title at a fixed size. Pushing or touching the dial clears the peak marker and does nothing else: a Readout never transmits, so there is no value to adjust. With Peak hold off there is no peak to clear, and the on-device gesture hints say so rather than advertising a gesture that cannot happen. Watching Program Change the bottom line stays PC ch1 even after messages arrive, and that is deliberate: the key is not tied to one preset, so what it watches is the channel, and the preset that arrived — its name, if you have given it one — is what fills the big slot.
| Watch | Control Change, Note velocity or Program Change — the kind of message to display. |
|---|---|
| Channel | MIDI channel 1–16. Must match the sender. |
| CC / Note number | Which controller or note to watch (hidden for Program Change, which carries its own number). Until you pick one, it follows Watch: 22 for Control Change and 60 for Note velocity, matching the default a Control Change key and a Note key already use. Once you pick a number it stays put, whichever way you switch Watch afterwards. |
| Naming | Note velocity only, display only: which octave numbering the note names use. Shares the one setting with the MIDI Note key, so the two panels always agree. |
| Numbering | Program Change only, display only: show programs as 0–127 as sent, or 1–128 to match gear that counts from 1. The Range ends count the same way, so a gauge never disagrees with the value above it. If you have named that program (in any Program Change key’s dropdown, or from an imported name map), the key shows the name instead of either number — Lead rather than 3 — and long names are shortened with an ellipsis to fit the key. The name is attached to the program as MIDI sends it, so it is the same name whichever numbering you pick. |
| Format | Display only — it changes the text drawn in the value slot and nothing else: not the byte on the wire, not the stored setting, and not how often the key repaints. Raw (default) shows the MIDI value 0–127. Percent is relative to this key's own Range, so a key limited to 20–100 reads 100% at 100 — the number agrees with the full-looking gauge beside it. Pan reads L / C / R from the MIDI centre (64), which is absolute: a restricted range honestly never reaches L50 or R50 rather than pretending to. Approx. dB reads the value as a fraction of full scale (0 dB at 127, about −6 dB at half, -inf at 0). It is called approximate on purpose: without knowing your device's own taper no single curve can be right for every DAW, and MIDIRover would rather show one honest approximation than ship a per-DAW curve file for you to maintain. Pan and Approx. dB are offered for Control Change only: a note readout’s value slot shows the note’s velocity, which is a magnitude — so Percent suits it — but it is neither a position nor an amplitude, and a note-off (velocity 0) would otherwise read L50 or -inf. The value keeps one size. A key picks the size that fits the widest reading its format can produce and stays there, so the text does not grow and shrink as the value moves — a Percent key draws 0% at the same size as 100%, and an Approx. dB key draws -inf at the same size as -42 dB. Raw and Pan are unaffected, because every reading they can produce is short enough to share one size already. |
| Name these values | Print a word instead of a number for the values you list, written as 0:Clean, 5:Crunch, 12:Lead — the same list the Bank action uses for its steps, so one you have already written can be pasted straight in. Separate items with commas or new lines. Anything you do not name still shows its number, so a partial list is fine, and a bare 12 with no name after it names nothing. Display only: the byte on the wire, the stored setting and the repaint rate are unchanged. One size for the whole key — naming any value makes the display pick one size for the longest name you have given, so the text does not jump between sizes as the value moves. A long name therefore makes every number on that key smaller: on the default display a six-letter name such as Crunch draws every value at roughly half the height a plain number would, so keep the names short if you want large numbers. Program Change readouts ignore this list — they already name their values from the program names you import. |
| Fill from | Value + Bar and Value + Arc only. Minimum (default) fills the gauge from the low end of the Range — what you want for a level, a gain, a wah. Centre fills it out from the middle instead, so the gauge is empty at the midpoint and grows to the right above it and to the left below. That is how a pan, a balance, or any other control whose middle is the neutral position reads naturally: on Minimum a centred pan shows a half-full gauge, which looks like half of something rather than like centred. It is not offered on Level meter or Needle, and that is deliberate rather than an omission: a meter is twelve quantised segments and a needle is a pointer over a fixed scale, so neither has a continuous fill to start from anywhere. Value prints no gauge at all. The same row, with the same two choices, is on the Control Change key and on the MIDI Dial, resolved the same way — so a Readout and the key driving one CC can be made to show the same picture. Readouts saved before this row existed fill from the Minimum, exactly as they did. |
| Key graphic | Value, Value + Bar, Value + Arc or Level meter. Whether any of them prints the key’s name is the Display row below, and no longer a choice in this list; where the two gauges START filling is the Fill from row above. The first three are the same faces a Control Change key in Sweep · Value / Gauge can draw, so a Readout and the key driving the same CC can show the same picture. Watching Program Change offers only Value: a program number names a patch rather than measuring anything, so a bar, an arc or a meter would draw program 64 as a fraction of a range it does not sit on. On a dial the choice is Value, Level meter or Needle — Bar and Arc have no dial form, and Needle has no key form, because its sweep needs the strip’s width. A Needle draws a pointer over an arc that fills as the value rises: a held peak shows as a dot on the scale, and a value above the top of Range turns the last slice of the arc red. It is deliberately not called a VU — a VU is a defined instrument with a dB-scaled scale and a calibrated reference, and this is the same linear reading the Level meter shows, in the shape of an analogue movement. Level meter is a twelve-segment bar fed by whatever arrives. It is on this action and on the SD+ dial — both are for watching a signal move — and not on the sending keys, which already know what they sent. It shows no number, on purpose: it repaints only when the lit segment count changes, so a number beside it would sit a moment behind the signal. Use Value + Bar when you want the exact figure. The mapping is linear across the Range and the meter is not calibrated — it is a level indicator, not a VU: there is no dB curve and no per-DAW correction, because without knowing your device’s own taper no single curve is right. If the value goes above the top of the Range, the top segment turns red — the meter has run out of scale and is no longer telling you how loud it is. At exactly the top it stays accent-coloured, because pinning there is the meter working rather than failing. The warning holds for about two seconds after the last over-range value, because a clip is an event: a single message above the Range would otherwise be gone before the key next repaints. It is shown whatever Peak hold is set to — that setting governs the falling marker and nothing else. This is the one case a full meter cannot otherwise show: with a Range of 40–90, every value from 90 to 127 looks identical without it. A meter is cheap on the deck’s repaint budget but not free, so one or two per profile is comfortable; a deck full of them will compete with each other. Every face is available for Control Change and for Note. A Readout watching notes shows the velocity, which is a magnitude, so a gauge of it reads as fairly as the percentage does — and a Level meter with Peak hold is one of the better uses of this action, since the marker keeps the hardest recent hit that a bare number cannot show. Program Change is the one exception, for the reason given above: a program names a patch rather than measuring anything. That exception is enforced by the plugin and not only by this panel, so it holds for a key you copied from another profile as well as one you set up here. If a key showing a Level meter is switched to Program Change it draws Value instead — and your choice is not thrown away: switch Watch back to Control Change and the meter returns with nothing to retype. |
| Display | Value + Name (default) prints the key’s name beside the value; Value only drops it and gives the whole face to the reading. It applies to every Key graphic choice — including Needle and Level meter, which previously had no way to hide a name — and on both a key and an SD+ touch strip, since this is the one action that runs on either. This used to be two entries in the Key graphic list. They were never two faces: the plugin drew Value only and Value + Name with the same call and differed only in whether it printed the name, so a list meant for choosing a picture was answering a second question as well — which is why a Needle could not be nameless. Splitting them apart is what makes the choice available everywhere. Readouts made before this change keep exactly the face they had: one set to the old Value only opens as Value with this row on Value only, and every other face opens with its name shown. Nothing on an existing key changes until you pick from this row. |
| Peak hold | Level meter only. Off by default. It controls the falling marker and nothing else — the red clip warning is shown either way. Mark the highest segment keeps a bright marker at the loudest segment reached and lets it fall back down the full scale in about twelve seconds — a segment a second on this face’s twelve — so you can see a peak you would otherwise have missed between glances. The time is what is fixed, so a meter here and a bridge column drawing eight bars empty together. It costs a few extra repaints, because the marker can move on a message the level alone would have skipped — measured at about 2.2 a second against 1.6 without it, both far below the deck’s ten. It falls whether or not values keep arriving: when the signal stops mid-fall the marker keeps stepping down once a second until it lands, then the key goes quiet again. That tail is bounded by the marker itself — at most twelve repaints for one falling from the top, and none once it has landed — so a key watching a dead source settles to an honest empty face instead of holding a line that looks live. |
| Resolution | Watching a Control Change only, and only for CC 0–31. Tells MIDIRover that the controller this key watches arrives as a pair — a coarse half on your number and a fine half 32 controllers above it, so CC 20 is joined by CC 52. The two are reassembled into one value, giving 16,384 steps instead of 128. This describes your gear; it does not change it. Everywhere else in MIDIRover, Resolution is a choice about what to SEND. Here it is a statement about what arrives — and it has to be, because nothing on the wire says whether CC 52 belongs to CC 20 or is a controller in its own right. The MIDI specification defines the pairing as a convention, not a reservation. Set it when your gear does not pair, and the key simply stops following; leave it off when your gear does, and the key shows the coarse half only, which moves in steps of 128. Switching it on widens Range to match and turns it into a type-in box, because 16,384 options is not a dropdown. Range also stays a type-in box while it holds a number too large for the list, so a Range set at 14-bit is not lost if the key is moved back to a controller that cannot pair. Format and Name these values switch off — both are built on a 0–127 scale and would describe a different control. Use 8-bit pair for gear that documents a 0–255 range, such as Novation. MIDIRover waits up to 50 ms for the second half. A device that sends them further apart than that is read as two separate controllers. |
| Range | The low and high ends of the Bar and Arc gauges, the span the twelve segments of the Level meter cover, and the span Percent is measured against — so it appears for any of those three Key graphic choices, or whenever Format is Percent (0–127 by default). Values outside it pin to the end. On a Level meter the Range is the scale. Left at 0–127 a signal that never exceeds 40 lights only the first four segments; set the Range to 0–40 and the same signal uses the whole meter. With Format set to Raw (the default) the number is the value received; the other formats describe that same value differently. |
| Feedback | The shared MIDI input to listen on — one setting for every MIDIRover key. This action does nothing until it is set. |
Recipes
See a parameter’s live value on a key that sends nothing
Watch → the message and its number, plus a Feedback port
The Readout never sends. It needs the port because the value has to come FROM somewhere — your DAW or controller echoing it back.
Catch a peak that moves faster than you can read it
Peak hold on
The reading keeps its highest value for a moment instead of snapping back, which is the difference between seeing a transient and missing it.
MIDI Meters
Display only, dialsA meter bridge on one Stream Deck + dial: up to four level meters side by side, each watching its own address. It never sends MIDI, and like the Readout it needs a Feedback port and software that actually sends MIDI. 1 draws the wide horizontal meter this plugin already uses; 2 to 4 draw vertical columns, and the column count decides their resolution — a vertical column gets 8 segments where the horizontal one gets twelve, because at four columns twelve segments are under 4px each and read as a texture rather than as steps. Each column names itself with the address it watches until you name it; from three columns up the channel is dropped from that label, because a 54.7px column shrinks CC22 ch1 to 11px and cannot fit CC127 ch16 at all.
The panel gives each column a tab carrying its own full set of settings — name, what it watches, channel, number, range and peak hold — so four columns are configured the same way four separate keys would be, one at a time rather than in a wall of rows.
Every column holds its own peak marker and its own clip warning, on the same rules as the single Level meter: the marker falls the full column in about twelve seconds, and the red top segment holds for about two seconds after a value above the Range. Pushing or touching the dial clears every column’s marker, and does nothing else — with no marker held, the deck says so rather than advertising a gesture that would do nothing. With no Feedback port set the strip says Feedback off in words, because four empty columns are indistinguishable from four live signals resting at zero.
| Feedback | The shared MIDI input to listen on — one setting for every MIDIRover key. This action does nothing until it is set. |
|---|---|
| Meters | How many columns the strip draws: 1 (the wide horizontal meter), or 2, 3 or 4 vertical columns. It also decides how many tabs there are — setting it to 2 hides the Meter 3 and Meter 4 tabs, and their settings are kept, not cleared. |
| Display | Whether the columns are labelled. Meters + Name draws each column’s name above it; Meters only hides all of them at once and gives the bars the freed height — a segment grows from 6.75px to 8.75, so a four-up bridge gets about a third more meter. Useful once you know which column is which. It applies to the whole strip, not per column, so it sits outside the tabs. |
| Name | What this column is called, drawn above it. Leave it empty and the column names itself with the address it watches, or with whatever you have renamed that CC or note to. At four columns a long name is shortened to fit; an address never is. |
| Watch | Whether this column follows a Control Change or a Note velocity. One bridge can mix the two — each tab chooses for itself. |
| Channel | The MIDI channel this column listens on, 1–16, and a box to name that channel. Channel names are shared with every other MIDIRover key. |
| CC number | Which CC this column follows (or which note, when Watch is Note velocity — the row is labelled Note then). Defaults to CC 22 or note 60, the same defaults the Control Change and Note keys use, so a column dropped beside one watches what it sends. |
| Range | The low and high values this column’s segments span, per column — eight of them when the strip shows two to four meters, and twelve when it shows one, because a single meter is drawn as the same wide face the Readout’s Level meter uses. A value above the high end lights the top segment red — which means the default 0–127 can never clip, since no CC can exceed 127; narrow the range to see it. |
| Peak hold | Marks the highest segment this column has reached and lets it fall back down the full column in about twelve seconds, per column — the same time a Readout’s meter takes, so a bridge and a Readout watching one CC agree about it despite drawing eight bars against twelve when 2–4 are shown. Set to 1 the bridge draws the wide twelve-segment face instead — the same one the Readout’s Level meter uses — so there the two are not merely comparable but identical, and the marker steps in twelfths. It keeps falling when the signal stops, so a column whose source has gone quiet empties rather than holding a line that looks live — a column falling from the top costs at most one repaint per segment, and the strip is then silent. It does not affect the clip warning, which is always on. Push or touch the dial to clear every column’s marker at once — rotating deliberately does nothing, so a knob turned by accident cannot wipe a reading. |
Recipes
Watch four levels at once on a single dial
Meters → 4, then give each one its own Watch address
A meter bridge across one dial. Like the Readout it never sends, and it needs a Feedback port plus software that reports levels.
One big level instead of four small ones
Meters → 1
At one meter the strip uses the whole width, which reads from further away.
MIDI Monitor
Display onlyA key that shows the last MIDI message that arrived — its type, channel, number, value, and the raw bytes underneath. It never sends anything. This is the key to reach for when something is not working: it answers did anything arrive at all, which nothing else on the deck can tell you. It needs a Feedback port, and says Feedback off until one is picked, or Waiting for MIDI once a port is set but nothing has spoken yet — so a blank-looking key always tells you which of the two to fix.
| Channel | Leave on All to see everything. Pick one channel and the key ignores the others — and also ignores Clock, Start/Stop and SysEx, which carry no channel at all — so leave it on All if you want to watch those. |
|---|---|
| Show | Musical messages (the default) hides the housekeeping traffic that never stops: Timing Clock, Active Sensing and MTC. Clock alone is 24 pulses per beat — about 48 messages a second at 120 BPM — so with Everything, incl. clock selected the key shows little except Clock. Switch it on to confirm a clock is arriving, then switch it back. |
| Feedback | The shared MIDI input to listen on — one setting for every MIDIRover key. This action does nothing until it is set. |
Recipes
Nothing is working and you cannot tell which half is at fault
Drop a MIDI Monitor key on the deck and pick the Feedback port
It shows the last message that arrived — type, channel, number, value and the raw bytes. If nothing appears, the problem is upstream of this plugin.
Too much traffic to read, and only one channel matters
Channel → the one you are debugging
Everything else is ignored, so the message you are waiting for is not buried by the rest.
Tempo
Display onlyA key that reads the tempo of whatever is sending MIDI clock, and beats along with it — once a beat, so counting it gives you the tempo — with the measured BPM above and the key's name below. It never sends anything. Pick how it keeps time in the Key graphic row: a metronome rod that swings, or a flash that pulses the key in your accent colour — one to look at, one to catch in the corner of your eye. Something has to be sending clock: a DAW will if you switch on clock output for the port MIDIRover listens to, while a standalone amp-sim plugin will not send it at all, so this key does nothing for that setup. Until clock arrives it reads No clock, and Feedback off if no input is picked — so a key that is not moving always tells you which of the two to fix. Stop dims the rod, or stops the flash, so a paused DAW still shows its tempo without pretending to play.
| Key graphic | How the key keeps time. Metronome (default) draws a rod hinged inside a wedge, swinging left and right on each half of the beat — something to look at directly. Flash replaces it: the whole key lights up in your key colour once a beat — lit for the first quarter of the beat and dark for the rest — so you can read the beat without looking straight at the deck. With no rod in the way, Flash also draws the BPM large in the middle of the key, exactly as a Control Change key set to Value only draws its value; the key's name stays in the usual place below. The flash uses the palette's own two colours on both key backgrounds — elsewhere a light background gets a darkened variant of the accent, which is right for thin lines but made a bright preset like Emerald → Lime read as dark green and olive across a whole key — and on the lit beat the text switches to whichever of black or white reads better against your colours — black for all six presets, and white if you pick a custom pair dark enough to need it. Neither display flashes while the transport is stopped. |
|---|---|
| Average over | How many beats the reading is measured across: 1 beat, 2 beats or 4 beats. This changes how the number looks, not how right it is — one beat is already accurate to a fiftieth of a BPM. Pick 1 beat to see a tempo change the instant it happens (about 0.7 s), or 4 beats for a number that sits still (about 2.6 s to catch up). At 1 beat the last digit may flicker between neighbouring values; at 4 beats it holds. |
| Feedback | The shared MIDI input to listen on — one setting for every MIDIRover key. This action does nothing until it is set. |
Recipes
Show the tempo your DAW is actually running at
Pick a Feedback port carrying MIDI clock
It reads the clock rather than guessing. MIDIRover does not generate clock, so this follows — it never leads.
Label
Text onlyA key that only shows text. It sends no MIDI, listens for none, and a press does nothing — use it to annotate the deck: a heading over a row of stomps, or a note beside the key it explains. The Stream Deck app can put a title on any key, but every other action does something when pressed, so a label built from one is a trap for whoever touches the deck next.
| Text | What the key shows. It wraps to fit, and a line break you type is kept. There is no separate Name row on this action: elsewhere the Name is a caption under a graphic, here the text is the key. |
|---|---|
| Size | Auto picks the largest size that shows everything and keeps every word whole, so a short word comes out big and a sentence smaller. Pick a fixed size (10–30 px) to match neighbouring labels instead; text too long for it is cut with an ellipsis rather than overflowing. |
| Align | Two pickers, one decision: vertical (Top / Middle / Bottom) and horizontal (Left / Center / Right), so a caption can sit against the edge nearest whatever it describes. |
| Text colour | Default follows the light or dark key background — that is what keeps a Label looking like a label rather than a lit control. Accent paints the text in the Deck theme colour instead, which is useful for a heading above a row, and is the only setting on this action that the theme's colour affects at all (the light/dark background always applies). Small text uses a solid accent rather than the gradient, which turns muddy at that size. |
Recipes
Title a row of keys so the deck reads as sections
Text, then Size and Align to taste
A Label sends nothing and does nothing on press. It is there purely so the deck explains itself.
Colour-code one area of the deck
Text colour → a colour for that group
Colour carries further than text at a glance, which is what matters on a dark stage.
Learning Mode
The fast way to set up a key — no typing CC numbers. Available on Control Change, Note, and MIDI Dial. This is MIDIRover learning from a controller you already own. Teaching your software to follow a MIDIRover key is the opposite direction and lives in the Neural DSP quick-start.
Open the Learn row
In the key’s settings, find Learn. Pick the MIDI input your controller is on — or leave Auto (first input).
Press Learn
The key reads Listening…. Move a knob, press a switch, or turn a dial on your controller.
It fills itself
MIDIRover captures the CC, Note or Program Change and fills the Channel and number for you. Status shows what it learned.
Naming values
Give channels, CCs, programs and notes friendly names so the dropdowns read 22 · Drive instead of just 22.
- Type a name in the small field next to most Channel / CC / Program / Note dropdowns — the four listed below have no such field.
- Names are shared across every key that offers that dropdown, so you label a value once — and every list of channels, CC numbers, programs or notes shows them, including the four you cannot type a name into. Those four are read-only for four different reasons, and the last of them is the only list in MIDIRover that shows no names at all. The MIDI Readout key’s Number list is the same field for a CC number or a note number depending on what the key is watching, so there is no one list to rename into — it reads both, following Watch. The Panic key’s Send on list is a target selector with an All channels option rather than a plain channel dropdown, so it shows the name of the gear on each channel and nothing more. The MIDI Monitor key’s Channel list is a filter on what arrives, and a name there tells you whose traffic you are watching. And the Advanced MIDI key’s Note list, which appears under Poly Aftertouch, is the one that shows no names: on the gear that message exists for, its note byte is a per-device parameter address rather than a pitch — an Access Virus parameter, a mixer’s mix — so the shared musical note names would be the wrong vocabulary rather than a missing one. Name that key with its own Name row instead, which is per-key, as an address whose meaning is per-device needs. In all four, renaming stays on the keys that actually address a channel, a controller or a note. One more thing worth knowing about channel names in particular: they show in every list — each panel’s Channel row, the Monitor’s filter, Panic’s destination list — and never on a key face. An unnamed key names the message it sends (
CC127 ch16), and that form is already at the ten-character limit the key face allows, so there is no room for a name as well; the number is the half you cannot do without. - CC and program names are scoped per channel — CC 22 on channel 1 and channel 2 keep separate names and never mix. Note names are global, since a note number means the same thing on every channel.
- Names in brackets are ours, not yours. Where MIDI already has a name for a control number, the list shows it in brackets —
6 · (Data Entry MSB),120 · (All Sound Off)— so you can tell at a glance which values you have actually named. Type your own name for one and the brackets go:6 · Gain. Every list follows this, the read-only ones included, so the same number reads the same way wherever you meet it. Note names have no brackets, because60really isC4on any gear, while a control-number name only describes what the protocol does with it. - Note names start from the musical name (
60 · C4) and you can replace it —36 · Kickis the usual reason. Which octave numbering those built-in names use is a single global choice under Naming on any Note key:Middle C = C4for Roland gear and most DAWs,C3for Yamaha, orC5, which suits a few older sequencers. It changes the label only; the note number sent never changes. - Name map — import a whole set of names at once, rather than typing them one at a time. Any key that offers naming has this row; the names are shared, so it does the same thing wherever you open it. MIDI Map Studio can build one for you from a Neural DSP mapping file: under Names for MIDIRover, press Copy name map. A map is also plain JSON, so anyone can write one by hand or share theirs. You can paste it in either of two notations. A name-map JSON document is what Map Studio copies and what one machine hands another. For typing by hand there is a plainer form, which needs no brackets, quotes or commas:
Sections are# my rig [channel 1] name = Amp cc 22 = Drive program 0 = Clean [notes] 36 = Kick[channel N]and[notes]; a line iswhat = name;#starts a comment and blank lines are ignored. Case does not matter,:works as well as=, andpcorprogmeanprogram. If a line cannot be read, the import is refused whole and names the line — which is the reason this form exists, because a JSON error can only point at a character. You do not need this page to hand: the panel shows an example of both notations — press the small ? beside the buttons — each with a button that copies it, ready to edit. Press Import — it merges: a name the document does not mention is left exactly as it was, so importing a map for one device never costs you the names you typed for another. A document that is not a name map, or is from a newer version of MIDIRover, is refused whole and nothing changes — you are told which, rather than being left with half a map applied. What you pasted stays in the box so you can correct it. Two more documents are refused for the same reason, and both matter most if you are generating a map rather than typing one: a blank name (a name with no text in it would quietly delete the name that was there, so it is refused rather than applied — to leave something unnamed, omit the entry, and to delete a name you already have, empty its rename box), and the same number written twice in one section —7and07are the same controller, and a document that names it twice is saying two things about one address. Leading zeros themselves are fine:cc 07andcc 7mean the same thing, in either notation. A third refusal joins those two: a name containing a character with nothing to draw — a control character, a text-direction override, a zero-width space. These are invisible, so a name carrying one cannot be read, retyped or told apart from the name beside it, and a tool that pads or converts text is the usual way one arrives. MIDIRover names the character it found and the line it is on, so you can fix the document at the source. Ordinary text is untouched: spaces, punctuation, accented letters and non-Latin scripts are all names —Bank P3,Amp Ch. 2andリードall import. The last refusal is length: a name can be up to 40 characters. That is not a limit invented for imports — it is the longest name the panel already lets you type into a key’s Namebox, and the rename boxes stop at 24, so a longer one in a document is asking for something you could not have created by hand. A key shows roughly a dozen characters anyway. As with every other refusal, MIDIRover says which name and how long it was, and changes nothing — it will not quietly shorten a name, because that would rewrite a document you may be sharing with someone else. Export goes the other way: it reads out the names you have already typed, into the same box and selected, soCtrl+Ccopies them. That is how a set of names you built by hand leaves this computer — to keep, to move to another machine, or to give to someone with the same gear. One thing an export does not carry is a source block saying where the names came from, and that is deliberate: your profile is whatever you have merged — perhaps a pack for one device, a pack for another, and a dozen names you typed — so no single origin would be true of the result. If you are putting together a pack to share, add that block to the exported document by hand. Clear removes them all. Because importing merges, names from two different rigs otherwise accumulate with no way to separate them — Clear is how you start again. It asks twice (the button becomes Really clear?, and waiting cancels), tells you how many it removed, and touches nothing but names: your MIDI port, your remembered channel, your colours and your Middle C setting all stay. Export first if you might want them back — that copy is the only undo. One thing to expect: keys on other pages keep showing their old names until you next open those pages. MIDIRover can only redraw the keys the deck is currently showing, and a key redraws itself correctly the moment it appears. An import also tells you if the map renames one of MIDI’s own control numbers — CC 120 All Sound Off, CC 0 Bank Select and a handful of others. It still imports, because plenty of gear really does drive its own parameters from those numbers; it is worth knowing because on most gear they do something structural rather than setting a value.
Neural DSP quick-start
Three steps. They assume you already have a Control Change key that sends — Install & first run ends by making one and checking it.
Route MIDI in
Open your Neural DSP plugin (or its standalone) and set its MIDI input to the port MIDIRover sends on — your loopMIDI port on Windows, MIDIRover on macOS.
MIDI-Learn a control
Right-click a stomp or knob in Neural DSP and choose MIDI Learn. Press your MIDIRover Control Change key — it binds instantly.
Switch presets
In Neural DSP's MIDI Mapping window, add a Program Change → Preset entry per preset, then use Program Change or Bank Up / Down keys to jump or scroll tones. In a DAW the host has to forward Program Change (Ableton Live doesn't; Logic often doesn't) — the standalone app is the reliable path, or map presets to CCs there instead.
Troubleshooting
- Nothing happens when I press a key
- Open any MIDIRover key’s settings and read the line under MIDI Port — it names the port and says whether anything is leaving the plugin at all. Red: nothing is being sent, and the line says why. Amber: MIDI is going somewhere other than the port this key is set to. Grey: MIDIRover is sending where you meant, so the problem is downstream — check that loopMIDI is running (Windows), that your software’s MIDI input is the same port, and that the channel matches on both sides. Opening the settings is worth doing on its own: it makes MIDIRover re-check the port and reopen it.
- MIDIRover has gone grey — the Stream Deck app has disabled it
- This is not a licence problem, a broken install, or anything to do with your MIDI setup: it means MIDIRover failed to start, and the app has stopped trying. A plugin that dies while starting is relaunched automatically every few seconds, and after twelve failed launches the app gives up and greys it out — so this appears a couple of minutes after the first failure rather than the moment something goes wrong. It is nearly always a machine still waking up: MIDIRover waits and retries while the app starts, and the disable only lands when whatever it is waiting for takes longer than that.
The way back is to restart the Stream Deck app for real. The disabled mark lives in the running app and is written nowhere on disk, so a genuine restart always clears it — there is nothing to repair, nothing to reinstall, and no reason to delete your keys. What does not work is closing the window: the app keeps running in the Windows notification area (or the macOS menu bar), and MIDIRover stays grey however many times you bring the window back. Quit it properly — right-click the tray icon and choose Quit on Windows, or Quit Stream Deck from the menu bar on macOS — then start it again. If the actions are still grey after that, the app never really quit; restarting the computer is the sure way and costs less than it sounds, because your keys and their settings are stored and come back exactly as they were.
If it keeps happening, the file to send isstartup-error.log— MIDIRover writes it beside its own bundle, in thebinfolder of its plugin folder (%appdata%\Elgato\StreamDeck\Plugins\com.midirover.plugin.sdPlugin\binon Windows, or~/Library/Application Support/com.elgato.StreamDeck/Plugins/com.midirover.plugin.sdPlugin/binon macOS). That file is the only artifact this failure leaves: the ordinary MIDIRover log is empty, because the plugin never got far enough to open it. Sendstartup-error.logand say what the machine was doing at the time — waking from sleep, first login, a fresh install — and that is enough to work from. - Where the log file is, and what to send if you report a problem
- MIDIRover writes its log inside its own plugin folder, under the Stream Deck app’s Plugins directory — the same place on both systems. On Windows, paste
%APPDATA%\Elgato\StreamDeck\Plugins\com.midirover.plugin.sdPlugin\logsinto the address bar of any Explorer window; on macOS opencom.midirover.plugin.sdPluginin the Stream Deck app’s Plugins directory and look in itslogsfolder. Take the newest file: the log rotates every time the plugin restarts, so the one you want is usually.0.log, and timestamps inside it are UTC rather than your local clock. If you are reporting something, the last hundred lines around the moment it went wrong are far more useful than the whole file — and a MIDI Monitor key on screen at the time answers “did anything arrive at all”, which the log alone often cannot. - The plugin isn’t receiving in Neural DSP
- Confirm the channel matches on both sides, and that you MIDI-Learned the right control. Watch incoming MIDI with a monitor if unsure.
- I can’t find the MIDI Dial action
- The dial actions need a model with dials; the Stream Deck + and + XL are the two Elgato documents with a touch strip to display the value on. On other models the dial action is hidden by design — use the key actions (e.g. CC Sweep mode to ride by hand).
- An NRPN or RPN key sends, a MIDI monitor shows the messages, and the device does nothing
- Check the device’s own NRPN/RPN reception switch before anything else. Many instruments ship with it off: Roland documents Rx.NRPN as a per-part switch that is off at power-on on several GS boxes, and Yamaha and Allen & Heath both have receive switches of their own. This is the one failure where every tool agrees nothing is wrong — the bytes are correct, the port is open, a monitor shows them arriving — because nothing is wrong on this side. MIDIRover cannot detect it: it knows which port it opened, never what is listening at the other end, which is why the panel states it as a note on every NRPN and RPN key rather than as a warning about yours in particular.
- The port is there, opens fine, and nothing crosses it
- A loopMIDI port created — or re-created — while other apps already held loopMIDI ports open can come up listed but non-functional. Every screen looks correct and no error appears anywhere; the only tell is a MIDI monitor showing zero traffic. Restart loopMIDI (quit it fully and reopen) — you don’t need to restart the Stream Deck app, because MIDIRover notices the port coming back and reopens by itself. Re-adding the port while apps are attached often reproduces it. Seen twice on one Windows machine. Detail in the troubleshooting guide.
- I deleted and re-created a virtual port — do I need to restart?
- No. If the port disappears and comes back, MIDIRover notices within about three seconds and reopens both its MIDI output and its Feedback input by itself, with nothing to touch. (That is for a port you picked by name. If you left the port on Auto, MIDIRover picks again on your next key press rather than in the background.)
- My port vanished from loopMIDI — why does the key still look fine?
- It shouldn’t any more. Open any key’s settings and the line under MIDI Port turns red and names the port that went missing, and the dropdown shows it marked (not present). MIDIRover deliberately does not switch you to some other device when your saved port disappears — quietly rerouting a rig into whatever else happens to be plugged in is worse than sending nothing — so nothing is sent until the port returns (it reopens by itself) or you pick another one. Re-create it in loopMIDI with the same name and it reconnects on its own. If the port is gone for good — renamed, or a device you no longer have — choose Auto at the top of the dropdown: that releases the saved name and lets MIDIRover pick again.
- Windows: no ports listed
- Open loopMIDI and create at least one port, then reopen the key settings so the list refreshes.
- None of the above — it still doesn’t work
- That is worth reporting: an unexplained failure here is either a bug in MIDIRover or a gap in this manual, and both are worth fixing. Report it with what you pressed, what you expected, and what the line under MIDI Port says — those three sentences are usually enough to identify it.
- The key shows a fixed picture and never updates
- If you set your own image on a key in the Stream Deck app, that image wins — Stream Deck stops letting the plugin draw, so the live graphics freeze. Nothing is broken and no error appears; the key just never changes again. It affects everything MIDIRover draws: the Sweep slider and knob, the Toggle on/off graphic, the Bank and Program numbers, and the MIDI Readout value. Clear the custom image on that key in the Stream Deck app (reset its icon back to the action's default) and the live graphic returns immediately. To keep a personal look, use MIDIRover's own colour settings instead — a per-key palette or the deck theme — which restyle the graphic rather than replacing it.
Support & feedback
Something not working, or a key you wish existed? Report a bug or ask for help — it goes straight to the developer, and a clear report is the fastest way to get a fix.
MIDIRover is free and made by an independent developer who plays guitar. If it saves you setup time, buy me a coffee.
MIDIRover 1.0.0.0 · Not affiliated with Neural DSP or Elgato. MIDI, Stream Deck and product names are trademarks of their owners.