DualSense MIDI Software Compared: What Each Tool Reads

The PS5 DualSense is the most interesting controller ever made as a musical instrument, and most DualSense MIDI software reads it as if it were a 2013 gamepad. Sticks, triggers, buttons, done. That works, it looks like success, and it quietly discards the touchpad, the gyroscope, the adaptive trigger motors, the haptics and the microphone — which is to say, every reason the DualSense is different from the pad it replaced. This comparison is organised around that gap: which tools see the whole controller, which see a subset, and what each missing feature actually costs you musically.

What software turns a PS5 DualSense into a MIDI controller?

Standalone bridges, a Max for Live device inside Ableton, the MIDItrol app on iOS, or an open-source Python project on macOS — and they differ enormously in how much of the pad they can see.

Feature support per each vendor's or project's own published material at time of writing: Pounding Systems, Isotonik announcement, Kaskobi, MIDItrol, taiga696/dualsense-midi, JoyToKey, Bome. "Not advertised" means the vendor does not list it, not that we tested and found it absent. Trademarks belong to their respective owners.

Which DualSense features do most MIDI tools miss?

The touchpad as an absolute XY surface, the gyroscope and accelerometer, adaptive trigger resistance, haptic feedback and the built-in microphone.

The technical reason is worth understanding because it explains the whole table above. Most gamepad software reads controllers through an abstraction layer — SDL's game controller API on desktop, XInput on older Windows tools, or the system's game controller framework. Those abstractions exist to make every pad look the same, which is exactly what a game wants and exactly the opposite of what a musician wants. The standardised layout has slots for two sticks, two triggers, a d-pad and a set of face buttons. It has no slot for a touchpad.

To read the rest, software has to drop below the abstraction to the raw HID report and parse the DualSense's specific byte layout. That is real work, it has to be maintained against firmware revisions, and it differs between USB and Bluetooth. Which is why so few tools do it.

Does the DualSense touchpad work as a MIDI XY pad?

Yes, with software that reads the raw report — the touchpad gives absolute X and Y position, which maps naturally to two continuous CCs.

This is the headline feature and it is worth being specific about why. A stick is relative and spring-loaded: it returns to centre, so it is good for momentary gestures and bad for setting a value and leaving it. The touchpad is absolute and stays where you put it, which is the behaviour of a Kaoss-style XY pad and a completely different musical tool. Put your finger at the top-left and the two CCs jump there instantly, which is a thing no stick can do.

It also supports multiple touch points and a physical click, which gives you an on-off gate underneath the two continuous axes — the classic effect-pad gesture. Our touchpad XY guide builds the mapping, and the Steam Deck trackpad equivalent covers the same idea on different hardware.

Can adaptive triggers respond to MIDI from my DAW?

Yes with software that supports sending data back to the controller, which lets a trigger stiffen, click or buzz in response to a MIDI message.

Almost every tool in this category is one-directional: controller in, MIDI out. The DualSense's trigger motors and haptic actuators require the opposite direction, and they are the least commonly supported feature in the field — note how many cells in the comparison table read "not advertised".

What it buys you musically is feedback you feel rather than hear, which matters most when you cannot look at the screen. A trigger that stiffens as a filter approaches self-oscillation tells your finger where it is. A pulse on the beat keeps you locked without a click track in the monitors. Our adaptive trigger feedback guide and haptic rumble guide cover both directions, and the velocity curve deep dive covers getting the response shape right.

Is there a free way to use a DualSense as a MIDI controller?

Yes — a free tier, a free Max for Live device, and an MIT-licensed Python project, each with different costs attached.

• Universal Controller MIDI free tier. One controller, one virtual port and three saved presets, kept indefinitely. Deliberately limited — multi-controller, OSC, MPE and the full mapping editor are Pro.
• Kaskobi's Max for Live device. Free, but needs Live 10 Suite or Trial (10.1.15+) with Max 8, and the MIDI never leaves Live. See the Max for Live comparison.
• taiga696/dualsense-midi. Free and MIT-licensed, macOS 11 or later, Python with pygame and python-rtmidi. Its own README says it is recommended for learning rather than professional gigs, has no jog wheel support, and explicitly ignores the motion sensors.
• Write your own. Forty lines gets a single axis working. See the open-source survey for the code and the six things that turn forty lines into a project.

Should I connect by USB or Bluetooth?

USB-C for anything timing-critical and for any diagnostic test, with Bluetooth saved for convenience once the mapping is proven.

Two separate reasons. The first is latency — every wireless hop adds some, and it is not constant, which matters more than the average when you are playing rhythmically. The second is feature completeness: the DualSense's report format differs between wired and wireless on some systems, so a feature that appears missing over Bluetooth may be present over USB. Never conclude that software cannot read your touchpad until you have tried it with a cable.

Detail in wired versus Bluetooth for MIDI, Bluetooth latency, and battery life when using the pad as a controller.

What does a mapping that uses the whole controller look like?

Touchpad for absolute two-axis control, triggers for pressure, sticks for momentary modulation, gyro for a gesture, buttons for notes.

The microphone row is genuinely unusual territory and we wrote it up separately in using the DualSense mic for pitch detection. For the full input inventory, every DualSense input itemised is the reference page, and the Ableton walkthrough turns it into a working set.

Is the DualSense actually worth choosing over a cheaper pad?

For musical work, yes — it has more distinct expressive surfaces than any other mainstream controller, and that is the whole reason this comparison exists.

Count what is on it: two analog sticks, two analog triggers with variable resistance, an absolute multi-touch trackpad with a physical click, a six-axis motion sensor, sixteen buttons, a microphone and two haptic actuators. Most dedicated MIDI controllers at twice the price have fewer continuous controls and none of the feedback. The catch, and it is the point of this article, is that you only get that surface if your software reads it.

If the touchpad and motion are not something you will use, a cheaper pad is genuinely the better buy and we would say so — the 8BitDo Pro 2 guide and the Hall-effect stick comparison both cover pads that beat the DualSense on durability or price for a sticks-and-buttons mapping.

How do you tell whether a tool reads the raw report or an abstraction?

Look at its input list for named DualSense-specific controls — if everything is called "button 5" and "axis 2", you are looking at an abstraction layer.

Three tells, in increasing order of reliability:

1. Generic naming. Numbered buttons and axes mean the software is reading a standardised layout and has no model of your particular controller.
2. No touchpad entry. The touchpad is the first thing to disappear when a tool reads through a game-controller abstraction, because the standard layout has no slot for it.
3. The pad is named something generic. If the tool reports "Wireless Controller", "HID-compliant game controller" or "Xbox 360 Controller" rather than "DualSense", it does not know what it is talking to.

There is a second, platform-level tell on macOS. A tool that reads controllers through Apple's modern framework will have requested input monitoring permission on first launch; one that never asked is either using a lower-level path or is about to fail silently. We cover both routes in the GameController framework deep dive and HIDAPI versus the native driver, which is the clearest explanation we have of the trade-off being made under the hood.

None of this means an abstraction-based tool is bad. For sticks, triggers and buttons it is often more robust, because the abstraction handles the per-controller differences for you. It only matters when you want the parts of the controller the abstraction was designed to hide.

How does the DualSense Edge change the picture?

It adds back buttons and adjustable trigger travel on top of everything the standard DualSense does, so any software that reads a DualSense reads the Edge.

The two features that matter musically are the rear buttons and the trigger stops. The rear buttons are the same win as Xbox Elite paddles: extra controls reachable without moving your thumbs, which is where transport and bank-switching belong. The trigger stops are mechanical limiters that shorten the trigger's travel — which, if you have mapped a trigger to a CC, changes the gesture from a long sweep to a short, switch-like press. Neither is a software feature, and both change how a mapping feels.

The Edge also has swappable stick modules, which is the only real answer to stick drift on a pad you use heavily. If your sticks are driving CCs, drift is not a cosmetic problem — it is a constant stream of unwanted MIDI. Our DualSense Edge guide covers the mapping differences, and the drift compensation guide covers the software side for standard pads.

What about the DualShock 4 and other PlayStation pads?

The DualShock 4 has a touchpad and a gyroscope too, which makes it a far better musical controller than its age suggests and a genuinely cheap way in.

What it lacks compared to the DualSense: adaptive trigger resistance, the newer haptic actuators, the built-in microphone, and USB-C. What it has: an absolute touchpad with a click, a six-axis motion sensor, analog triggers and the same button layout. For someone who wants to try touchpad XY control without buying new hardware, a second-hand DualShock 4 is the cheapest entry point in this entire category.

Software support is also broader, simply because the pad has existed for longer — note that Kaskobi's Max for Live device lists PS3 and PS4 pads but not the DualSense. If your decision is partly about which pad to buy, the DualSense versus DualShock 4 comparison works through it properly, and the DualShock 4 setup guide covers the mapping.

FAQ

What software turns a PS5 DualSense into a MIDI controller?

Standalone bridges such as Universal Controller MIDI and Gamepad MIDI from Pounding Systems, a Max for Live device if you work only inside Ableton Live, the MIDItrol app on iOS, or the open-source taiga696/dualsense-midi project on macOS.

Which DualSense features do most MIDI tools miss?

The touchpad as an absolute XY surface, the gyroscope and accelerometer, adaptive trigger resistance, haptic feedback and the built-in microphone — generic HID and XInput paths expose only sticks, triggers and buttons.

Does the DualSense touchpad work as a MIDI XY pad?

Yes, with software that reads the raw controller report, because the touchpad reports absolute X and Y position which maps naturally to two continuous CCs for Kaoss-style control.

Can adaptive triggers respond to MIDI from my DAW?

Yes with software that supports output back to the controller, which lets a trigger stiffen or buzz in response to a MIDI message, though it is the least widely supported feature in this category.

Is there a free way to use a DualSense as a MIDI controller?

Yes — Universal Controller MIDI has a free tier of one controller, one port and three saved presets, Kaskobi publishes a free Max for Live device, and taiga696/dualsense-midi is an MIT-licensed Python project for macOS.

Should I connect the DualSense by USB or Bluetooth for MIDI?

USB-C for anything timing-critical or when testing whether a feature works at all, because wired reporting is more complete and more consistent, with Bluetooth reserved for convenience once the mapping is proven.

The short version

Do not pick DualSense software on whether it "supports the DualSense" — almost everything does, in the sense that sticks and buttons work. Pick it on the three features that separate this controller from every other pad: the absolute touchpad, the motion sensors, and the ability to send feedback back into your hands. Open any tool's input list and look for those by name before you commit.

Download Universal Controller MIDI free, plug in over USB-C, and map the touchpad first — it is the input most software cannot see and the one that changes how you play. Free tier is one controller, one virtual port and three saved presets; Pro is AUD $89 one-time with the mapping editor, multi-controller routing, MPE, OSC and haptic output. Next: the head-to-head against Gamepad MIDI.