A DualSense gives you more than twenty-five assignable MIDI controls, but they are not interchangeable. Some are digital switches, some are spring-loaded, some stay where you leave them, and three of them are outputs rather than inputs at all. Mapping a volume fader to a stick feels wrong for a reason, and that reason is mechanical. This is the input-by-input reference: what every physical control on the controller actually produces, what it is genuinely good at, and what to stop trying to make it do.
- Continuous inputs: two analog triggers, two analog sticks, touchpad X and Y, three gyro axes. These are your sweeps.
- Digital inputs: four face buttons, four d-pad directions, L1, R1, two stick clicks, touchpad click, plus the system buttons. These are your notes and state changes.
- Outputs: rumble motors, adaptive trigger resistance, and the light bar — all driven by incoming MIDI, all Pro features.
- Cost: the defaults below work on the free tier. Changing any binding needs the Pro mapping editor at
$89one time.
What does each DualSense input send by default?
Buttons send notes, triggers and sticks send continuous controllers, the touchpad sends an XY CC pair, and the gyro sends three more CCs — all on MIDI channel 1.
| Control | MIDI message | Target |
|---|---|---|
| Cross Note 60 (C3) Drum pad 1, clip launch Digital | ||
| Circle Note 62 (D3) Drum pad 2, stop Digital | ||
| Square Note 64 (E3) Drum pad 3 Digital | ||
| Triangle Note 65 (F3) Drum pad 4, arm Digital | ||
| L1 / R1 Notes 67 / 69 Bank or scene up and down Digital | ||
| L2 trigger CC 1 Filter cutoff, expression Analog | ||
| R2 trigger CC 2 Resonance, drive, send level Analog | ||
| Left stick X / Y CC 3 / CC 4 Bipolar macros, pitch bend Analog, sprung | ||
| Right stick X / Y CC 5 / CC 6 Bipolar macros, pan Analog, sprung | ||
| Touchpad X / Y CC 16 / CC 17 XY morph pad Analog, absolute | ||
| Touchpad click Separate button Latch, snapshot, tap tempo Digital | ||
| Gyro pitch / yaw / roll CC 20 / 21 / 22 Gestural FX intensity Analog, drifting | ||
| D-pad Notes 78–81 Navigation, preset step Digital | ||
- Notes 60-65
- Notes 78-81
- Note 67
- Note 69
- CC 1
- CC 2
- CC 3 / 4
- CC 5 / 6
- CC 16 / 17
Those are the stock bindings. They exist so something audible happens the moment you finish the first-run wizard, and they are the same on the free tier as on Pro. Changing them — putting a trigger on CC 74 for a filter cutoff, say — requires the mapping editor, which is a Pro feature. The broader setup context for all of this is in how to use a PS5 controller as a MIDI controller.
What are the face buttons and d-pad good for?
Note triggers — drum pads, clip launches, scene fires, keyswitches — and nothing that needs a continuous value.
Cross, Circle, Square, and Triangle are plain digital switches. There is no pressure sensing in them, which has one consequence worth being blunt about: they cannot generate real velocity. Every hit comes out at the same fixed velocity unless something else varies it. If you want dynamics from finger drumming, the standard approach is to hold a trigger as a velocity modifier while you hit the pad, so L2 position scales the velocity of the next note. That is a mapping-editor behaviour, so it is Pro territory.
The d-pad on a DualSense is four separate switches in a cross arrangement rather than a single rocker, so diagonals register as two simultaneous presses. That makes it excellent for navigation — preset up and down, track left and right, scene stepping — and poor for anything where an accidental diagonal would fire a wrong note. Keep notes on the face buttons and keep the d-pad for moving around.
Good for: drum pads, clip launch, transport, keyswitches, navigation. Bad for: anything expressive, anything continuous, anything where a fixed velocity sounds mechanical.
What about L1 and R1?
They are digital shoulder buttons, which makes them ideal modifier keys rather than musical inputs.
The most valuable job for L1 and R1 is not sending a note at all — it is acting as a shift layer so the rest of the controller does two different things depending on whether a shoulder is held. Hold L1 and the face buttons become scene launches instead of drum pads. That doubles your usable surface without adding hardware, and it is how most serious gamepad mappings get past the "I have run out of buttons" wall. Layered bindings live in the mapping editor, so again, Pro.
On the default free mapping they send notes 67 and 69, which works fine as bank up and bank down.
Which DualSense input is best for expression?
The two analog triggers, L2 and R2 — by a wide margin.
They are the only inputs on the controller with long analog travel that stays put. Press a trigger halfway and let your finger rest; the value holds. That single property is what makes them the right home for filter cutoff, send level, drive amount, expression, crossfade position, or anything else you want to set and sustain. The sticks cannot do this because they spring back. The touchpad cannot do this while your finger is off it.
Triggers are also the controller's only inputs that work in both directions. The adaptive trigger motors inside L2 and R2 can push back under MIDI control, which means the same physical control that is sending your filter sweep can simultaneously be resisting your finger in time with the kick drum. There are three modes — continuous resistance, section resistance over a defined travel range, and vibration between 1 and 40 Hz — and the bridge writes to the trigger over HID at 100 Hz, giving roughly 10 ms of internal jitter. That is fast enough that the sensation feels glued to the audio rather than trailing it. The full treatment is in PS5 adaptive triggers as MIDI haptic feedback.
Good for: filter cutoff, expression, send level, crossfade, velocity modifiers, anything you want to hold. Bad for: fast repeated triggering — the travel is long and your finger will tire.
What are the analog sticks actually good at?
Bipolar parameters that should return to zero when you let go — and badly suited to anything you want to set and leave.
A stick is spring-centred. That is a mechanical fact and it determines everything about where a stick belongs in a mapping. Release it and the value snaps to the middle. If you have mapped a channel fader to a stick, releasing it jumps the fader to 50% and you have just ruined the take. If you have mapped pitch bend to a stick, releasing it returns the pitch to centre, which is exactly what pitch bend should do.
So the rule is: sticks for things that have a natural neutral. Pitch bend, modulation depth that should relax, pan offset, a filter that should spring back, a vibrato amount, a morph that should return to the source. Four axes of that, plus two clicks, from inputs you can operate without looking.
Two practical notes. First, worn DualSense sticks drift — they send small non-zero values with nothing touching them — and the fix is a wider deadzone rather than new hardware. Second, both sticks also click, giving you L3 and R3 as two extra digital buttons that are easy to hit without moving your thumbs. Tap tempo and panic-stop are both good homes for a stick click, because you will never press one by accident during a sweep.
Good for: pitch bend, bipolar modulation, pan, anything that should recentre. Bad for: volume, absolute level, any set-and-forget value.
How good is the touchpad as a MIDI surface?
It is the most expressive surface on the controller — a genuine Kaoss-pad-style XY control that most people leave bound to nothing.
The DualSense touchpad reports raw coordinates across a 1920 × 1080 grid, which the bridge scales down to the MIDI range of 0–127. After scaling you get roughly 256 effective steps per axis, finer resolution than the sticks give you. Unlike a stick, it is an absolute surface: your finger position is the value, not a displacement from centre.
The classic binding is filter cutoff on X and resonance on Y, which under the General MIDI 2 convention means CC 74 and CC 71:
{
"touchpad": {
"mode": "xy",
"x": { "type": "cc", "cc": 74, "channel": 1, "range": [0, 127] },
"y": { "type": "cc", "cc": 71, "channel": 1, "range": [0, 127], "invert": true }
}
}Knowing where the corners land makes tuning ranges much easier:
| Finger position | Raw X | Raw Y | CC value with Y inverted |
|---|---|---|---|
| Top-left | 0 | 0 | X = 0, Y = 127 |
| Top-right | 1919 | 0 | X = 127, Y = 127 |
| Centre | 959 | 540 | X = 64, Y = 64 |
| Bottom-left | 0 | 1079 | X = 0, Y = 0 |
| Bottom-right | 1919 | 1079 | X = 127, Y = 0 |
The one thing to internalise: the touchpad click is a separate button. Touching the surface sends position; pressing it down sends a distinct digital event. They do not fire together and they can be bound to different things — position to a morph, click to latch that morph in place. A deeper walkthrough of the surface, including gating a held note on touch-start so the sound only exists while your finger is down, is in the DualSense touchpad XY guide.
Good for: two-dimensional morphs, filter sweeps, send pairs, gestural texture. Bad for: precise repeatable values — you cannot see where your finger is.
Is the gyro usable for MIDI?
Yes, with calibration, and it is the input most likely to need re-zeroing partway through a session.
The DualSense exposes three motion axes — pitch, yaw, and roll — which default to CC 20, CC 21, and CC 22. Before using them, rest the controller flat on a table and run the gyro calibration so all three start centred. Without that step the axes begin at whatever arbitrary orientation the controller happened to be in, and your parameter starts at a random value.
The honest caveat: gyros drift. Over a long session the zero point wanders, so a parameter you left alone will slowly creep. Re-calibrating during a break fixes it. Sony's gyro is also tuned for fine aiming in shooters, which makes it quick but a touch jumpy for musical use — smoothing on the binding helps, and smoothing is a Pro mapping-editor setting.
Good for: gestural FX intensity, performance moments where the audience can see the movement, theremin-style wobble. Bad for: anything that must stay still, and anything you are recording as automation without cleanup.
What about the microphone and the speaker?
Neither is a MIDI input. They are audio devices, and they sit outside the controller-to-MIDI path entirely.
The DualSense has a built-in microphone and a small speaker in the body. The bridge maps physical controls to MIDI messages; it does not route audio. If you want the microphone doing something musical, that is a separate audio-input problem — the controller presents as a normal audio device to your operating system over USB, and anything you do with that signal happens in your DAW, not in the mapping. We cover one approach to that separately in the DualSense microphone pitch detection guide, but it is a different pipeline to everything on this page.
Which DualSense features are outputs, not inputs?
Three — the rumble motors, the adaptive trigger resistance, and the light bar. All are driven by MIDI coming back from your software, and all are Pro features.
- Rumble motors. Two of them, driven from incoming note or CC data. The obvious use is feeling the kick drum in your hands while monitoring quietly, which is genuinely useful backstage or in a shared room.
- Adaptive triggers. Covered above — resistance that changes in response to what your DAW is doing. Map it to a compressor's gain reduction and the trigger gets heavier as the mix ducks.
- Light bar. The RGB strip either side of the touchpad, drivable from CC values. Useful as a visual state indicator — which bank you are on, whether you are armed — and worth keeping subtle in a live set so it does not strobe at the audience.
Bidirectional mapping is what separates a gamepad from a one-way controller, and the full pattern is laid out in bidirectional MIDI with haptic rumble and adaptive triggers.
What is the sensible way to lay all of this out?
Put notes on the digital inputs, sweeps on the triggers and touchpad, recentering parameters on the sticks, and navigation on the d-pad.
That single sentence resolves most mapping arguments. The shape of the hardware tells you where things belong: anything that must hold a value goes on a trigger, anything that must return to neutral goes on a stick, anything two-dimensional goes on the touchpad, and anything binary goes on a button. Fight that and you will spend your session working around the controller instead of playing it.
The stock mapping follows those rules already, which is why it is worth living with for a week before changing anything. When you do want to change it, the mapping editor, per-binding curves, and layered shift states are in Pro at $89 one time, two machine seats, and free major upgrades. Download the free build first and find out where it actually gets in your way.
FAQ
Which DualSense inputs are analog and which are digital?
Only the two triggers, the two analog sticks, the touchpad position, and the three gyro axes produce continuous values. The face buttons, d-pad, L1, R1, the stick clicks, the touchpad click, and the system buttons are all on-off digital inputs.
Can DualSense face buttons send MIDI velocity?
Not from the button itself, because the face buttons are digital switches with no pressure sensing. They send a fixed velocity, and the usual workaround is to hold a trigger as a velocity modifier while you hit the pad.
What is the best DualSense input for filter sweeps?
The analog triggers. They have long travel, they stay where you leave them rather than springing back to centre, and they are the most controllable expressive input on the controller.
Why are the analog sticks bad for volume faders?
Because they are spring-centred. Let go and the value snaps back to the middle, which is right for pitch bend or a bipolar modulation amount but wrong for anything you want to set and leave.
Does the DualSense touchpad click fire when you touch it?
No. The click is a separate digital button underneath the surface, so touching the pad sends position data while pressing it sends a distinct button event. They can be bound to different things.
Can the DualSense light bar and haptics be driven from my DAW?
Yes, but it is a Pro feature. Incoming MIDI can drive the rumble motors, the adaptive trigger resistance, and the light bar colour, which turns the controller into a feedback surface as well as an input device.