Controllers
Connect a MIDI controller, trust it, and manage mapping bundles and MIDI ports from Settings.
Settings → Controllers (“MIDI mappings and connected hardware. Trust a device to auto-enable it on connect after Save.”) has two cards: Mappings and MIDI ports.
Mappings
Card subtitle: “Stored in app data. Seed copies shipped maps when missing; Update overwrites from the app bundle.” The header button is Update All.
Each row shows the device’s vendor and product as its title. Pills beside it give the mapping id, the device id, the bundle version, and Attached while the mapping is live. On the right:
| Control | What it does | Timing |
|---|---|---|
| Update available | Appears when the mapping shipped with this build is newer than the copy in app data. | Label only |
| Update | Overwrites the app-data copy from the app bundle. | Acts immediately |
| Trust | Toggles trust for the device. | Part of the draft; takes effect on Save |
| Attach | Toggles the mapping on or off. | Acts immediately |
With no mapping bundles in app data yet, the card reads “No mappings in app data yet.”; Update All seeds them from the bundle.
Save restarts the audio engine when it is running. The mapping actions above run before any save; Trust is the only row control that waits for it.
MIDI ports
Card subtitle: “Detected MIDI inputs and outputs, and the mapping each one matches.” Every detected port gets a row with an IN or OUT chip, the port name, and either the mapping it matched or No mapping.
With nothing plugged in, the card reads “No MIDI ports detected.”
Connecting a controller
Plug in a controller Mixar has a mapping for and a toast appears: <device> connected, then “Do you want to use this controller?”. The prompt has an Always allow this device checkbox and Cancel / Enable.
- Enable attaches the mapping now.
- Always allow this device plus Enable also stores the device id in the trusted list. The next time the device is plugged in, the mapping attaches without asking.
- Cancel leaves the port alone. It will not ask again until the device is re-plugged.
Trust and Attach on each row are the same switches the prompt sets.
Controller audio outputs
A mapping can declare the controller’s own audio interface, including which
channels carry the master and headphone buses. When that controller’s output
device is present and Mixar is still using another output, attaching the mapping
shows a second prompt: Switch audio outputs to <device>? Switch
outputs runs the engine on the controller without changing your saved
devices; Keep current leaves
Settings → Audio as it is. While the override is active, the Master bus and
Preview bus cards show an Overridden by <device> mapping badge, and the
fields display the active controller route. Editing a field removes that bus’s
badge; Save applies the new route and leaves the rest of the override intact.
Unplugging the controller (or detaching its mapping) resumes the saved devices
immediately. The override is live only for the session: it is never written to
the saved audio settings.
To skip the prompt on later connections, tick Remember before choosing Switch outputs. The same option is available as an Audio toggle on the mapping row in Settings → Controllers; like Trust, it takes effect when you press Save. With it enabled, attaching that controller switches the outputs automatically.
Declining only affects the current connection, so reconnecting asks again. A saved route that happens to match the controller does not suppress the offer; only a live override or the Audio preference does.
The DDJ-400 mapping ships with master on channels 1–2 and headphones on 3–4, and confirming also enables the preview bus. The exact routes are visible and editable in Settings → Audio.
What ships
Only the Pioneer DDJ-400 has a shipped mapping. Adding another controller means authoring a mapping bundle: MIDI mappings.