The fastest way to a working layout is usually someone else's. A gamepad MIDI preset is a mapping somebody already built and aimed at a particular host — which stick rides which CC, which button fires which clip — and the marketplace is where those live. Browsing is free, including on the free tier.
- Filter by your host, not your controller. The mapping is written against what the software expects.
- Treat it as a starting point. Nobody else knows your session; expect to rebind two or three things.
- Browsing is free — you do not need Pro to see what is there.
- 23 presets as of November 2026, mostly Resolume and Ableton. Small enough that one good upload shows.
Pick by software, not by hardware
This is the thing people get backwards. A preset is aimed at a host: a Resolume mapping assumes Resolume's shortcut system, an Ableton mapping assumes tracks and clip slots, a TouchDesigner one assumes named CCs arriving at a MIDI In CHOP. Which pad you are holding is the smaller variable — a DualSense layout usually transfers cleanly to an Xbox pad, because the sticks, triggers and face buttons line up.
The exception is the touchpad. It is a DualSense feature with no Xbox equivalent, so a preset leaning on touchpad XY will have two controls that simply do not exist on the other pad. The listing says which device it was built for, which is the thing to check when a mapping looks two-thirds right.
What is actually in there
Honest numbers, because a library that overstates itself wastes your time. As of November 2026:
| Host | Presets |
|---|---|
| Resolume | 10 |
| Ableton Live | 6 |
| TouchDesigner | 4 |
| Generic / any host | 3 |
Twenty-three in total. That is a young library, and the useful consequence is that one good mapping is a visible contribution rather than the thousandth item in a pile.
Why does a downloaded preset do the wrong thing?
Nearly always because it assumes a session you do not have. A preset built for a four-track Ableton set will fire clips on tracks that are empty in yours. A Resolume mapping expects its own layer order. The mapping is sending exactly what it promised — it is aimed somewhere else.
That is not a fault in the preset, and it is why the description matters more than the screenshot. A good listing says what it assumes. Read that first, then rebind the two or three controls that do not match how you actually work.
How do you publish one?
From inside the app, once you have a mapping you are happy with. It becomes its own page on the site, carrying its tags, its device and its host, so somebody searching for that exact combination can land on it directly instead of it being buried in an app-only list.
If you are building a layout from scratch rather than adapting one, the template builder is the visual way to do it, and it exports to seven hosts in their own formats. The publishing walkthrough covers the upload itself, and the design notes cover naming things so they still make sense to a stranger.
What makes a preset worth publishing
The difference between a preset someone uses and one they download and abandon is almost never how clever the mapping is. It is whether a stranger can tell what it assumes.
- Say what session it expects. "Four tracks, FX on track 3" is the single most useful sentence a listing can contain.
- Name controls by what they do, not where they are. "Filter cutoff" survives; "R stick up" means nothing once it is in someone else's host.
- Say which pad you built it on. Anything using the touchpad will have dead controls on an Xbox pad, and that is fine as long as it is stated.
- Leave the obvious controls obvious. Transport on the d-pad is a convention for a reason — surprising people costs more than it gains.
None of that is extra work if you do it while building. The template design notes go further on naming and structure.
Do you need the app before any of this is useful?
Yes, and the free tier is enough to find out whether any of it applies to you. It bridges a controller over USB, shows every input live as you press it, and lets you browse the library — so you can confirm your own gear is detected and see what people have built before spending anything.
Download the free tier, plug in whatever pad you own, and open the marketplace. If your controller is not detected in the first five minutes, nothing else on this page matters yet, and the fix is almost always one of four things.
Where to start by host
If you already know your software, these are the setup guides worth reading alongside the presets — they explain what the mapping is talking to:
- Resolume — how its mapping modes differ, which is the usual reason a VJ preset behaves oddly.
- Ableton Live — the DualSense setup walkthrough.
- TouchDesigner — mapping a DualSense into TD.
And if none of this is working yet because the app does not see your controller at all, that is a different problem — start here rather than with presets.
FAQ
What is the preset marketplace?
A library of controller mappings built by other people, browsable from inside the app and on the website. Each preset is a layout — which stick sends which CC, which button fires which note — aimed at a particular host like Ableton, Resolume or TouchDesigner.
Do I need Pro to use presets from the marketplace?
Browsing is in the free tier. The free tier bridges a controller over USB and lets you browse the library, so you can see what exists before deciding whether to buy.
Should I pick a preset by my controller or by my software?
By your software. The mapping is written against what the host expects, so a Resolume preset assumes Resolume shortcuts regardless of which pad you hold. A preset built for a DualSense usually transfers to an Xbox pad, because the control shapes line up.
Why does a downloaded preset not do what I expected?
Almost always because it assumes a session you do not have — a specific track order, a particular FX chain, a Resolume layer that is not there. The mapping is sending what it promised; it is aimed at a different arrangement. Read the description, then rebind the few controls that do not match.
How do I publish my own preset?
From the app, once you have a mapping you are happy with. It gets its own page on the site with its tags, device and host, so it is findable by someone searching for that combination rather than buried in an app-only list.
How big is the library?
Small and honest about it — 23 presets as of November 2026, weighted towards Resolume and Ableton. That is the stage where one good contribution is actually visible, rather than the thousandth item in a pile.