Blog Comparison 14 min read

Best Gamepad to MIDI Software: 10 Tools Compared for 2026

Ten tools that turn a game controller into MIDI, compared on platform, controller coverage, maintenance status and price — with primary sources.

By Aidxn Design

Searching for the best gamepad to MIDI software produces a list that is mostly wrong in a specific and predictable way: it mixes tools that read controllers with tools that create MIDI ports with tools that rewrite MIDI, lists archived GitHub repositories next to current commercial products without noting which is which, and quotes prices from whenever the article was written. This is the version we wanted to find: ten tools, each fact taken from the vendor's own site or repository, each category boundary named, and every link below verified to resolve before publication. Yes, we make one of them. We have flagged where the others are better.

TL;DR
  • Standalone cross-platform: Universal Controller MIDI and Gamepad MIDI (Pounding Systems). These are the two real head-to-head options.
  • Ableton-only: Kaskobi's free Max for Live device, or Isotonik's paid Gamepad device. Excellent inside Live, useless outside it.
  • iOS: MIDItrol. The only serious answer, with one significant limitation.
  • Not gamepad tools at all: loopMIDI, Bome MIDI Translator, Camelot, JoyToKey. All good software, all solving adjacent problems.
  • Archived: GlovePIE, MidiHID, midibox360. Still run, nobody is fixing them.

What is the best gamepad to MIDI software?

For a standalone, cross-platform bridge the realistic shortlist is Universal Controller MIDI and Gamepad MIDI from Pounding Systems; for Ableton-only use a Max for Live device; and for iOS it is MIDItrol.

That is three answers because it is genuinely three different questions, and any article giving you one answer has quietly assumed your setup. The rest of this piece is the evidence behind those picks and the reasons the other seven tools in the field do not belong in the same sentence.

The full comparison table

Platform support, category and maintenance status are taken from each project's own site or repository at time of writing.

ToolCategoryPlatformsReads gamepadsEmits MIDIMaintainedPricing model
Universal Controller MIDIGamepad bridgemacOS, Windows, LinuxYesYes + OSCYesFree tier, one-time Pro
Gamepad MIDI (Pounding Systems)Gamepad bridgemacOS, Windows, LinuxYesYesYesOne-time purchase
Gamepad MIDI (Kaskobi)Max for Live deviceWherever Live runsYesInside Live onlyFree downloadFree
Gamepad (Isotonik / User Friendly)Max for Live deviceWherever Live runsYesInside Live onlyYesPaid, one-time
MIDItroliOS appiOS / iPadOSYesYes + OSCLast updated 2021Paid app
Bome MIDI Translator ProMIDI rules enginemacOS, WindowsNoYesYesOne-time licence
CamelotLive performance hostmacOS, Windows, iPadNoRoutes MIDIYesOne-time purchase
loopMIDIVirtual port creatorWindowsNoNo — carries itYesFree
JoyToKeyKeystroke mapperWindowsYesNoYes — v7.4, Oct 2026Shareware
GlovePIEDevice reader + scriptingWindowsYesVia scriptNo — abandonedFree
MidiHIDOpen source, HID to MIDImacOSYesYesNo — archived 2020Free, GPL-3.0
midibox360Open source, PythonWindows, LinuxXbox 360 padsYesNo — archived 2022Free, MIT

Sources, all verified at time of writing: Pounding Systems, Kaskobi, MIDItrol on the App Store, Bome, Audio Modeling, loopMIDI, JoyToKey, GlovePIE preservation repo, MidiHID, midibox360. Trademarks belong to their respective owners.

Why are four of these not gamepad tools?

Because they solve the steps either side of the gamepad problem, and search engines have been merging the categories for a decade.

The chain from a controller to a sound has three links, and every tool in this field occupies exactly one or two of them:

  1. Read the device. Something has to open the HID or game-input stream and interpret it. Gamepad bridges, JoyToKey and GlovePIE live here.
  2. Produce MIDI. Convert interpreted input into note and CC messages with deadzones, curves and debouncing applied.
  3. Carry MIDI to the host. A virtual port. loopMIDI, the macOS IAC Driver and the ALSA sequencer live here.

Bome sits downstream of all three, rewriting MIDI that already exists. Camelot sits downstream again, consuming MIDI into a performance host. Both are strong products in their category and neither will ever see your controller. We cover that boundary at length in the gamepad chain comparison and the Camelot breakdown.

Universal Controller MIDI versus Gamepad MIDI: the real head-to-head

These two are the only standalone, cross-platform, actively maintained, gamepad-native options, which makes them the comparison that actually decides anything.

From Pounding Systems' own product page, Gamepad MIDI runs four controllers simultaneously with per-player mappings, maps sticks, triggers, buttons, d-pad, touchpad, gyroscope and accelerometer, does 14-bit pitch bend on analog axes, ships Drum Kit, Chord Pads, DJ Controller and SWAM templates, includes 30-plus scales and chord types with a keyboard preview, shows real parameter names via device profiles, and creates its virtual MIDI output without a driver install. It runs on macOS Apple Silicon, Windows 10/11 64-bit and Linux. It is a one-time purchase with licences covering up to three machines, and the vendor states there is currently no free trial but they offer refunds if it does not work with your setup.

That is a good product and the feature list is not padding. Two things genuinely distinguish them, and we will name both honestly:

DifferenceUniversal Controller MIDIGamepad MIDI (Pounding Systems)
Try before buyingFree tier — 1 controller, 1 port, 3 presetsNo trial; refund offered instead
Built-in scale and chord engineMapping-level, no 30+ scale libraryYes — 30+ scales and chord types with preview
14-bit pitch bend on axesStandard CC and pitch bendExplicitly advertised
Adaptive trigger haptics back to the padYes (Pro)Not advertised
OSC outputYes (Pro)Not advertised
Preset marketplaceYes — community presetsBundled templates
Simultaneous controllersMulti-controller (Pro)Four, with per-player mappings
Licence coverageOne-time Pro licenceUp to three machines

Feature claims taken from each vendor's own product page at time of writing. Where a row says "not advertised" it means the vendor does not list it, not that we tested and found it absent.

If a built-in scale and chord-generation engine is central to how you want to play — mapping a pad to in-key chords rather than to raw notes — read their page carefully, because that is a real differentiator and we would rather you bought the right tool than the one whose blog you happened to land on. If you want to try before you pay, or you need haptics going back into the controller, or you need OSC as well as MIDI, that is our side of the line.

Is there free gamepad to MIDI software?

Yes — Kaskobi's Max for Live device is free, several archived open-source projects still run, and Universal Controller MIDI has a free tier of one controller, one port and three saved presets.

The free options and what each actually costs you in practice:

  • Kaskobi Gamepad MIDI — a free Ableton Live device. Per the download page it needs Live 10 Suite or Trial (10.1.15+) and Max 8, and lists Xbox One, PS3, PS4, Switch Pro and Saitek X52 Pro support. Cost: it only exists inside Live.
  • Archived GitHub projects — free and sometimes still functional. Cost: no maintainer, and two of the three are explicitly read-only. See the open-source survey.
  • Our free tier — one controller, one virtual port, three saved presets. Cost: it is deliberately not unlimited, and multi-controller, OSC, MPE and the full mapping editor are Pro features.
  • Roll your own — pygame's joystick module plus mido is about forty lines. Cost: you are now the maintainer.

Which tools can actually see a DualSense properly?

Only the ones written after the DualSense existed and specifically for it — everything else sees the subset that looks like an older gamepad.

This is the single most under-reported fact in this category. A DualSense will happily enumerate on any OS as something a generic HID tool can read, which produces a working-looking result with sticks, triggers and buttons. Missing from that result: the touchpad's absolute X and Y, the gyroscope and accelerometer, adaptive trigger resistance, haptic output, and the controller's own microphone. That is more than half of what makes the pad interesting.

Worth reading before you commit to a tool: every DualSense input itemised, how wired and Bluetooth modes differ, and the DualSense-specific software comparison.

Which gamepad to MIDI tools support Linux?

Very few — Universal Controller MIDI and Gamepad MIDI from Pounding Systems both list Linux support, and the archived midibox360 targets it, while loopMIDI, JoyToKey, Bome and Camelot have no Linux builds at all.

If you are on Linux the stack below the application also differs: controllers come through evdev, and MIDI ports come from the ALSA sequencer rather than from a loopback driver you install. We cover both in the evdev bridge guide and the ALSA port guide, and the Ardour mapping guide covers the DAW end.

How do you test any of these in ten minutes?

Install it, map one analog trigger to a filter cutoff, and sweep it — that single test separates a real MIDI chain from a keystroke chain and proves the port is live.

  1. Install the tool and connect the controller over USB, not Bluetooth, for the first test.
  2. Confirm a virtual MIDI port exists at OS level before opening your DAW.
  3. Open the DAW, enable the input, and MIDI-learn one knob to the trigger.
  4. Sweep slowly. Smooth movement means continuous CC. Two jumps means something binary in the chain.
  5. Now press every face button and confirm one message per press, with no repeats.

If any step fails, the missing-port troubleshooter covers the usual causes, and the routing-chain latency guide covers the case where it works but feels wrong.

Why do comparison lists in this category keep getting it wrong?

Because the tools share vocabulary without sharing function, and most lists are assembled from other lists rather than from vendor pages.

Four specific errors turn up again and again, and knowing them makes any list easier to read critically:

  1. Category collapse. A port creator, a translator and a bridge all get described as "MIDI software", so loopMIDI ends up recommended to someone who needs a controller read. loopMIDI cannot read a controller. It was never supposed to.
  2. Stale pricing and stale platform claims. Prices move, platforms get added, products stop being subscriptions. We found one of our own tables carrying an out-of-date pricing model for a competitor while writing this series, and corrected it in the Camelot piece rather than quietly.
  3. Archived projects presented as live. A GitHub link looks identical whether the repository was last touched yesterday or in 2017. Only the archive banner tells you, and lists rarely mention it.
  4. Feature lists copied without checking the controller. "Supports gamepads" and "reads a DualSense touchpad" are very different claims, and the gap between them is most of this product category.

The defence is simple and takes a minute per tool: open the vendor's own page or the repository, find the platform list and the last-updated date, and ignore everything written about it elsewhere.

What should you expect to pay?

Between nothing and roughly the price of a cheap MIDI controller — which reframes the whole question.

The spread across this field is unusually wide for software that does one job. A free Max for Live device costs nothing if you already own Live Suite. An iOS app is a few dollars. The standalone desktop bridges are one-time purchases in the range of a budget hardware controller. A rules engine or a performance host costs several times that, because they are much larger products doing much more.

Three things worth weighing against that:

  • The controller is already paid for. That is the whole economic argument for this category — you are buying software to unlock hardware you own, not buying hardware.
  • One-time beats subscription for live work. Offline activation means a licence check cannot fail on a venue's captive-portal Wi-Fi.
  • A trial or free tier is worth more than a feature list. Ten minutes with the actual software tells you more than any table, including this one.

If you are weighing a bridge against buying a dedicated controller instead, we have written that comparison honestly too — switching from an APC mk2 and DualSense versus Push 3 both conclude that hardware still wins for some jobs, and say which.

FAQ

What is the best gamepad to MIDI software?

For a standalone cross-platform bridge the realistic shortlist is Universal Controller MIDI and Gamepad MIDI from Pounding Systems, for Ableton-only use a Max for Live device such as Isotonik's Gamepad or the free Kaskobi device, and for iOS the practical answer is MIDItrol.

Is there free gamepad to MIDI software?

Yes — Kaskobi's Gamepad MIDI device for Ableton Live is free, several archived open-source projects on GitHub still run, and Universal Controller MIDI has a free tier covering one controller, one port and three saved presets.

Do I need loopMIDI to use a gamepad as a MIDI controller?

Only if your bridge does not create its own virtual MIDI port, because loopMIDI is a port creator on Windows and does nothing to read a controller or generate MIDI by itself.

Which gamepad to MIDI tools support Linux?

Very few — Universal Controller MIDI and Gamepad MIDI from Pounding Systems both list Linux support, while loopMIDI, JoyToKey, Bome MIDI Translator and Camelot do not ship Linux builds at all.

Can a Max for Live device replace a standalone bridge?

Inside Ableton Live it can, and the free Kaskobi device does it well, but a Max for Live device cannot send MIDI to anything outside Live, so VJ software, a second DAW or a hardware synth over USB host all need a standalone bridge.

Which tools can read a DualSense touchpad and gyro?

Only the tools written after the DualSense existed and specifically for it — generic HID and XInput-era utilities see a subset of the pad that looks like an older controller, with no touchpad, no motion and no adaptive triggers.

The short version

Pick by operating system, then by controller, then by whether you need the MIDI to leave your DAW. That ordering eliminates eight of the ten tools before price enters the conversation, and it stops you installing a Windows port driver to solve a problem that was never about ports.

Download Universal Controller MIDI free and run the ten-minute test above. Free tier is one controller, one virtual port and three saved presets; Pro is AUD $89 one-time and adds the mapping editor, multi-controller routing, MPE and OSC. If the scale-and-chord engine matters more to you than any of that, go and read Pounding Systems' page — we would rather you bought the right tool.

Keep reading

More setup walkthroughs