Use a PS5 or Xbox Gamepad as a Logic Pro Control Surface

Apple sold the Logic Remote iPad app, killed Logic Control hardware, and left Logic users with a weird gap where a tactile control surface should be. If you have a PS5 DualSense or an Xbox Series controller sitting in a drawer, you already own the fix. This guide turns either pad into a fully native Logic Pro control surface — transport, smart controls, plugin macros, channel sends — without buying a single piece of dedicated hardware.

Why use a gamepad in Logic Pro

Logic's Controller Assignments engine is one of the most flexible mapping systems in any DAW — it just needs MIDI to feed it. Once a gamepad shows up as a virtual port, Logic treats it exactly like a Mackie Control or a Native Instruments Komplete Kontrol. You get sixteen tactile inputs, two analog sticks for two pairs of continuous CCs, two analog triggers for filter or send rides, and a touchpad for XY automation. That is more usable surface than the Logic Remote iPad app, with zero subscription, zero second screen, and zero Wi-Fi flakiness.

The other quiet win: gamepads have haptics. Adaptive triggers on the DualSense and the rumble motors on both controllers can be driven back from Logic for tactile feedback on transport and tempo. Universal Controller MIDI handles both directions.

What you'll need

• Universal Controller MIDI v1.0 or later (download here)
• Logic Pro 10.7.5 or later (10.8 recommended for the updated Controller Assignments UI)
• macOS 12 Monterey or newer — the bridge needs Core MIDI and the modern HID stack
• A PS5 DualSense, DualSense Edge, or Xbox Series controller — wired USB-C strongly preferred for tracking sessions
• A USB-C cable that carries data (charge-only cables will pair but not enumerate)

Step-by-step setup

1. Install and plug in

Run the installer, launch Universal Controller MIDI, plug the gamepad in. The status pill flips green and the live input preview lights up as you press buttons. Confirm Core MIDI sees the virtual port:

# macOS — list every MIDI source and destination
system_profiler SPAudioDataType | grep -i midi
# Or the more direct check
midiclient -l 2>/dev/null || echo "use Audio MIDI Setup to verify UCMIDI Out is listed"

2. Bring the IAC Driver online

Open Audio MIDI Setup (Cmd-Space, type it). Window → Show MIDI Studio → IAC Driver → Device is online. Add a port called UCMIDI Out if one is not already there. Logic refuses to see virtual buses that are flagged offline, so this is the single most common setup gotcha.

3. Register the controller as a Control Surface

Launch Logic Pro. Go to Logic Pro → Settings → Control Surfaces → Setup. New → Install…, then pick Mackie Control for the cleanest fader/transport behaviour, or the dedicated UCMIDI device class shipped with the bridge for native button labels. Assign Input port and Output port to Universal Controller MIDI.

4. Map smart controls with Controller Assignments

Open Logic Pro → Settings → Controller Assignments. Expert View, switch on Learn Mode (Cmd-L). Click any on-screen knob — smart control, channel strip pan, plugin parameter — then move the gamepad input you want to bind. Logic captures the assignment, including channel and CC, into the active zone. Turn off Learn Mode when done so you do not accidentally rebind on touch.

5. Save as a template

File → Save as Template… with a name like UCMIDI Default. Every new project starts with the surface registered, which means you never re-do this on song two.

Like the workflow already? Get Pro for $49 — one-time, owned forever. Unlocks unlimited preset slots, the Logic Remote Script bundle, and adaptive trigger output.

Mapping ideas that ship

• Triggers ride the focused plugin's two macros. L2 to filter cutoff, R2 to resonance. Works in Alchemy, Surge XT, Serum, Pigments, anything with macro slots.
• Right stick is XY automation. Map X to send 1, Y to send 2 — instant wet/dry sweeps without reaching for the mouse.
• D-pad navigates the marker track. Bind to the Logic key commands Go to Next Marker / Go to Previous Marker. Mixing 90-minute film cues is suddenly tolerable.
• Face buttons trigger Drummer fills. In a Drummer track, MIDI-learn the cross/circle/square/triangle buttons to the four fill intensity buttons. Live arrangement becomes a thumb game.
• Touchpad as a Logic Pads instrument trigger. Bind CC 16/17 to two on-screen Logic Pads X/Y axes for chord-pad performance.

Gotchas

• Logic ignores the new port until you relaunch. Core MIDI's port table is read once at startup. Quit Logic, confirm UCMIDI Out is online, relaunch.
• Controller Assignments will not capture if Learn is off. Obvious in hindsight, painful when you spend ten minutes wiggling sticks at a frozen UI.
• Mackie Control mode steals transport. If you registered as Mackie Control, the bridge's transport CCs will conflict with Logic's auto-assigned transport. Pick one — either delete the Mackie surface or unassign the bridge's transport keys in the editor.
• Bluetooth latency in Logic is real. Tracking with a DualSense over Bluetooth adds 8–14 ms which Logic will not compensate for. Wire it.

Wrap-up

Logic's Controller Assignments engine has always been better than the hardware Apple ships for it. A gamepad bridged through a virtual MIDI port gives you the surface Apple never built — sixteen tactile inputs, two analog sticks, two analog triggers, a touchpad XY pad, and haptic feedback, all for the cost of the controller you already own. The official Logic control surface docs are worth a skim once you start customising the deeper Mackie zones.

Download Universal Controller MIDI and your DualSense is part of the Logic mix in ten minutes flat.