Set up ASIO4ALL in REAPER and record your first take
REAPER uses ranges to decide which driver inputs and outputs appear in a project. A device can be active in ASIO4ALL while a channel stays hidden in REAPER. Set up the device and check the first and last channels before troubleshooting an individual track.

In this guide
How to set up ASIO4ALL in REAPER
To use ASIO4ALL in REAPER, open Options › Preferences › Audio › Device, set Audio system to ASIO and choose ASIO4ALL v2 as the ASIO Driver. Click ASIO Configuration to enable your playback and recording devices, then set REAPER's first and last input and output channels so the ones you need are inside the range.
REAPER uses these ranges to decide which driver channels appear in a project. That means a device can be active in ASIO4ALL while a channel stays hidden in REAPER. This guide shows how to configure ASIO4ALL in REAPER on Windows 10 and Windows 11, record a first mono take, and check which application is actually controlling the block size.
What you need
- REAPER installed on Windows 10 or Windows 11.
- ASIO4ALL 2.22 installed from the publisher using
ASIO4ALL_2_22.exe. ASIO4ALL is free for end users, including commercial recording. - Headphones or speakers and, for recording, a microphone or instrument connected to a device Windows already recognises.
The publisher's getting started manual explains how ASIO4ALL connects to a DAW in general; the steps below apply that to REAPER.
Configure ASIO4ALL v2 in REAPER's Device preferences
Open Options › Preferences and select Device under Audio. Keep the configuration small for the first test. A stereo output and one microphone channel are usually enough to check the round trip from capture to playback.
- Set Audio system to ASIO and choose ASIO4ALL v2 as the ASIO Driver.
- Click ASIO Configuration. In the ASIO4ALL panel, enable the audio endpoint for your headphones or speakers and the recording input you intend to use.
- Back in REAPER, turn on Enable inputs if you are recording. Set the first and last input so the range covers the channels you need.
- Set the first and last outputs to include your playback pair.
- Apply the preferences and close the window.
Tip: Enable only the devices you are using right now in the ASIO4ALL panel. A short list of channels makes REAPER's ranges easier to read, and fewer devices means fewer things that can disagree about timing.
Understanding channel ranges
REAPER shows driver channels by number. The first and last input and output settings act like a window: anything outside the window is not offered to tracks. If your microphone is on driver input 3 and the range is set to inputs 1 to 2, the mic stays invisible in the track input menu even though ASIO4ALL is passing it through.
| Setting | Example value | Why |
|---|---|---|
| Audio system | ASIO | Uses an ASIO driver rather than WDM or WASAPI directly |
| ASIO Driver | ASIO4ALL v2 | The name the driver uses in hosts |
| Enable inputs | On | Required for recording |
| Input range | First to last channel you record from | Makes the mic channel visible to tracks |
| Output range | Includes your headphone or speaker pair | Lets the Master track reach your playback device |
Record one channel and play it back
With the device configured, insert a new track and arm it for recording. In the track's input selector, choose Input: Mono and then the channel your microphone or instrument uses. A single microphone belongs on a mono input; a stereo pair would leave one side empty or duplicate the signal.
Check the meter first
Speak or play and look for a clean meter response on the track before you enable input monitoring. If the meter stays still, check the input range in Device preferences, the input you enabled in the ASIO4ALL panel, the hardware gain and the cable.
Take and playback
Record a short take of ten or fifteen seconds and stop. Disarm the track and play the recorded item. If it sounds clean and in time, the round trip through ASIO4ALL is working and you can move on to a real session.
If the track and Master meters move while playback is silent, confirm that the Master track's hardware output uses the pair you configured in Device preferences. Then check the device you enabled in the ASIO4ALL panel and the physical volume of your headphones or speakers.
Choose a monitoring path
You can hear yourself while recording in two ways. Each has a place, but using both at once usually produces an audible double.
- Hardware direct monitoring: the interface or USB mic sends the input straight to its headphone output. It has no software buffer delay, which is useful for a vocalist who wants a natural feel.
- REAPER input monitoring: the signal passes through REAPER and its track effects before reaching your ears. It is useful when you need to hear reverb, compression or an amp simulator while performing.
Pick one and keep the other monitoring path off. If you hear a slight echo or a phasey, hollow sound, both paths are probably active.
Watch out: Turning on input monitoring with an open microphone and speakers can cause feedback. Use closed headphones and a low volume until you know which monitoring path is active.
Monitoring latency in numbers
Software monitoring adds at least one input buffer and one output buffer. At 48 kHz, a 128-sample buffer lasts about 2.7 ms, 256 samples about 5.3 ms and 512 samples about 10.7 ms. At 44.1 kHz, 256 samples is about 5.8 ms. Small buffers keep monitoring comfortable; large buffers can make it feel late.
Check which setting controls the block size
REAPER can request a sample rate and block size from the driver in Device preferences. That is convenient, but it also means two applications can appear to control the same value: REAPER's request and the buffer setting in the ASIO4ALL panel.
When an ASIO4ALL change seems ignored
If a change in the ASIO4ALL panel appears to have no effect, inspect REAPER's Request block size checkbox and the size the session reports. When REAPER is requesting a size, it may override what you set in the driver panel.
- Decide which application should set the block size, REAPER or ASIO4ALL.
- Change one setting at a time.
- Reopen the preferences or reinitialize audio if REAPER still shows the previous value.
- Note the block size and sample rate REAPER reports once it settles.
The publisher's buffer size documentation and our ASIO4ALL buffer size guide explain how the driver handles buffer values in more detail.
Note: Keep the project rate consistent during the first test so you can compare buffer settings fairly. Changing sample rate and block size together makes it hard to tell which one improved or worsened playback.
Tune ASIO4ALL for real REAPER projects
A first take in an empty project proves the setup works, but a production project with many tracks and plugins asks much more of the computer. Clicks that emerge only in a large project are a reason to test a larger block size in that session.
A practical routine
Track with a smaller block size when timing feel matters, then raise it for mixing when you need headroom for effects. Write down the stable value before changing it again for a live recording, so you can always return to a known-good setting.
Before raising the buffer, close other applications that use audio, such as browsers, video calls or media players. ASIO4ALL works on top of the existing WDM drivers, and another program holding the same device can cause problems that look like a buffer issue. If you need another app briefly, version 2.20 and later include a system tray option to pause host audio and release the devices.
Latency and alignment
If recorded takes land slightly early or late against the click, look at how latency is reported and compensated rather than lowering the buffer further. Our guide to ASIO4ALL latency compensation covers how to check alignment with a simple loopback test.
ASIO4ALL or WASAPI in REAPER
REAPER can also use WASAPI directly. Some people prefer it for simple playback, while ASIO4ALL is useful when you want an ASIO driver, a single control panel and the option to combine inputs and outputs from compatible WDM devices. Our comparison of ASIO4ALL and WASAPI covers the differences.
The official REAPER User Guide documents the Device preferences page and recording options in full, and is worth keeping nearby while you set up a new machine.
Frequently asked questions
Check that the mic input is enabled in the ASIO4ALL panel via ASIO Configuration, that Enable inputs is on in Device preferences, and that the first and last input range includes the mic's channel number.
REAPER may be requesting its own block size. Inspect the Request block size checkbox in Device preferences, decide which application should set the value, and reinitialize audio if the old size is still shown.
Use Input: Mono and select the channel the microphone is plugged into. A single mic on a stereo input often records on one side only.
Confirm the Master track's hardware output uses the pair inside your output range, that the matching device is enabled in ASIO4ALL, and that your headphones or speakers are connected and turned up.


