Steam Deck Trackpads as MIDI XY Pads

The Steam Deck has the richest input surface of any controller in this category and almost nobody uses it for music. Two capacitive trackpads, four back grips, two analog sticks, two analog triggers, a gyro, and a full Linux desktop that can run the bridge and the DAW on the same device. The trackpads alone make it more interesting than any console pad, because a trackpad does something a stick fundamentally cannot: it stays where you put it.

Why does the Steam Deck controller not reach my MIDI bridge?

Because Steam Input grabs the Deck's built-in controls at the system level whenever Steam is running, and it does not share.

This is the first wall everyone hits and it looks like a broken bridge. The Deck's controls work perfectly in every game, the bridge lists no controller, and nothing you do in the bridge changes it — because the input never gets that far. Steam sits between the hardware and every other application on the system, translating the Deck's native inputs into whatever the current layout says they should be.

Two ways out, both in Desktop Mode:

• Quit Steam entirely. Blunt and completely effective. In Desktop Mode, right-click the Steam tray icon and quit. The Deck's controls fall back to their raw kernel driver and the bridge sees them.
• Add the bridge to Steam and give it a gamepad layout. Add the AppImage as a non-Steam game, launch it through Steam, and set its controller layout so the inputs arrive as a standard gamepad rather than as mouse and keyboard emulation. More fiddly, but it keeps Steam running.

Note that the trackpads default to mouse emulation in Desktop Mode, which is exactly what you do not want — a trackpad acting as a mouse sends pointer movement, not coordinates. Quitting Steam clears that too.

If you have not got the Linux build installed yet, the SteamOS install guide covers the AppImage and the immutable filesystem side; this post picks up once it is running.

Can the Steam Deck trackpads be used as MIDI XY pads?

Yes, and this is the single best reason to use a Deck for music — each pad is a capacitive absolute-position surface, so touching a corner jumps the value to that corner.

The difference from a stick is not a detail, it is a category change. An analog stick reports deflection from a spring-loaded centre: you push, the value moves, you let go, the value snaps back to 64. That is correct for a pitch bend and wrong for everything else. A trackpad reports where your finger is, and when you lift your finger the last position stays. That is how a Kaoss Pad works, how an XY plugin pad works, and how your brain expects a two-dimensional control to behave.

Set both pads to absolute mode in the bridge:

Surface	Axis	MIDI	Good destination
Left trackpad	X	CC 16	Filter cutoff
Left trackpad	Y	CC 17	Resonance
Left trackpad	Click	Note 88	Latch — freeze the current XY value
Right trackpad	X	CC 18	Delay time
Right trackpad	Y	CC 19	Feedback
Right trackpad	Click	Note 89	Effect on/off

The clicks matter more than they look. Both trackpads press in as buttons, which gives you a free "commit" gesture — slide to a position, click to latch, lift your finger. Without a latch you have to keep a finger down to hold a value, and you only have so many fingers. The same pattern works on the DualSense touchpad and is covered in the touchpad XY guide, but the Deck has two of them.

How do you stop a trackpad jumping when you first touch it?

Decide deliberately between absolute and relative mode per pad, because the right answer depends on the parameter, not on the hardware.

Absolute mode means the value snaps to wherever your finger lands. For a filter XY pad this is what you want — it is a performance gesture and the jump is the point. For a mix send it is a disaster, because a careless touch on the edge of the pad sends a reverb from 0 to 100 instantly.

Relative mode means your finger's movement nudges the value from wherever it already was, like a trackpad moving a mouse pointer. No jump, no accidents, and no ability to leap across the range in one gesture.

The practical split: left pad absolute for performance sweeps, right pad relative for anything you are setting rather than playing. If you need absolute behaviour without the jump risk, set a soft takeover so the value only starts following your finger once the finger position crosses the current value — the bridge's pickup mode does this, and it is the same mechanism a hardware mixer uses when you load a new scene.

What should the four back grips do?

Modifiers and mode switches — not notes — because they sit under fingers that are otherwise doing nothing and because they are awkward to hit rhythmically.

Grip	Finger	Suggested job
L4	Left middle	Hold-to-shift — second note layer on every face button
R4	Right middle	Hold to swap both trackpads to a second CC bank
L5	Left ring	Bank down / previous scene
R5	Right ring	Panic — all notes off

The R4 binding is the one worth building a rig around. Two trackpads give you four CCs; two trackpads plus a bank modifier give you eight, and because the modifier is held rather than toggled there is no mode you can get stuck in. Conditional bindings like these are a Pro-tier feature, as is the per-binding smoothing you will want on the gyro.

What not to put on the grips: anything that has to land on a beat. The grips are stiff, the finger positions are unusual, and you will be late. Keep rhythmic playing on the face buttons and the triggers.

Does the gyro add anything the trackpads do not?

One thing: a continuous value you can change without using a finger, which matters when both thumbs and both index fingers are already committed.

Tilting a Steam Deck is a bigger, slower gesture than tilting a Joy-Con because the thing weighs considerably more, and that is an advantage for musical use — large slow movements are easy to control and hard to do by accident. It is a bad home for anything sharp and a good home for a long filter drift, a reverb size, a grain density.

The three settings are the same as any gyro rig: smoothing to kill sensor noise, a dead band around the rest position so holding still holds the value, and a bound recentre so integration drift never strands a parameter. The reasoning behind each is laid out in the Joy-Con motion guide and applies identically here.

Can the Deck run the bridge and the DAW at once?

Yes — Desktop Mode is a full KDE Plasma Linux desktop, so the bridge opens an ALSA virtual port and any Linux DAW on the machine can take it as an input.

# confirm the bridge's ALSA MIDI client is present
aconnect -l

# connect the bridge client to your DAW's input client
aconnect :0 :0

Ardour, Reaper's Linux build and Bitwig all run on SteamOS and all take ALSA MIDI input. The constraint is not the MIDI side, it is the handheld — you are running a DAW, a bridge and a desktop on a battery-powered device with a small screen. For writing on a train it is remarkable. For a session you intend to finish, plug into a dock and a real screen, or run the Deck purely as the control surface and let a laptop do the work. The ALSA and JACK routing details are covered properly in the Ardour on Linux guide.

Troubleshooting

• Bridge sees no controller. Steam Input has it. Quit Steam in Desktop Mode or set a pass-through layout.
• Trackpads move the mouse pointer instead of sending CC. Same cause — Steam's desktop layout maps them to mouse emulation.
• No MIDI client in aconnect -l. The virtual port failed to open. Relaunch the bridge from a terminal and read the output.
• AppImage will not run. Mark it executable with chmod +x. SteamOS's root filesystem is immutable, so do not try to install a system package.
• Trackpad value jumps on first touch. That is absolute mode working as designed. Switch to relative or enable pickup mode for that binding.
• Gyro drifts over a long set. Bind a recentre button and use it between sections.
• Everything resets after a SteamOS update. Keep the AppImage and your exported presets in your home folder, which survives updates; the system partition does not.

Frequently asked questions

Why does the Steam Deck controller not reach my MIDI bridge?

Steam Input claims the built-in controls system-wide whenever Steam is running, so the bridge receives nothing until you quit Steam in Desktop Mode or set a controller layout that passes raw input through.

What is the difference between the Steam Deck trackpads and an analog stick for MIDI?

A stick reports a position relative to a spring-loaded centre and snaps back when released, while a trackpad reports an absolute finger position and holds the last value, which makes the trackpad behave much more like a real XY pad.

Do the Steam Deck back grips send separate inputs?

Yes, L4, R4, L5 and R5 are four distinct buttons on the back of the Deck, which makes them ideal homes for modifiers and shift layers because they sit under fingers that are doing nothing else.

Does the Steam Deck have a gyroscope for MIDI?

Yes, the Deck includes an inertial sensor, and it works as a continuous MIDI source once you add smoothing and bind a button to recentre the orientation reference.

Can a Steam Deck run the DAW and the bridge at the same time?

Yes in Desktop Mode, since SteamOS is a full Linux desktop, though the practical limit is how much a handheld can run at once rather than anything about the MIDI side.

Two XY pads in a bag you already carry

Strip away the gaming and a Steam Deck is a battery-powered Linux computer with two absolute XY surfaces, four grip buttons, two analog triggers and a gyro. That is a more capable control surface than most dedicated MIDI hardware under a few hundred dollars, and the only thing standing between you and it is remembering to quit Steam.

Download the Linux build, drop into Desktop Mode, and put a filter under each thumb.