The Xbox Adaptive Controller is the most widely distributed piece of adaptive input hardware ever made. It was built so that people who cannot use a standard gamepad can play games, and it does that by turning the gamepad into a hub: nineteen labelled 3.5 mm jacks on the back, two USB-A ports on the sides, and two large programmable pads on the top surface. Every one of those inputs is, as far as a computer is concerned, an ordinary Xbox button press. Which means every one of them can become a MIDI note, a control change, a transport command, or a scene launch — the moment you put a bridge in between.
This guide covers that in practical detail: what the XAC actually exposes to a computer, how to wire it for music rather than for games, which mapping behaviours matter when a player has a small number of reliable inputs, and — just as importantly — where the XAC is the wrong answer and what to reach for instead.
- What it is: the XAC is a switch hub that looks like an Xbox gamepad to the OS. Universal Controller MIDI reads it like any other gamepad and emits virtual MIDI.
- Input count: Microsoft documents nineteen 3.5 mm jacks plus two USB-A joystick ports. Each jack maps to one Xbox input, and each Xbox input can carry its own note or CC.
- What you need: an XAC, switches of your choosing, a mount, a computer running macOS, Windows or Linux, and a DAW.
- Free vs Pro: free covers one controller, one MIDI port, three saved presets. The mapping editor is Pro, and custom mapping is the whole point here — budget for it.
- Get assessed: SpecialEffect and AbleGamers do this work properly and for free. A blog post is not an assessment.
What does the Xbox Adaptive Controller actually send to a computer?
It sends ordinary Xbox gamepad input — the switch plugged into a jack does not appear as its own device, it appears as the button that jack is labelled with.
This is the single most useful thing to understand about the XAC, and it is what makes it work with a MIDI bridge at all. The controller does not expose nineteen new device types to the operating system. It presents the familiar Xbox control set, and internally it routes each 3.5 mm jack to one of those controls. Microsoft's own Xbox Adaptive Controller product page and the getting started support article describe the device as a hub designed to accept external switches, buttons, mounts and joysticks, and the publicly documented hardware summary notes nineteen jacks on the rear frame, each corresponding to a different button, trigger, bumper or d-pad function.
For music this is good news, because it means no special support is required anywhere in the chain. If a bridge can read an Xbox controller, it can read an XAC. Universal Controller MIDI treats the XAC exactly the way it treats a Series X|S pad covered in our Xbox Series controller MIDI setup guide, with no separate code path and no separate preset format.
The practical consequence is that your mapping work happens in two places: once at the hardware layer, deciding which physical switch goes into which labelled jack, and once at the software layer, deciding what MIDI that jack emits. Those are genuinely different decisions and it is worth being deliberate about both.
How do you wire switches into the XAC for a music rig?
Put your most reliable, lowest-effort inputs on the jacks you will use most, and decide that ordering before you decide any MIDI at all.
The rear jacks take a standard 3.5 mm TRS plug and register when the switch closes a circuit. That is deliberately a very low bar, and it is why the XAC ecosystem is so large — anything from a commercial capability switch to a homemade foil pad works. AbleNet manufactures a wide range of capability switches with different actuation forces and surface sizes, and Logitech's Adaptive Gaming Kit was produced specifically as a bundle of buttons, triggers and mounting hardware for the XAC. Microsoft also maintains a compatible devices list worth reading before buying anything.
For a music rig, the ordering logic is different from gaming. In a game, the inputs you use most are movement and the primary action. In a music session, the inputs you use most are usually transport (play, stop, record), the undo command, and whichever one or two sounds you are currently working with. Those four or five functions should land on your easiest switches. Everything else — scene navigation, track select, tempo nudge — can sit on inputs that take more effort, because you hit them far less often.
A useful exercise before wiring anything: sit with the person who will use the rig and list every action they want to perform in a session, then rank them by frequency. The top five get the best switches. This takes twenty minutes and saves weeks of quiet frustration later.
Mounting matters more than switch choice
A good switch in a bad position is worse than a mediocre switch in a good one. Switch mounting — gooseneck arms, wheelchair clamps, tray mounts, headrest mounts — is its own discipline, and it is one of the main things SpecialEffect's assessment team works on when they build a setup for someone. The charity provides assessments, equipment loans and ongoing modification free of charge in the UK. If you are within reach of that service, use it before you spend money on switches.
Which MIDI behaviours matter most on an adaptive rig?
Latch and toggle behaviours matter more than anything else, because they let one short press replace a long hold.
On a standard gamepad, holding a button is cheap. On an adaptive rig it often is not — sustained pressure may be tiring, painful, or simply not possible depending on how the switch is actuated. So the mapping question stops being "which note does this button play" and becomes "what happens when this switch closes, and what happens when it opens".
The behaviours worth having in your vocabulary:
| Behaviour | What happens | When to use it on an adaptive rig |
|---|---|---|
| Momentary | Note on while held, note off on release | Short percussive hits where hold time carries musical meaning |
| Toggle | First press turns on, second press turns off | Mutes, solos, loop enable, effect bypass — anything binary |
| Latch | Press starts a sustained note that stays on until a separate stop | Drones, pads, held chords where a long hold is not viable |
| One-shot | Single press fires a fixed-length event, release is ignored | Sample triggers, scene launch, transport commands |
| Hold-to-repeat | Held switch repeats at a set rate | Scrolling through a track list or stepping a value with one input |
Universal Controller MIDI exposes these as per-input behaviours in the mapping editor, which is a Pro feature. We go through the design trade-offs between them in far more depth in adaptive MIDI mapping design, and the single-switch case specifically in switch-accessible MIDI triggering.
How do you get continuous control from an XAC?
Through the USB-A joystick ports, or by using a repeat behaviour on a switch to step a control change value up and down.
Continuous control — filter cutoff, volume, pitch bend, anything that wants a value rather than an on and off — is the one area where a pure switch rig needs thought. The XAC's two USB-A ports accept external joysticks, and SpecialEffect's GameAccess resource on XAC joysticks walks through the options and how they behave. A joystick plugged into one of those ports presents as the corresponding analog stick, so a MIDI bridge reads it as a normal axis and can emit a CC from it.
Microsoft has since released the Xbox Adaptive Joystick as a first-party option in that category. Whether it suits a given player is an individual question about grip, force and travel — but mechanically, anything that registers as an analog axis will produce a usable MIDI CC.
If a joystick is not viable, the fallback is to step values with switches. Assign two inputs as increment and decrement on the same CC, give them a hold-to-repeat behaviour, and set the repeat rate slow enough to be controllable. It is not expressive in the way a stick is, but it is completely usable for setting a level, and it has the significant advantage of being recallable — you can hit an exact value and leave it there, which is harder with a spring-return stick. Our piece on stick drift compensation covers the deadzone settings that make axis inputs behave predictably once you do have a stick in the rig.
What does a working XAC music mapping look like?
A small number of high-frequency functions on the easiest inputs, one sustained-sound latch, one stop-everything panic switch, and nothing else competing for attention.
Here is a layout that has held up well as a starting point. Treat it as a skeleton to be rebuilt around the individual, not as a preset to copy.
| Control | MIDI message | Target |
|---|---|---|
| Large pad 1 (top surface) One-shot note Play / stop transport toggle Switch: Built in | ||
| Large pad 2 (top surface) One-shot note Record arm and start Switch: Built in | ||
| A jack Momentary note Primary drum or sample sound Switch: Lowest-force switch available | ||
| B jack Momentary note Secondary sound Switch: Second easiest switch | ||
| X jack Latch note Sustained pad or drone Switch: Any reliable switch | ||
| Y jack One-shot note Undo Switch: Any reliable switch | ||
| LB / RB jacks Hold-to-repeat CC Filter cutoff down / up Switch: Switches at moderate reach | ||
| D-pad up / down jacks One-shot note Scene or clip navigation Switch: Switches at moderate reach | ||
| Menu jack One-shot note All notes off and master mute Switch: Deliberately separate switch | ||
| USB-A port 1 Two CC axes Two continuous parameters Switch: External joystick | ||
Two notes on that table. First, the panic switch deserves its own physically distinct actuator, placed where it cannot be hit by accident but can always be reached — a stuck latched note with no way to stop it is the single worst failure mode in this kind of rig, and it is worth designing around. Second, resist the urge to populate all nineteen jacks on day one. Start with six or seven. Add inputs only when the person using the rig says they want another one.
Does the free tier of Universal Controller MIDI cover this?
Partly — enough to verify the hardware works, but not enough to build a genuinely adaptive layout.
We should be direct about this rather than bury it. The free tier handles one connected controller, one virtual MIDI port, and three saved presets. For an XAC rig that is enough to plug in, confirm every switch registers, and play notes with the default mapping. That is real and useful.
What it does not cover is the mapping editor, which is where you assign custom notes and CCs per input and set momentary, toggle, latch and repeat behaviours. That editor is a Pro feature at AUD $89 as a one-time purchase, and for this audience it is not optional — the default presets are built around a two-handed gamepad layout and will be wrong for almost every adaptive rig. If you are evaluating whether to buy, install the free build first and confirm all your switches register before you spend anything.
The one-controller limit on the free tier also matters here. Some adaptive rigs pair an XAC with a second device — a foot controller, another gamepad for a different body part, or a co-located assistant's pad. That is a Pro scenario. Our write-up on multi-controller sessions covers how the bridge handles more than one device.
Where is the Xbox Adaptive Controller the wrong tool?
Anywhere the barrier is not about pressing things — breath, speech, eye gaze and head movement all need different hardware.
This matters and it gets skipped too often. The XAC is a switch and joystick hub. It is excellent if a person can reliably actuate at least one switch with some part of their body, and it scales beautifully from one switch to nineteen. But it has nothing to offer if:
- The reliable input is breath. Sip-and-puff and breath-controlled instruments are a different category. The QuadStick is a sip-and-puff game controller built for this, and Jamboxx is a breath-driven music controller. Both address needs the XAC does not.
- The reliable input is gaze or head position. Eye-tracking hardware such as that made by Tobii operates on an entirely different principle, and SpecialEffect maintains an eye gaze resource covering what is realistic with it. We cover combining gaze and head tracking with a gamepad in hands-free music making.
- The barrier is the DAW interface, not the controller. If the obstacle is reading the screen, no input device fixes it. A screen reader workflow is the answer, which is a separate build covered in our screen-reader-friendly gamepad workflow.
- The person wants to play a conventional instrument. Adapting an acoustic instrument is a real and well-developed field. The OHMI Trust funds and documents one-handed adaptations of orchestral instruments through its biennial competition, and its instrument catalogue covers brass, woodwind, guitar and more. A MIDI gamepad is not a substitute for a playable clarinet if a clarinet is what someone wants to play.
Drake Music is the organisation to know if you want the broader picture. Its technology programme and accessible musical instrument collection document a decade of instruments built with and for disabled musicians, and its links to other accessible music tech is the most useful single index in this field. None of these organisations is affiliated with this product, and nothing here should be read as endorsement by them.
How do you test an XAC MIDI rig properly?
By playing a whole piece of music with it, not by pressing each switch once.
Bench testing proves the wiring. It proves nothing about whether the layout is usable. The problems that sink adaptive rigs are almost all time-dependent: a switch that is fine for ten presses and painful for two hundred, a reach that is comfortable at the start of a session and not at the end, a latch that keeps getting left on because the stop switch is one centimetre too far away.
A reasonable test protocol:
- Build a four-bar loop. Note anything awkward.
- Build an eight-bar arrangement with two sounds and one parameter move.
- Record a complete take of something at least two minutes long.
- Stop and ask the person what annoyed them. Change one thing. Repeat.
Change one thing at a time. Adaptive layouts drift into incoherence fast if you remap three inputs between every take, and the person using the rig has to relearn muscle memory each time you do. Our general mapping templates guide covers saving and versioning layouts so you can roll back a change that made things worse.
What does it cost to build this?
The XAC and switches are the expensive part; the software and the computer side are comparatively cheap.
We are deliberately not quoting hardware prices here, because they vary by region and change constantly — check Microsoft's own page, AbleNet and Logitech directly. What we can say is the shape of the cost: the controller, the switches and the mounting hardware together dominate the budget, and the MIDI side adds one software purchase and whatever DAW you already use. Free DAWs exist and are genuinely capable, and our guides to LMMS and Cakewalk cover two of them.
If cost is the binding constraint, there is also a case for skipping the XAC entirely at the start. A standard controller plus a thoughtful mapping solves a surprising number of access needs for a fraction of the price, and we go through that comparison honestly — including where it falls down — in the cost of accessible music tech.
Who should you talk to before building one of these?
An assessment service, if you can reach one, because they will spot in ten minutes what a guide cannot tell you at all.
SpecialEffect provides free one-to-one assessments, equipment loans and modifications in the UK. AbleGamers in the US runs a peer counselling programme and maintains a public knowledge base including a page on the XAC specifically. OneSwitch.org.uk has archived single-switch and one-handed input techniques for over twenty years, including a music-specific section. For music in particular, Drake Music and the OHMI Trust are the organisations doing the deepest work. We link to all of them because their guidance is better than ours on the questions they specialise in, not because any of them have endorsed this software.
FAQ
Does the Xbox Adaptive Controller work as a MIDI controller?
Yes, with a bridge application in between. The XAC presents itself to macOS, Windows and Linux as a standard Xbox-compatible gamepad, and Universal Controller MIDI reads that gamepad stream and emits virtual MIDI from it. Anything plugged into the XAC jacks arrives as the Xbox input that jack is mapped to, so a switch wired to the A jack becomes whatever you assign the A button to.
How many separate switches can one Xbox Adaptive Controller send to a DAW?
Microsoft documents nineteen 3.5 mm jacks on the rear panel, each corresponding to a different Xbox button, bumper, trigger or d-pad direction, plus two USB-A ports for external joysticks. That is a large number of discrete inputs from one device, and every one of them can carry a separate MIDI note or control change once mapped.
Do I need Pro to use the Xbox Adaptive Controller for MIDI?
No for basic use, yes for custom layouts. The free tier sends notes and control changes from one connected controller through one MIDI port with three saved presets, which is enough to confirm the rig works. The mapping editor is a Pro feature, and custom mapping is the entire point of an XAC rig, so most people building a serious adaptive setup will need Pro.
Can two people set up the controller together?
Yes. The Xbox Adaptive Controller supports a copilot arrangement where a second controller is paired alongside it, which is commonly used so a support worker, family member or teacher can assist during setup without taking the device away from the player. Check the current Xbox support documentation for how copilot behaves on your platform, because the behaviour is defined by Microsoft rather than by the MIDI bridge.
Is the Xbox Adaptive Controller the right choice for every access need?
No. It is designed around switch and joystick inputs, so it suits people who can reliably actuate at least one switch with some part of the body. It does not address needs that are primarily about breath control, sip and puff, eye gaze or speech, and it is not a substitute for an individual assessment. Organisations such as SpecialEffect and AbleGamers assess people one to one and will often recommend something other than an XAC.
Where can I get help choosing and mounting switches?
SpecialEffect in the UK runs free one to one assessments and equipment loans, AbleGamers in the US maintains a public knowledge base and a peer counselling programme, and OneSwitch.org.uk has documented single-switch and one-handed input setups for over two decades. None of these organisations is affiliated with Universal Controller MIDI, but all three publish guidance that applies directly to building an adaptive MIDI rig.
Start with the hardware you already have
If you have an XAC, you already own the hard part. The software side is a download and a mapping session. Download Universal Controller MIDI, plug the controller in, and confirm every switch you have wired registers before you change anything else. Then build the layout around the person, one input at a time.