Set up ASIO4ALL in FL Studio on Windows
FL Studio can use ASIO4ALL v2 to access compatible Windows audio devices through its ASIO driver menu. Start by getting sound from a simple project, then add your recording input. This sequence makes it easier to locate a problem in the driver, the output device or the Mixer.

In this guide
How to use ASIO4ALL in FL Studio
To use ASIO4ALL in FL Studio, open Options › Audio settings (or press F10), choose ASIO4ALL v2 from the Device menu, click Show ASIO Panel and enable the output your headphones or speakers use. Play a simple project to confirm sound, then enable your microphone input and route it to a Mixer insert. Finally, tune the buffer under a realistic project load.
That order matters. Getting clean playback first, then adding a recording input, then adjusting latency lets you isolate a problem to one layer at a time: the driver, the output device or the FL Studio Mixer. This guide walks through each step on Windows 10 and Windows 11 and explains what to check when something does not behave as expected.
What you need before you start
- A Windows 10 or Windows 11 PC with FL Studio installed.
- ASIO4ALL installed from the publisher. The current release is 2.22, distributed as
ASIO4ALL_2_22.exe. If you have not installed it yet, follow the ASIO4ALL installation guide first. - Headphones or speakers connected to a device Windows already recognises, plus a microphone if you plan to record.
ASIO4ALL is free for end users, including commercial audio work, so there is no licence step to complete before using it in FL Studio.
FL Studio ASIO and ASIO4ALL are different drivers
FL Studio ships with its own driver called FL Studio ASIO. It appears in the same Device menu as ASIO4ALL v2, which is a common source of confusion. The two drivers have separate control panels and separate settings, so a change made in one does not carry over to the other.
Everything in this article applies when you select ASIO4ALL v2 by name. If you follow a step and the panel looks different from what is described here, check which driver is selected at the top of the Audio tab before going further.
Which driver to pick
If your audio interface came with its own manufacturer ASIO driver, that driver is usually the first choice. ASIO4ALL is a universal driver that works on top of the existing WDM drivers in Windows, which makes it useful for built-in sound chips, USB headsets, USB microphones and devices without a dedicated ASIO driver. Try a manufacturer driver first if you have one, and keep ASIO4ALL as a reliable fallback.
| Driver | Where it comes from | Typical use |
|---|---|---|
| ASIO4ALL v2 | Installed separately from asio4all.org | Built-in audio, USB headsets and mics, combining inputs and outputs from compatible WDM devices |
| FL Studio ASIO | Installed with FL Studio | Image-Line's own option for general playback |
| Manufacturer ASIO | Installed with an audio interface | Dedicated interfaces with their own driver and control panel |
Select ASIO4ALL v2 and a playback device in FL Studio
Install ASIO4ALL, then close and reopen FL Studio so the program can find the new driver. Connect your headphones, speakers and any USB audio device before launching FL Studio, because some devices only show up in the driver list when they are present at start-up.
- Open
Options › Audio settingsor press F10, then select the Audio tab. - Choose ASIO4ALL v2 from the Device menu.
- Click Show ASIO Panel to open the ASIO4ALL control panel.
- Enable the output for the device your headphones or speakers are connected to. Begin with a single output device rather than several.
- Check the physical volume control on the device, your headphone amp or your speakers.
- Play an instrument or an audio clip in a blank project. Watch the Master level meter and listen for steady playback.
If you hear clean audio at this point, the driver and output path are working. Save a copy of this blank project as a test file. It is useful later whenever you change a setting and want to confirm the basics before opening a large session.
Tip: Keep the first test as simple as possible: one output device, one instrument, no effects. Adding inputs, extra devices or a heavy project before playback works makes it much harder to see which layer is causing a problem.
Using the advanced view
The ASIO4ALL panel has a simple view and an advanced view. Click the wrench icon to switch to the advanced view, where you can expand a device and enable or disable individual inputs and outputs. You need this view when a device offers several channels and you want to pick a specific one.
Route a microphone to a Mixer insert
Once playback works, open the ASIO4ALL panel again with Show ASIO Panel and enable the input your microphone is attached to. If the device has several inputs, use the wrench to open the advanced view, expand the device and select the specific input you need.
Assign the input in the Mixer
In FL Studio, select a free Mixer insert and choose the microphone input from that insert's audio input menu. For a single microphone, choose the mono channel that corresponds to the socket the mic is plugged into, rather than a stereo pair. A mono mic on a stereo input often records on one side only.
Speak into the microphone and watch the insert meter. Once you see a signal, record a short take and play it back. A ten-second test take is enough to confirm the full path from capture to playback.
When the mic does not appear
If the insert's input menu does not list the microphone, check the input's status in the ASIO4ALL panel and confirm that Windows detects the device. A USB microphone that is unplugged, disabled in Windows or held by another application may not be available to the driver. Our ASIO4ALL USB microphone guide covers device-specific checks, and the official FL Studio manual on recording USB microphones explains the Mixer side.
Watch out: Keep speakers quiet when monitoring an open microphone, or use headphones. A live mic near speakers can feed back quickly, especially when you lower the buffer to reduce latency.
Set the ASIO4ALL buffer size in FL Studio
The buffer decides how much audio the driver processes in each block. A smaller buffer means lower latency but more work for the CPU per second; a larger buffer gives the computer more headroom but adds delay between a key press and the sound you hear. With ASIO4ALL v2 selected, you set the buffer in the ASIO4ALL panel for the selected device.
Buffer maths
The delay of one buffer is samples divided by sample rate, multiplied by 1000 to give milliseconds. Real round-trip latency is higher, because input and output each add their own buffer and device overhead, but this calculation lets you compare settings quickly.
| Buffer (samples) | At 44.1 kHz | At 48 kHz | Good for |
|---|---|---|---|
| 128 | about 2.9 ms | about 2.7 ms | Playing synths live, vocal monitoring in light projects |
| 256 | about 5.8 ms | about 5.3 ms | A common all-round starting point |
| 512 | about 11.6 ms | about 10.7 ms | Mixing busy projects with many plugins |
| 1024 | about 23.2 ms | about 21.3 ms | Heavy mixdowns where real-time playing is not needed |
Test under a realistic load
A blank project will run at almost any buffer, so test in the session you actually plan to use. Play it for a few minutes and listen for clicks. When you hear dropouts in a busy project, increase the buffer one step and test again.
For live synth playing or vocal monitoring, try a shorter setting during a test take and keep the lowest one that stays stable. Many producers use a small buffer while tracking and a larger one while mixing. The full ASIO4ALL buffer size guide and the publisher's buffer size documentation go deeper into the trade-offs.
Note: Save the project before restarting FL Studio after a driver change. Switching drivers or devices can briefly interrupt audio, and a restart is sometimes the cleanest way to make the new setting take effect.
Troubleshoot ASIO4ALL in FL Studio
Most ASIO4ALL problems in FL Studio fall into three groups: no sound, a missing input, or clicks and dropouts. Working through them in the same order as the setup makes them easier to solve.
Master meter moves but headphones are silent
A moving Master meter with silent headphones usually makes the output path the quickest place to investigate. FL Studio is producing audio, but it is not reaching your ears. Check these points in order:
- Which output is enabled in the ASIO4ALL panel, and whether it belongs to the device your headphones are plugged into.
- Where the headphones are physically connected, for example front panel versus rear panel or laptop jack versus USB headset.
- Whether another application is using the selected device and preventing ASIO4ALL from opening it.
- The hardware volume on the device, headphone amp or speakers.
For a broader checklist that applies to every host, see our ASIO4ALL no sound guide.
Input missing or silent
If the input menu on the Mixer insert does not show the microphone, return to the ASIO4ALL panel and confirm that the input is enabled. If the input is listed but the insert meter stays flat, check that you picked the correct mono channel, then the hardware gain and the cable.
Clicks, pops and dropouts
Raise the buffer one step and test the same project again. If the clicks disappear, the computer needed more headroom for that session. If they continue at large buffer sizes, reduce the number of enabled devices in the ASIO4ALL panel and close other audio applications before trying again.
Habits that keep FL Studio and ASIO4ALL stable
A stable setup is mostly about consistency. Once ASIO4ALL works in FL Studio, a few small habits help you keep it that way across sessions and updates.
Before each session
- Connect USB audio devices before launching FL Studio.
- Close other applications that play or record audio, such as video calls or browsers playing media.
- Open your saved test project first if you changed anything since the last session.
When you update
Write down the ASIO4ALL version, the enabled inputs and outputs, the sample rate and the buffer that worked. After updating ASIO4ALL or FL Studio, reopen the same test project with the same hardware and compare. If behaviour changes, the ASIO4ALL version history is the first place to look for related fixes.
Version 2.22 lists improved dropout prevention in certain cases, and it is the release the publisher currently offers. Version 2.20 added an option to pause host audio from the system tray, which is handy when you want another app to use the device briefly without closing FL Studio.
Frequently asked questions
Both can work. Choose ASIO4ALL v2 when you want its control panel, need to pick specific inputs and outputs from WDM devices, or are following instructions written for ASIO4ALL. If your interface has its own manufacturer ASIO driver, try that first.
Make sure ASIO4ALL is installed from the publisher and restart FL Studio after the installation. FL Studio reads the list of drivers when it starts, so a driver installed while it is open does not appear until the next launch.
Start around 256 samples, which is roughly 5.3 ms at 48 kHz. Lower it for live playing or vocal monitoring if the project stays stable, and raise it one step at a time when a busy project starts to click.
Yes. Enable the microphone's input in the ASIO4ALL panel, then choose that input on a free Mixer insert. For a single mic, pick the mono channel that matches its socket and record a short test take before a full session.


