Blog Hardware 8 min read

Polyend Tracker — Gamepad Step + Envelope Control

Drive Polyend Tracker step entry and FX columns from a gamepad. Full CC map for the envelope columns, per-track CC banking, and pattern jumps.

By Aidxn Design

The Polyend Tracker is what happens when someone reads the source code of FastTracker 2 and decides it deserves a hardware shell with a battery. Sixteen steps per row, eight tracks, an FX column per step, and a single rotary encoder that wants to be ten encoders. The polyend tracker gamepad workflow through Universal Controller MIDI hands you proper analog control over the FX columns and step velocity without breaking the Tracker's keep-the-screen-busy ergonomics.

TL;DR
  • What you do: bridge a gamepad to the Tracker over USB, send CC into the active step's FX column.
  • What you need: Polyend Tracker or Tracker Mini, gamepad, laptop, USB-C cable.
  • Killer feature: per-track CC banking via L1/R1 — eight tracks, eight CC sets.
  • Time: 15 minutes including the per-track bank setup.

Why a gamepad fits the Tracker workflow

The Tracker is a step sequencer with a screen. Step selection happens on the grid; FX entry happens through the rotary or via numeric entry. The single encoder is the bottleneck — every parameter sweep means scrolling a list and rotating. A gamepad bypasses that. Both sticks send CC straight into the FX column of the currently selected step, two shoulder triggers handle velocity, and the d-pad steers the cursor faster than the Tracker's own jog wheel can manage.

The MIDI implementation that matters

The Polyend Tracker has had a slightly inconsistent MIDI implementation across firmware versions. The 1.7.x release fixed the FX column CC handling so external CC writes a value into the FX column of whichever step the cursor sits on. That is the killer move — every step on the grid is an independently addressable target. The Polyend Tracker manual lists the active FX numbers per firmware build; print the CC table and tape it to the back of the Tracker.

Gamepad inputTracker targetMIDI message
Left stick XFX column — filter cutoffCC 74, channel 1
Left stick YFX column — filter resonanceCC 71, channel 1
Right stick XFX column — pan positionCC 10, channel 1
Right stick YFX column — sample tuneCC 21, channel 1
L2 triggerStep velocityCC 11, channel 1
R2 triggerFX value (active FX type)CC 70, channel 1
D-pad up/downStep cursor up/downNote 60/61, channel 16
D-pad left/rightTrack scroll left/rightNote 62/63, channel 16
L1 / R1Switch CC bank (track 1–8)internal bridge action
Cross (A)Trigger active stepNote 36, channel 1

Per-track CC banking

Eight tracks, one set of sticks. The bridge solves that with a bank system: L1 and R1 cycle the active bank, and each bank stores a different CC table. Bank 1 drives track 1's FX column, bank 2 drives track 2's, and so on. Visual feedback on the bridge UI shows which bank is active. The Tracker itself does not need to know — the bridge just sends the right CCs at the right time.

# bridge preset — polyend-tracker.toml
[preset]
name = "Polyend Tracker — 8 track CC banks"
device = "tracker"
banks = 8

[bank.1]
label = "Track 1 — kick"
[bank.1.binding.left_stick]
cc_x = 74    # cutoff
cc_y = 71    # resonance
[bank.1.binding.right_stick]
cc_x = 10    # pan
cc_y = 21    # tune

[bank.2]
label = "Track 2 — snare"
# inherits binding structure, change CC numbers per track preference

[modifier]
L1 = "bank_prev"
R1 = "bank_next"

Step-by-step setup

1. Tracker side — enable USB MIDI

Shift + Menu, Config, MIDI. Set MIDI IN to USB, RX CHANNEL to 1, RX TRANSPORT to ON if you want the Tracker to follow gamepad-driven MIDI clock from the bridge. Save the config — it persists across reboots, which the older 1.4 firmware did not always honour.

2. Bridge side — channel 1 with channel 16 for navigation

The bridge needs to send the FX CCs on channel 1 (synth side) but the d-pad navigation notes on channel 16 (so they don't accidentally trigger a sample). Right-click each d-pad binding in the bridge mapping editor and set the channel override.

3. Test the FX column write

Select an empty step on track 1. Wiggle the left stick. The FX column should populate with a filter cutoff value that updates live. If nothing happens, the Tracker is not in the right RX mode — check that the active step is selected (highlighted) and that the track is not muted.

Live performance patterns

  • One-finger filter sweep across all steps. Hold Square (a "global" modifier in the bridge) and the left stick writes the same cutoff value to every step on the active track. Drop the modifier and it goes back to per-step writes.
  • Pattern jumps. Bind Shift + d-pad right to a Program Change. PC 0–127 jumps the Tracker between patterns. Great for transitions when you have multiple variations queued.
  • Quick humanise. R2 sends a slightly randomised value to the FX column on each press. Three taps and the step velocities now feel handmade.
  • Tap tempo into the Tracker. Bind the touchpad click to drive MIDI clock — the bridge exposes a tap-tempo input that becomes the master clock the Tracker follows.

What the Tracker will not do

It will not accept CC writes when no step is selected — the cursor has to be on a step. It will not respond to MPE or 14-bit CC. And the firmware-listed CC mapping changes between versions; the Mini and the full Tracker also occasionally diverge by a CC number or two. Test before the gig.

Related rigs

For a deeper dive on hardware synths plus USB host quirks, read gamepad to hardware synth via USB host. For a pure finger-drumming workflow that pairs with the Tracker, see beat making with a PS5 controller. And for tempo control, tap tempo MIDI clock from gamepad buttons covers the master clock chain.

The Polyend Tracker rewards anyone who learns its grid muscle memory. The bridge rewards the rest of you who want the Tracker plus eight analog hands.

Keep reading

More setup walkthroughs