The one forum thread on Launchpad and Playtime 2 in Reaper has a question and no answer. It holds the question, a few tags and a list of similar threads, nothing more (https://audiosex.pro/threads/launchpad-for-playtime-2-in-reaper.85652/). So this guide does not guess at compatibility. It gives you a verification step, a setup order, and a test project that shows on your own machine whether pad launches are as tight as mouse launches.
Step 0: Confirm support before you plug anything in
Everything else depends on two facts: which models are supported and how the mapping works. Both can change between releases. Playtime is made by Helgoboss, the developer behind ReaLearn. Check the current Playtime and ReaLearn documentation on the Helgoboss site for three things:
- Whether your exact Launchpad model (Mini, X, Pro, and their generations) is listed as supported.
- Whether support comes from a bundled controller preset, from a ReaLearn mapping, or from a controller list inside Playtime itself.
- Which pad mode the device must be in (for example a Programmer or Session layout), and which Novation firmware or Components settings the docs mention.
This article states none of those as fact, because the current documentation has not been checked here. If your model is not listed, treat it as unsupported until the docs or the developer say otherwise. A custom ReaLearn mapping may be possible, but that is a bigger project and a different guide.
Step 1: Set up the audio side first
A hardware test means nothing if the audio path keeps changing. Fix these before you touch the Launchpad.
- Open Preferences > Audio > Device and pick one buffer size. Write it down. Use the same value for every test pass.
- Close other audio apps and set your interface as the Reaper device, so you are not testing a laptop's default output.
- Set the project tempo to something easy to read on a grid, such as 100 BPM. The number is arbitrary. A round tempo just makes bar lines easy to check.
- Leave the project sample rate alone for the whole test.
Step 2: Connect the Launchpad and enable its MIDI port
If you can, plug the Launchpad straight into the computer instead of going through a hub. Then open Preferences > Device > MIDI Devices in Reaper and look for the Launchpad ports. Which ports need enabling, and whether they are set for input or for control, depends on the mapping route you confirmed in Step 0. Follow the documentation for that route, not a generic rule. This pairs well with see also: how to test audio to midi converters on your own tracks.
One caution, and it is an inference rather than a documented fact. If two things claim the same device at once, such as a preset and a separate hand-made mapping, each pad press may be handled twice. Suspect that first if you later see double triggers.
Step 3: Build the test project
This project removes every variable except how the clip was launched.
- Make a new Reaper project at your chosen tempo and open Playtime.
- Create four clips in one scene, all the same length, for example two bars. Use loops you already own or make your own. A drum loop, a bass loop, a chord loop and a plain click work well.
- Make sure each loop starts exactly on its first beat, with no leading silence. A sharp transient on beat one, like a kick or a click, makes timing easy to see on a waveform.
- Match clip gain by ear and by meter so the four loops sit at similar loudness. Don't change these levels during the test.
- Set Playtime's launch quantization to one bar. The exact label may differ by version, so check the setting in your install. Quantized launches make the fair comparison, because both methods should land on the same bar line whatever your hands do.
- Add a new audio track, arm it, and set its input to record the output of the Playtime track (or route the master to it). That gives you a recording to inspect, so you don't have to trust your ears alone.
Step 4: Map and check pad behavior
With the mapping from Step 0 active, press each pad in the scene and confirm the matching clip starts. Don't judge timing yet. You are only checking that the right pad launches the right clip, and that the LED colors make sense when a clip is idle, queued, playing and stopped.
Playtime's documentation should describe what the feedback is meant to look like for your model. If your pads show something different, go to the troubleshooting table below. This pairs well with our guide to varispeed vs time stretch for sampling: a daw exercise.
Step 5: Run the A/B comparison
The test has two passes with identical settings. Only the launching method changes.
- Pass A, mouse: start the Reaper transport, then click a drum clip so it launches on the next bar. Let it play four bars, stop it with the mouse, then launch the next loop. Record the output to the test track for the whole pass.
- Pass B, Launchpad: repeat the same sequence by pressing pads. Keep the same buffer size, tempo, quantization and clip gain.
- Put both recordings side by side and zoom in on the first transient after each bar line. With quantization on, each loop should start on the grid in both passes. A visible shift in Pass B only points to a problem in the control path.
- Level-match before you listen. Check both recordings on the same meter, such as Reaper's built-in loudness meter, and if one is louder, trim its item volume until both read the same. Louder always sounds tighter, so skipping this step biases the result.
- Listen blind if you can. Have a friend rename or shuffle the two items, then pick the one that feels more solid. If you can't hear a difference and the waveforms line up on the grid, the Launchpad is doing its job.
No latency numbers appear here because none are cited. Your own recordings are the only evidence that counts for your rig.
What to watch and listen for
Three behaviors decide whether a controller is reliable enough for live use.
Also read: suno bridge with ableton live 12: try the beta or wait?
- Launch timing. Loops should enter on the bar line, not slightly early or late.
- Loop restarts and stops. A loop should restart cleanly at its first beat and stop without a click, a hanging tail or a restart.
- Double triggers. One pad press should produce one launch. If a clip restarts, stops straight after starting, or toggles unexpectedly, count that as a failure and repeat the pass to see whether it happens every time.
Run the test several times. A single clean pass proves little. Ten passes that all line up is a result you can rely on.
Troubleshooting
| Problem | Likely cause (check first) | What to try | |---|---|---| | No pad response | MIDI port not enabled in Reaper, wrong pad mode, or mapping inactive | Recheck Preferences > Device > MIDI Devices, put the Launchpad in the mode the docs require, and confirm the mapping is switched on | | Wrong LED colors or no feedback | Feedback output port not enabled, or a mapping meant for a different model or mode | Enable the output port, confirm you loaded the preset for your exact model, and compare with the documented feedback behavior | | Pads launch the wrong clips | Layout mismatch between the pad grid and the Playtime matrix | Check the grid offset or scene position in the mapping and move the matrix view to match | | Double triggers | Two mappings or control routes handling the same device (inference) | Disable all but one route, then retest | | Late launches only on Launchpad | Buffer size, USB hub, or a busy system rather than the quantization setting | Retest with the same buffer, plug in directly, close background apps, and compare the recordings again | | Launches drift between passes | Quantization changed, or the clips differ in length | Reset one-bar quantization and confirm all loops are exactly the same length |
If none of this fixes it, post your Launchpad model, firmware version, Reaper and Playtime versions and the mapping route in the Helgoboss support channels linked from their documentation. Those details make a problem answerable.
What to expect next
Once the Launchpad passes the A/B test, save the project as a template. You can then rerun the same check after a Reaper, Playtime or firmware update. From there, the next step is building your own scene layouts and stop pads for jamming.
If the pads fail the test, you have recordings that show where. That makes a support question or a refund decision much easier.



