FL Studio

Best FL Studio Audio Settings, ASIO Driver and System Requirements

Set FL Studio's audio driver, buffer length, sample rate and CPU options for recording or mixing, plus ASIO driver advice and system requirements.

On this page
  1. Open the audio settings panel
  2. Pick the right audio driver
  3. Buffer length: the main latency setting
  4. Sample rate
  5. CPU and performance options
  6. Suggested settings for recording and mixing
  7. System requirements
  8. Common misconceptions
  9. Related guides

The audio settings decide how quickly FL Studio responds, how stable playback is, and how much processing power is left for plugins. Most of the useful controls sit in one panel, so it helps to know what each one does before you change it.

Open the audio settings panel

Go to Options > Audio Settings, or press F10 and open the Audio tab. The layout varies a little by version, but the device, buffer length and sample rate controls are all in this panel.

Pick the right audio driver

The driver connects FL Studio to your sound hardware. On Windows you usually choose from three options:

  1. Your audio interface’s own ASIO driver. If you use an external interface, such as one from Focusrite or PreSonus, install the driver from the manufacturer’s site and select it. This is usually the best choice.
  2. FL Studio ASIO. It is built into FL Studio and is a reasonable fallback when you have no interface.
  3. ASIO4ALL. A free third-party driver for built-in sound cards. It can work well, but it can be finicky, and it may lock the device to one application.

For what ASIO does and why a native driver usually wins, see What Is ASIO?.

Avoid the Primary Sound Driver for recording. It gives limited buffer control and usually adds more latency.

On macOS, FL Studio uses Core Audio, so there is no ASIO choice to make.

FL Studio ASIO handles one input device and one output device. Set them in its own panel, which you open with Show ASIO panel.

Buffer length: the main latency setting

The buffer length sets how many audio samples the computer processes in each batch. A smaller buffer means less delay. It also gives the CPU less time to finish each batch, so crackles and dropouts become more likely.

You can work out the delay for each buffer size with this formula:

Delay per buffer (ms) = buffer size in samples ÷ sample rate × 1,000

Buffer (samples) Delay at 44.1 kHz Typical use
64 about 1.5 ms Playing virtual instruments on a fast computer
128 about 2.9 ms Tracking vocals and instruments
256 about 5.8 ms Tracking on a slower computer
512 about 11.6 ms Mixing projects with many plugins
1024 about 23.2 ms Heavy projects where crackles are a problem

These figures are for one buffer. The round-trip delay, which is what you hear when you play and monitor through the computer, is roughly double, plus the converter’s own delay. A round trip under about 10 ms usually feels immediate to most players, though people differ. The audio latency and buffer size guide explains how one buffer becomes the full round trip.

As a rule of thumb, tracking works well at 64 to 256 samples, and mixing a heavy project often needs 512 samples or more. The underrun counter in Audio Settings shows dropouts. If it climbs while you work, raise the buffer.

Sample rate

44.1 kHz and 48 kHz cover almost all music work. 44.1 kHz is common for music that will be streamed, and 48 kHz is the usual choice for video. Set the same rate in your interface’s control panel and in your operating system.

A higher sample rate does not reduce latency for free. It shortens each buffer in time, but it also roughly doubles the processing load.

CPU and performance options

These options are in the Audio Settings panel and the related CPU menus:

  • Multithreaded generator processing and Multithreaded mixer processing spread work across CPU cores.
  • Smart Disable switches off plugins that are not producing sound, which saves CPU.
  • Triple buffer can stop glitches on large projects, but it adds latency. Turn it off while recording.
  • Mixer resampling quality affects CPU load during playback. Set a higher quality for the final export.

Suggested settings for recording and mixing

  • Recording: your interface’s ASIO driver, a buffer of 64 to 256 samples, Triple buffer off, and a sample rate that matches the interface.
  • Mixing: the same driver, a buffer of 512 samples or more, and Smart Disable turned on.

System requirements

System requirements change between versions, so check the page for the version you use or plan to buy. Image-Line’s current FAQ lists these minimums:

  • Windows: Windows 10 or 11, a 2 GHz CPU with SSE2, 4 GB of RAM, and 4 GB of free disk space.
  • macOS: macOS 10.15 or later on an Apple Silicon or Intel Mac, with the same memory and disk requirements.

For smoother performance, Image-Line suggests a quad-core CPU, 8 GB of RAM or more, and an SSD. FL Studio runs natively on Apple Silicon. Earlier releases listed different minimums, so an older guide may not match what you need.

Common misconceptions

  • “ASIO4ALL is always the best choice.” A dedicated interface driver usually performs better.
  • “A higher sample rate lowers latency for free.” It shortens the buffer, but it also raises CPU load.
  • “The smallest buffer is always best.” Very small buffers in large projects cause crackles and underruns.
  • “Crackling means clipping.” Crackles are usually buffer underruns. Clipping is a level problem, covered in why audio clips in FL Studio.

If you hear delay while you play or record, read how to fix audio and MIDI latency in FL Studio. For controllers, see how to reduce MIDI latency. If a take comes out silent, check why an FL Studio recording is silent before you change the buffer.

Keep exploring

Guides from other topics

All topics →