Midi Stone

For Sending one controller to several instruments, moving a controller to another channel or key, turning one control into another, and keeping unwanted messages away from a device or a program.

• The map: devices on the left, ports on the right. Pick a device, switch on the ports it should reach. Nothing is linked until you link it.
• Each link has its own gates (notes, controls, programs, bend and pressure, clock), can move everything to one channel, and can transpose.
• Mappings turn one message into another: a control into a different control, a note into a program change, pressure into pitch bend, a pad into a key press on the computer. Values can follow, stay fixed, be scaled along a curve, or toggle. Learn sets the trigger from the controller itself.
• Blocking in three places: the gates on a link, filters at the door (clock, active sensing, system exclusive, or any message by its first bytes), and a Block mapping for one exact message.
• Four layers give one controller four sets of jobs.
• The reactor in the middle is a five-pin MIDI socket in a stone: its left pins light with what comes in, its right pins with what goes out, a red arc shows a blocked message, and its rim carries one segment for each mapping.
• The glass shows who sent what, where it went and why, the tempo of an incoming MIDI clock, and the sixteen channels. The monitor lists every message with its bytes and can be searched and exported.
• This is a concept preview running in Chrome, pictured here with stand-in devices. It has not been tried with real controllers yet, and the Windows program is not built. Pressing computer keys needs a small helper program beside it.

Status Concept preview (browser, Web MIDI). Windows program not built yet
Inputs and outputs Every MIDI port the computer has; plugging and unplugging is followed
Mappings Control, note, program, pitch bend, key press, block, layer
Sets Saved as files; sets from Nexus MIDI open too (without their Ableton actions)