Most pad controllers (MPC, MPD, Maschine, Fire, Launchpad) are class-compliant: no drivers, no MIDI router, no fuss. Padforms catches your device in under a second and starts scoring every hit against the click.
USB-A or USB-C; both work. Class-compliant pad controllers (MPC, MPD, Maschine, Fire, Launchpad) need no drivers on macOS or Windows.
Padforms expects the standard MPC pad layout (MIDI notes 36 to 51). Most devices default to this. If you've remapped pads in your DAW or device editor, reset to the factory preset; your manual will say how.
The top bar shows CONNECTED within a second of plugging in. Hit any lesson: the timeline scrolls, every hit gets graded against the click.
Unplug, count to two, plug back in. If you still see nothing, close anything else that might be holding the device: MPC Beats, Ableton, your device's editor app, MIDI Monitor. Padforms doesn't fight for the connection; the first app to grab it wins.
Nine times out of ten, it's a custom preset. Reset your device to its factory pad layout (MPD218: hold top-left for three seconds; MPC / Maschine / Fire: see your manual). Confirm the pads send standard MIDI notes 36 – 51.
macOS: open Audio MIDI Setup and lower the buffer size to 128 samples. Windows: Padforms uses WASAPI Exclusive, so close any other audio app first, then open Padforms.
Right-click the app → Open → Open again. Padforms is signed but not yet notarized in v1. After the first launch, double-click works normally.
Padforms uses Microsoft's WebView2 runtime to render the UI. Most Windows 11 machines have it already. If yours doesn't, the installer fetches it (~120 MB). One-time, then you're set.
Most setup issues are a five-line fix once we see the actual error. Drop a note with your OS, your MPD218 firmware version, and what you've already tried. We write back personally, usually within a day.