Cockos REAPER for Mac

You have just connected an audio interface, launched REAPER for the first time and the empty arrange view feels more like a blank canvas than an invitation. The application makes no assumptions about your workflow: there are no dedicated track types, just a single channel strip that can hold audio, MIDI, video or a folder of other tracks. That restraint is the best place to start.

• Record a track, any track. Create a new track, arm it and choose your input. REAPER sees up to 512 channels of hardware input, so a mono vocal take and a full drum kit are set up the same way.
• Build a folder to group sources. Drop one track onto another and the child routes automatically into the parent. Record the folder output to freeze processing without rendering a stem: useful for committing a drum bus while keeping the raw takes underneath.
• Remap a hardware output. Open the routing matrix and assign a track directly to a different pair of outputs. With 512 hardware and loopback channels available, cue mixes and external processing chains are a matter of patching, not workarounds.
• Script a small action. Open the Actions list, study a few of the bundled ReaScript examples and bind a custom keystroke. Even a simple script that trims silence from a selected item reveals how much of the interface can be reshaped.

None of these steps requires a template. REAPER treats an orchestral session and a solo voice memo as the same core problem: signal arrives, signal is processed, signal leaves. Starting from that principle keeps the first hours practical rather than theoretical.

Small conveniences: the shortcuts that disappear into muscle memory

Some of REAPER's best design lives in moments so brief you stop noticing them after a week. A single click on the lower half of a track's volume fader resets it to unity gain: no modifier key, no menu. Right-click any knob on the default theme and the value snaps back to its default. These are not documented in a splash screen; they are simply there, waiting for an accidental discovery that becomes instinct.

The routing window itself rewards a closer look. Drag a send from one track to another and the fader appears inline, but hold Ctrl while dragging and REAPER creates a send with the level already at −∞, a precaution against the sudden blast that plagues less thoughtful DAWs. Another quiet detail: the transport bar's rate control. Typing a value directly into the field sets playback speed with sample-level precision, which turns a quick reference check into a transcription tool without opening a single dialogue.

Item gain is perhaps the most overlooked. Hover over the top edge of any media item until the cursor changes, then drag upward. The waveform scales visually in real time, and the gain adjustment is pre-FX, meaning a quiet piano take can be levelled before it ever hits the compressor. No need to insert a trim plugin for such a simple task. In the MIDI editor, holding Shift while dragging a note constrains movement to horizontal or vertical only, and the same modifier while adjusting velocity in the controller lane locks the edit to a single note row. These small constraints add up to faster editing across a long day.

Project-studio owners, sound designers, and composers: three profiles

REAPER's flexibility means different things to different people, but three groups tend to describe their relationship to the software in similar terms.

The project-studio owner tracking live bands. A session with twelve inputs from a drum kit, four from a bass DI chain and a handful of vocal mics needs routing that does not collapse under its own weight. REAPER's 512 hardware inputs and folder-based grouping let an engineer build a monitor matrix per musician without leaving the project. The ability to record the folder output of a drum group while keeping the spot mics underneath means committing a rough mix for the band without destroying the option to rebalance the snare later. Speed matters too: punching in on sixteen tracks simultaneously adds no audible latency beyond what the interface itself imposes, and the absence of track-type restrictions means a click track, a guide vocal and a reference mix all sit on the same kind of strip, arranged in whatever order makes sense for the session.

The composer working with large sample libraries. A template with 200 MIDI tracks routed to a dozen multi-output instruments is not unusual, and REAPER treats every one of those tracks identically. The Actions list becomes a second language here: a custom script that hides all tracks without MIDI data in the current project, bound to a single keystroke, clears the workspace in under a second. The MIDI editor's per-note articulation maps, introduced quietly in the version 7 cycle, remove the need for keyswitch channels that clutter the piano roll. And because the software places no ceiling on the number of MIDI hardware outputs, a composer can drive external synthesizers alongside virtual instruments without dedicating a separate computer to the task.

The post-production editor assembling dialogue and sound design. The item-based nature of REAPER's editing suits someone who thinks in regions, not tracks. A dialogue editor can drop fifty takes onto a single track, trim and crossfade each one independently, then apply clip-level effects only to the three that need de-essing. Spectral edits are non-destructive: paint out a chair squeak in the spectrogram view and the original audio remains underneath, recoverable at any time. When the project moves to a mixing stage, the editor can export a folder containing all active takes as a single WAV with embedded markers, and the import on the mix system lands with everything in place.

Launch in two seconds, install under 50 MB: a working impression

REAPER launches in roughly two seconds on a modern Mac, and the installer itself is smaller than a single drum sample library. That compactness is not a compromise: the application occupies less than 50 MB on disk yet draws a full mixing console with real-time FFT analysis on every channel without a perceptible frame drop. On an Apple Silicon machine, the native ARM build runs cool even under load. A project with 80 tracks, each carrying an instance of ReaEQ and a convolution reverb on an aux bus, keeps the CPU meter hovering around 15 percent on an M1 Pro, leaving plenty of room for virtual instruments. The software rarely beachballs: when it does, the cause is almost always a third-party plugin rather than the host itself.

Stability under pressure is where the engineering shows its priorities. Crashing a plugin does not crash the session. REAPER runs each effect in a separate process by default, so a misbehaving compressor simply goes silent while the rest of the mix continues playing. The option to bridge plugins individually or as a group is buried in the compatibility settings, but once enabled it transforms a risky mix session into something predictable. Audio device dropout behaves similarly: if the interface disconnects mid-playback, the transport stops but the project remains intact, and reconnecting the hardware restores the routing without restarting the application.

Memory use scales with the project, not the ego. An empty session sits at around 120 MB of RAM. Loading a dense orchestral template with Kontakt instances pushes that figure upward, but REAPER's disk streaming is aggressive enough that samples are fetched as needed rather than preloaded in their entirety. The result is a DAW that fits comfortably on a laptop with 16 GB of unified memory, even for work that other applications would reserve for a desktop machine.

Disable the startup prompt and other early adjustments

A fresh REAPER installation is a starting point, not a conclusion. A few early adjustments pay for themselves within the first session.

Disable the default project prompt. Under Preferences > General, the setting labelled "Prompt for project on startup" is enabled out of the box. Switch it to "New project" and the application opens to a blank canvas immediately. The time saved is small, but the mental shift is larger: REAPER stops asking permission to begin.

Set the audio device sample rate explicitly. By default, REAPER requests the sample rate of the project from the hardware. If the interface is set to 48 kHz and the project was last saved at 44.1 kHz, the result is a mismatch that can go unnoticed until a render sounds pitched. In Preferences > Audio > Device, ticking the box labelled "Request sample rate" and entering a value locks the session to a known quantity.

Turn on auto-save with a tight interval. REAPER's undo history is famously deep, but it does not protect against a power cut. Under Preferences > Project, enable "Save to timestamped file in project directory" and set the interval to three minutes. Each save appends to a rolling archive rather than overwriting the main project file, so reverting to a version from an hour ago is always possible.

Resize the mixer panel to taste. The default mixer layout shows a single row of narrow strips. Dragging the divider upward reveals multiple rows, and right-clicking any empty area of the mixer offers layout options that change the strip width and the controls visible. Selecting a layout with the full insert chain displayed turns the mixer from a level-checking panel into a proper mixing surface.

In short: a handful of preference changes, applied once, remove the small frictions that accumulate over a long editing day. The software rewards the effort with an environment that feels less like a rented studio and more like a room you have arranged yourself.

• macOS 10.15 or later
• Apple Silicon and Intel Macs