Cubase's Quick Controls system is the cleanest mapping engine Steinberg ever built — eight slots per track and per VST, each one mappable to any incoming MIDI CC. Pair that with a DualSense or Xbox controller and you get a tactile mixing surface that costs nothing more than the controller already in your drawer. This guide walks through the Cubase gamepad MIDI controller setup from a cold install to a stick driving a UAD plugin's macro slot.

TL;DR

What you do: bridge the gamepad to virtual MIDI, add a Generic Remote in Cubase, point it at the bridge, then assign Quick Controls.
What you need: Cubase 12+ or Nuendo 12+, macOS 12+ or Windows 10+, a DualSense or Xbox controller, Universal Controller MIDI v1.0+.
Time: 10 minutes from install to a stick driving track pan and the Track Quick Controls 1–4.
Cost: the controller you already own. Bridge free to try, $49 for Pro.

Why use a gamepad in Cubase or Nuendo

Cubase splits its automation into Track Quick Controls (eight slots per track, perfect for mix moves) and VST Quick Controls (eight slots that follow the focused plugin, perfect for synth performance). Both are CC-mapped from the same Generic Remote layer, which means a DualSense bridged into virtual MIDI plugs straight in — and Cubase treats it identically to a Faderport or an Avid Artist Mix.

Nuendo users get the same workflow, plus the Control Room monitor mix is mappable from the d-pad — solo, mute, and dim from a thumb instead of a mouse trip.

What you'll need

Universal Controller MIDI v1.0+ (download)
Cubase 12+ or Nuendo 12+ (Pro, Artist, or Elements with MIDI input)
Windows 10+ or macOS 12+
A PS5 DualSense, DualSense Edge, or Xbox Series controller
USB-C data cable — wired strongly preferred for tracking

Step-by-step setup

1. Install and pair

Run the installer, launch the bridge, plug in the controller. On Windows accept the driver-signing prompt for the kernel-level virtual MIDI port. On macOS drag the app to Applications and launch.

2. Enable the virtual MIDI port

macOS: Audio MIDI Setup → Window → Show MIDI Studio → IAC Driver → Device is online. Windows: skip. Confirm UCMIDI Out appears in the Core MIDI / Windows MIDI device list.

3. Load the Cubase preset

Bridge UI: Presets → Cubase (default). Sticks send CCs 74, 71, 75, 76 (the Cubase-default Quick Control CCs). Triggers send CC 11 (expression) and CC 1 (mod). Face buttons send transport notes 60–63. Touchpad sends CC 16/17.

4. Add a Generic Remote

Cubase: Studio → Studio Setup → + → Generic Remote. MIDI Input: Universal Controller MIDI. Click Import and pick the UCMIDI-Cubase.xml file in the bridge's installer folder (/Applications/Universal Controller MIDI.app/Contents/Resources/RemoteScripts/ on macOS or C:\Program Files\Universal Controller MIDI\RemoteScripts\ on Windows). The Quick Control bindings populate the Generic Remote table.

5. Bind plugin parameters to Quick Controls

Open any plugin (Steinberg's Frequency 2, a UAD device, a third-party VST). Right-click any parameter, pick Add to Quick Controls. The next available VST Quick Controls slot takes the parameter, and whichever bridge input was mapped to that slot now drives it.

6. Save as a template

File → Save as Template. New songs boot with the Generic Remote registered and the standard Track Quick Controls bindings in place.

Like the workflow? Get Pro for $49 — one-time, owned forever. Pro unlocks unlimited bridge presets, the Nuendo Control Room script, and adaptive trigger feedback for transport states.

Mapping ideas that ship

Triggers ride the focused plugin's two most-used parameters. Filter cutoff and resonance on Steinberg Padshop, or wet/dry on Frequency 2's mid-side bands.
Left stick = Track Quick Controls 1 and 2. Map slot 1 to track pan, slot 2 to track send 1. Two thumb axes for spatial mixing.
Right stick = VST Quick Controls 1 and 2 on the focused plugin. Follows whatever you click on, so a single stick becomes a per-plugin macro pair.
D-pad as marker nav. Bind to Locate Next Marker / Locate Previous Marker via Cubase Key Commands.
Face buttons for Cycle / Record / Play / Stop. Faster than mousing to the transport bar during a tracking session.

Generic Remote XML snippet

<!-- UCMIDI-Cubase.xml — Track Quick Controls 1–4 from sticks -->
<binding>
  <source channel="1" type="cc" value="74"/>
  <target device="Quick Controls" parameter="QuickControl 1"/>
</binding>
<binding>
  <source channel="1" type="cc" value="71"/>
  <target device="Quick Controls" parameter="QuickControl 2"/>
</binding>

Gotchas

Generic Remote does not see the port until Cubase is restarted. Cubase reads the MIDI device list once on launch. Quit, confirm the bridge is running, relaunch.
Quick Controls do not respond on a fresh track. Track Quick Controls inherit from the project preset — check Project → Project Setup → Track Quick Controls defaults if a new track ignores the stick.
Stick-jump on plugin focus change. Enable Soft Takeover in the Generic Remote settings so the parameter waits for the stick to cross its current value before re-engaging.
Adaptive triggers stay limp. Confirm output port is set in the Generic Remote and the bridge's Output enabled toggle is on under Settings → MIDI Output.

Wrap-up

Cubase's Quick Controls system was built for tactile mixing surfaces, and a DualSense is one of the densest tactile surfaces ever shipped. Bridge them through virtual MIDI and you have a Faderport-class workflow without the $300 price tag. The Steinberg Generic Remote docs are worth reading once you start customising the XML.

Download Universal Controller MIDI and your DualSense joins the Cubase mix in ten minutes.

Cubase + Nuendo — Quick Controls from a PS5 or Xbox Gamepad