Multi-controller mode

Multi-controller mode turns one DAW track armed for input into four-player territory — up to four controllers polled in parallel, each on its own MIDI channel, all feeding the same virtual port. Pro-tier feature, built for duo jams, accessibility setups, and one-player-with-two-hands configurations.

What it actually does

Plug in a second controller. The app detects it, assigns it the next free MIDI channel, and shows it as a second tile in the editor. Each controller has its own bindings, its own deadzones, its own calibration — they share a virtual port but never collide.

Controller A might be your drum kit (channel 1, note triggers). Controller B might be your synth (channel 2, CC sweeps and pitch bend). One DAW, two armed tracks, two players — or one player using both hands independently.

{
  "controllers": [
    { "id": "DualSense#A4B2", "channel": 1, "preset": "drum-pads" },
    { "id": "DualSense#9C71", "channel": 2, "preset": "synth-bay" }
  ]
}

Controller capability matrix

Multi-controller is hardware-agnostic — but not every gamepad supports every feature. If you're mixing devices, this table tells you what survives the trip across each one. Anything missing on the source gracefully degrades to the next-best mapping:

Controller	Notes & CCs	Adaptive triggers	Haptics	Gyro	Touchpad
DualSense (PS5)	Yes	Yes	Dual-actuator	Yes	Yes
DualShock 4 (PS4)	Yes	No	Rumble	Yes	Yes
Xbox Series X|S	Yes	No	Rumble + impulse	No	No
Xbox One	Yes	No	Rumble + impulse	No	No
Switch Pro	Yes	No	HD rumble	Yes	No
Joy-Con (pair)	Yes	No	HD rumble	Yes	No

Channel routing

By default, controller N gets MIDI channel N. You can override this per-controller — useful if your DAW template expects drums on channel 10 (General MIDI percussion). See MIDI messages for the channel refresher.

Each controller's bindings can override the channel too. A binding-level channel always wins over the controller-level channel — handy for multi-timbral setups where one controller drives three synths on three different channels.

Mixing controller types

Multi-controller doesn't require matching hardware. You can run a DualSense and a DualShock 4, or a DualSense and an Xbox controller, on the same port at the same time. Each controller gets its own UI tile reflecting its actual button layout — the editor isn't locked to one device shape.

Bundle config — what gets saved

A multi-controller bundle is a single JSON file that references each controller, its assigned preset, its channel, and any overrides. Bundles are portable: copy the file plus the referenced presets and the whole rig moves to a new machine. Here's a full two-controller bundle in production shape:

{
  "type": "multi-controller-bundle",
  "name": "duo-jam-night",
  "version": "1.0.0",
  "controllers": [
    {
      "id": "DualSense#A4B2",
      "role": "drummer",
      "channel": 10,
      "preset": "drum-pads",
      "overrides": { "haptic": "enabled" }
    },
    {
      "id": "DualSense#9C71",
      "role": "synth",
      "channel": 2,
      "preset": "synth-bay",
      "overrides": { "pitchBendRange": 12 }
    }
  ],
  "transport": { "syncSource": "external" }
}

Setup

With Pro enabled, plug in the second controller. The app detects it within a second and prompts you to confirm the channel assignment. Pick a preset for it (or build one fresh), save the multi-controller config as a single preset bundle, and you're done.

Common mistakes

• Two controllers on the same channel. Both fire into the same DAW track, events collide, and the result is unplayable. Always assign distinct channels — the app warns, but you can override the warning and shouldn't.
• Sharing one preset between controllers. Presets are calibrated to a specific controller's serial. Two controllers running the same preset inherit the same calibration, which is wrong for both. Save each controller's preset separately.
• Using Bluetooth on all four controllers. Bluetooth shares a single 2.4 GHz channel. Three or four BT controllers in the same room contend for airtime and start dropping events. Wire at least two.
• Hot-swapping mid-recording. Plugging in a new controller mid-record reshuffles channel assignments. Set the rig up before pressing record, not during.
• Forgetting to bundle. Saving each preset individually is fine for testing — but the multi-controller bundle is what locks the channel assignments, roles, and overrides into a single recallable config. Save the bundle when the rig works.

Ready to wire up your first multi-rig? Start with two presets you already love, then bundle them via File → New multi-controller config in the mapping editor.