FL Studio Pro
Recording

FL Studio Audio Interface Not Detected: Driver and Input Fix

By Eric Norris Published Sep 24, 2026 15 min read

Quick answer

Select the interface's own ASIO driver on Windows or its Core Audio device on macOS, set a Mixer Insert input from (none) to the right channel, watch the meter, and clear the Input couldn't be opened and Not enough ASIO outputs messages.

FL Studio audio interface troubleshooting cover with a connected interface and Mixer input path

When FL Studio doesn't detect your audio interface, open Options > Audio settings (F10) and select the interface's own ASIO driver on Windows, with FL Studio ASIO or ASIO4ALL only as fallbacks, or the interface itself as the Core Audio device on macOS. Then click the input menu at the top of a Mixer Insert, change it from (none) to the channel your source uses, and watch that Insert's meter. Recording needs Producer Edition or higher, and on a Mac FL Studio also needs microphone permission. My order is power and driver first, then the Mixer input, then permissions, because a Mixer menu can only list the inputs the driver exposes.

Image-Line’s Audio Settings documentation spells out the key distinction: the selected audio driver decides which inputs and outputs FL Studio can use, and the Mixer then picks one of those inputs for recording. If the device is missing from the driver, the Mixer can’t bring it back. If the device shows up in Audio Settings but the Mixer is set to None, the meter will still sit silent.

Audio interface powered and connected to a computer with an input cable ready for FL Studio
Start with the physical path: power, USB connection, source cable and the operating-system device must all be present before FL Studio can select an input.

Check what FL Studio needs to record an input

Recording from an interface needs FL Studio Producer Edition or higher. Image-Line's answer on greyed-out recording inputs applies to external audio recording through the Mixer, and the edition comparison lists Audio Recording as Producer Edition and up. On Fruity Edition no driver or Mixer setting turns the interface into a recording source, so settle the edition first. The FL Studio edition guide covers what each edition adds and how upgrades work.

The recording manual lists the other conditions, and all of them have to hold at once:

  • Windows: an ASIO driver is selected under Options > Audio settings (F10).
  • macOS: FL Studio has microphone permission, which applies from Mojave on. From Monterey on, the Mac microphone mode should be Standard.
  • For Playlist recording, right-click the Record button and make sure Audio has a tick.
  • The source is plugged into an input on the interface.
  • The interface input is selected in the input menu of a Mixer track; arm that track for Playlist recording, or record with Edison loaded on that Insert.

Start with the physical and system checks

Switch the interface on and check the connection before changing FL Studio settings. The device should show its normal power indicator, and the source you want to record should be plugged into an input, not an output. For a microphone, that means the right input socket and sensible gain. For a synthesizer or other line source, use the input pair that matches your cabling.

Plug the USB cable straight into the computer when you can. Hubs, adapters and loose connectors can leave the interface powered but unavailable as an audio device. If the interface has more than one USB mode or driver package, use the mode the manufacturer’s current driver supports. Change one thing at a time so you know which layer made the difference.

Next, check whether the operating system sees the interface as an audio device. If it doesn’t show up there, FL Studio can’t make it appear. Sort out the cable, power, driver or operating-system problem first. If the system sees it but FL Studio doesn’t, move on to the driver selection below.

Start with operating-system checks, then check the driver separately. On Windows, the Sound control panel’s Recording list checks the Windows audio endpoint; absence there alone does not rule out an interface with its own ASIO driver. Check the manufacturer’s driver/control panel and whether that ASIO device appears in FL Studio too. On macOS, open Audio MIDI Setup from the Utilities folder and look for the interface in its device list. Image-Line's knowledge base notes that the interface's own ASIO entry is only available while the unit is connected and its driver installed, so switch the interface on before you start FL Studio, and restart FL Studio if it was already running. Leave Bluetooth headsets out of this job: Image-Line's audio setup page warns that Bluetooth devices add significant audio delay.

Windows: choose the interface ASIO path

On Windows, an external input needs an ASIO path that exposes the interface’s recording channels. Open Options > Audio settings, or press F10, and look at the Device field. If the manufacturer provides an ASIO driver for the interface, try that path first. Image-Line recommends the OEM ASIO driver whenever one exists, because it’s built for that device’s inputs, outputs and timing behavior.

Don’t pick a driver by name alone. After selecting it, look at the input and output information that appears. A driver can be installed and still expose only a different device, a playback-only path or no usable input pair. If the interface’s channels show up after you select the OEM driver, keep that driver selected while you set up the Mixer.

A greyed-out input menu on the Mixer has a specific cause. Image-Line's knowledge base traces it to a DirectSound driver and sends you to ASIO. The Audio Settings manual groups Primary Sound and WDM as Standard drivers and rates ASIO as faster and more efficient than Primary Sound. An Image-Line forum thread shows the pattern: a mixing console appeared in FL Studio as a DirectSound device while it recorded without trouble in Reaper, so the hardware worked and the driver choice failed. If your interface's own ASIO entry is missing from the Device list, follow the manufacturer's current driver installation instructions for your exact interface and operating system, then connect and switch on the interface before opening FL Studio.

Four-step audio-input path: operating-system recognition, device driver in Audio Settings, connected physical input on a Mixer Insert, then input-meter activity
Select the device driver first, then choose the physical input on a dedicated Mixer Insert. Meter movement confirms that the source reaches FL Studio.

FL Studio ASIO is a compatibility option for when the manufacturer’s driver is missing or unsuitable. It’s handy for a quick check, but the available inputs and latency behavior can differ from the OEM path. If an input appears with one driver and disappears with another, that points to a driver-path difference, and the Mixer isn’t to blame.

The two fallbacks behave differently. FL Studio ASIO selects one Input and one Output, which can come from separate devices, and it's multi-client, so other applications stay audible next to FL Studio. ASIO4ALL can select several inputs and outputs from separate devices. The recording manual also warns that FL Studio ASIO, a simulated ASIO driver built on WASAPI, can shift alignment and add jitter from take to take, and it tells you to switch to the native ASIO driver for your interface when you have one. My default is the interface's own driver for any take worth keeping, with FL Studio ASIO only as a quick proof that the input works. The FL Studio audio settings guide compares the driver choices and their latency trade-offs.

Close other audio applications for a moment if the selected driver says the device is unavailable. Some drivers grant exclusive access, and a browser, video call or another DAW can be holding the interface. Reopen Audio Settings once the other application lets go, then check the device list again.

With ASIO4ALL, open its panel and look at the WDM Device List. Expand the interface with its + button and activate the input channels you need; activating the device alone does not necessarily activate its inputs. Only active channels appear in the Mixer input menu. A red X through an input or output usually means another audio application is using it, according to the ASIO4ALL page of the FL Studio manual: close FL Studio, close the program that holds the device, then reopen FL Studio. Audio Settings also has Auto close, which lets other applications share the device when FL Studio loses focus. If voice-chat apps or media players keep tying up inputs in ASIO4ALL, turn Auto close off, close those programs and restart FL Studio. The same switch matters when bridged plugins stop playback by taking audio focus: turn Auto close off or use FL Studio ASIO.

The "Not enough ASIO outputs" message

If FL Studio shows "Not enough ASIO outputs are available. At least 2 channels are needed", open F10 > Audio and check Status, which reports the selected driver's inputs and outputs. Confirm that the interface is on and connected, then select its driver again. If FL Studio was already running when you powered the interface, restart FL Studio first. The message is a reason to check the selected device and its available channels; it does not establish a hardware fault.

“Input couldn’t be opened”: check the Windows input

If FL Studio ASIO reports “Input couldn’t be opened!”, check its recording input before changing Mixer effects. Open Options > Audio settings > Show ASIO panel and choose your interface or microphone by name in Input instead of leaving [Default input] selected. Image-Line’s FL Studio ASIO input controls follow the Windows default recording device when that default option is selected; working playback does not establish that the intended input is selected.

On Windows 11, open Settings > Privacy & security > Microphone. Check Microphone access, Let apps access your microphone and Let desktop apps access your microphone. Microsoft documents these microphone permissions for desktop apps; FL Studio does not need to appear in the individual Microsoft Store app list. On Windows 10, the corresponding page is Settings > Privacy > Microphone.

Return to FL Studio and check the input again. If it is now available, continue with the dedicated Mixer Insert below. If it still fails, use the manufacturer’s ASIO path described above when available; the message alone does not identify a hardware fault.

When using FL Studio ASIO through the Windows audio stack, check that the FL Studio sample rate and the Windows device rate agree. Treat this as a setting to rule out, not a diagnosis for every OEM ASIO driver. Then switch off Windows Audio Enhancements, also called Sound Effects or Spatial Sound. They add EQ, bass boost or loudness processing at system level, and the manual notes that FL Studio ASIO sits on top of the Windows audio stack, so it's affected too. My rule is enhancements off for recording and mixing alike, because the manual warns they distort your sense of levels and tonal balance.

macOS: check Core Audio, Aggregate Device and permission

macOS uses Core Audio device paths instead of Windows ASIO drivers. In FL Studio Audio Settings, choose the interface or the relevant Core Audio device, then check which inputs and outputs it exposes. If you combine the interface with another audio device, Image-Line documents using an Aggregate Device on macOS. You have to create the aggregate in Audio MIDI Setup before FL Studio can select it.

For a missing-device diagnosis, start with the interface selected directly as a single Core Audio device, because that leaves fewer routing choices to check. If you do create an aggregate, confirm its input and output members and sample-rate relationship in Audio MIDI Setup. A device can be listed while the aggregate exposes the wrong side or an unexpected channel order.

The same USB recording page adds a less obvious use: aggregating a single interface can fix crackling, especially while recording, as long as the sample rate in Audio MIDI Setup matches FL Studio's. FL Studio can choose one input device and one output device separately. Combining two input devices, or multiple outputs in one role, requires an aggregate; the total number of connected devices is not the deciding condition.

macOS device-role map: choose one input and one output separately; combine two input devices through an Aggregate Device, or aggregate multiple output devices for one FL Studio output
One input device and one output device can be selected separately; aggregate multiple devices within either role.

macOS can also block microphone and audio-input access. If the device is there but no signal reaches FL Studio, check the system privacy permission for FL Studio, then restart the application after you change it. Permissions can explain a silent input, but they can’t explain a device the operating system doesn’t see at all.

The switch lives under Apple menu > System Settings > Privacy & Security > Microphone, where, as Apple microphone access guide shows, you turn access on or off for each app. Image-Line's Mac audio recording checklist adds the cases people miss. The permission applies to every input device, not just a built-in microphone. On Apple Silicon, grant it in both Apple Silicon and Rosetta modes if you switch between them. If FL Studio isn't in the list at all, start it once in Rosetta mode so macOS asks for microphone access, then switch back; Image-Line traces that gap to an earlier install under Rosetta 2.

From Monterey on, one more control sits in the menu bar. While FL Studio is running, click the Microphone icon at the top right and select Standard mode. If Standard is already on and recordings still sound poor, switch to Voice Isolation and back to Standard; the same checklist says that resets settings that weren't applied correctly.

Set the FL Studio driver before changing the buffer

The buffer isn’t an input switch. It changes how much audio FL Studio processes at a time, which affects latency and stability, and it can’t create an input the selected driver doesn’t expose. Choose the right device first, confirm the inputs show up, and only then adjust the buffer if you hear delay, clicks or dropouts.

For a normal recording check, use a moderate buffer and leave plugin compensation decisions alone until the input works. A very small buffer can add clicks that pull you away from the real diagnosis. If changing the buffer makes the device vanish, go back to the driver that exposes the interface and deal with the buffer separately.

Select the interface input on a Mixer Insert

Open the Mixer and select an unused Insert. The FL Studio Mixer manual describes the input menu at the top of the Mixer track. Choose the interface input or stereo pair that carries your source. Don’t leave the Insert on None, and don’t assume that picking the interface in Audio Settings automatically assigns a Mixer input.

An Insert reads (none) until you choose an input, and the Mixer manual defines (none) as no external input selected. Click it and pick the interface channel. Each Mixer track takes one external stereo input, and selecting an input auto-arms the track for recording, shown by the red recording icon. On Windows the menu only lists inputs while an ASIO driver is in use, so an empty or greyed list sends you back to the driver section. For a multi-input interface, right-click the Input menu to run Auto-map: it gives each input on the device its own Mixer track, starting at the track you clicked and working to the right. I'd run Auto-map only when you record several sources at once, because one source on one Insert is easier to trace.

Give the external source its own dedicated Insert. If the interface exposes inputs 1 and 2 as a stereo pair, choose that pair for a stereo source. For a mono microphone or instrument, choose the correct mono input where available and keep the other channel out of the route. The exact names depend on the driver, so read the channel labels instead of guessing from the number.

Watch the Insert meter while the source plays. It’s the quickest way to split the diagnosis in two:

  • If the input is missing from the menu, return to the selected driver and operating-system device.
  • If the input is listed but the meter does not move, check the source cable, input gain, permission and the selected channel.
  • If the meter moves, FL Studio sees the interface. Continue to the recording destination and monitoring choice.

The Master meter doesn’t prove the external input is set up correctly, because the Master combines all of the project’s routed audio. The dedicated Insert tells you whether this particular interface input is reaching FL Studio.

Set the Recording Pickup selector in front of the Input menu as well. Its EXT position, marked recommended in the Mixer track properties reference, records direct from the audio interface, and the recording level is then set on the interface, not inside FL Studio. I'd leave it on EXT for a single source, because nothing else routed to that track can blend into the take. The same selector holds Monitor external input with three settings: Off, When armed, which monitors only while the track is armed, and On, which always monitors.

Record only after the meter moves

Once the Insert meter responds, pick the destination that suits the job. The official audio recording workflow separates focused recording in Edison from recording into the Playlist. Use Edison for a short take you want to inspect, trim or save as a sample, and the Playlist when the take needs to sit against the project timeline.

For Edison, load Edison on the Mixer Insert and record the signal there. Keep the source route isolated so you can stop, inspect and save the take without capturing the rest of the project. The existing FL Studio Edison guide covers the editing and file-handling choices after capture.

For the Playlist, arm audio recording and pick the recording option that sends the Insert to the arrangement. Record a short test first, and check that the clip lands on the expected track and holds the interface source, not the whole Master output.

For Playlist recording, two switches decide whether the take lands. Right-click the main Record button and make sure Audio has a tick in the recording filter, then check that the Insert's own recording switch is armed; the recording manual singles out that second switch because it's easy to forget.

Fix the common symptoms in the right order

The interface is not in Audio Settings

Check power, cable, operating-system visibility and the manufacturer driver. Reopen FL Studio once the OS recognizes the device. On Windows, try the OEM ASIO driver before FL Studio ASIO; on macOS, check the Core Audio device and any permission prompt. Don’t start by lowering the buffer, since a buffer change can’t repair a missing device.

The interface is in Audio Settings, but no input appears on the Mixer

Confirm that the selected driver exposes recording channels and not just playback. Some devices expose different channel sets depending on the driver mode, sample rate or aggregate configuration. Re-select the driver, then reopen the Mixer input menu. If the channels are still missing, the problem sits between the driver and the device, and the recording command isn’t involved.

The input menu is greyed out or stuck on (none)

First confirm that you have Producer Edition or higher for external audio recording. On Windows, check for a DirectSound or other Standard driver and switch to ASIO under F10 > Audio. If the menu opens but stays on (none), click it and choose the channel your source uses. If ASIO4ALL is selected and no input appears, check its WDM Device List for a red X and close whatever holds the device. On macOS, check the microphone permission. If you combine multiple input devices or multiple output devices, check that the Aggregate Device includes the intended channels in the expected order.

The input is listed, but the Mixer meter is still silent

Check the input socket, cable and gain. Make sure the source is really producing signal and that phantom power is on only when the connected microphone needs it. Choose the channel that matches the physical socket. On macOS, revisit FL Studio’s microphone permission; on Windows, check whether another application has grabbed exclusive control of the interface.

If the meter stays silent after those checks and the source is a microphone, open the existing microphone input troubleshooting guide. It follows the same signal-first logic and digs deeper into source-specific causes.

The meter moves, but the recording is empty

Make sure you’re recording the Mixer Insert that carries the signal. Check the audio recording filter and the selected Edison or Playlist destination. A moving Master meter doesn’t prove the correct Insert is armed. Make a short capture, stop it and look at the waveform before you record a long take.

You hear clicks, dropouts or unstable monitoring

Raise the buffer for now and cut unnecessary load while you diagnose the input. Then check the interface sample rate and, if you use one, the macOS aggregate configuration. The existing FL Studio crackling guide is your next stop when the interface is visible and the problem is performance, not detection.

The recording contains the whole project or a doubled signal

Move the source to a dedicated Insert and monitor one path only. If you hear the same source directly through the interface and again through FL Studio, switch one monitoring path off. If the Master is being recorded, the external input gets mixed with drums, instruments or effects. The clean route is source → interface input → dedicated Insert → Edison or Playlist.

Use this final checklist

Work through these checks in order:

  1. The interface is powered and its source is connected to an input.
  2. The operating system sees the interface as an audio device.
  3. Windows uses the interface OEM ASIO driver when available, or macOS uses the correct Core Audio device.
  4. FL Studio Audio Settings shows the interface’s input channels.
  5. A dedicated Mixer Insert is set to the input or stereo pair carrying the source.
  6. The Insert meter moves before recording starts.
  7. Edison or Playlist is selected for the job, and only one monitoring path is active.

If the device disappears before step four, stick with the operating-system and driver checks. If it appears but the meter stays still, stick with the physical input, permissions and channel choice. Once the meter moves, the detection problem is solved, and anything left over is about recording, monitoring, timing or performance.

Frequently asked questions

Why doesn't FL Studio detect my audio interface?

FL Studio sees an interface only through the driver selected under Options > Audio settings (F10). If the interface's own ASIO driver isn't installed, the unit is off or disconnected, or a DirectSound driver is selected, its inputs never reach the Mixer. Install the manufacturer's driver, power the interface, then select its ASIO driver on Windows or the interface as the Core Audio device on macOS.

What does Input couldn't be opened mean in FL Studio?

FL Studio ASIO couldn't open the recording input it's set to use. Choose your interface or microphone by name in the ASIO panel's Input field instead of [Default input], check the Windows microphone permissions, and match FL Studio's Sample Rate to the Windows recording device.

Why does the Mixer input say (none)?

(none) means no external input is selected for that Mixer track. Click the input menu at the top of the track and choose the interface channel. If the menu is greyed out on Windows, switch to an ASIO driver first.

Can FL Studio Fruity Edition record from an audio interface?

No. External audio recording from the interface requires Producer Edition or higher; this does not exclude Fruity Edition’s MIDI-note recording, and its edition comparison lists Audio Recording as Producer Edition and up.

Should I use ASIO4ALL, FL Studio ASIO or my interface driver?

Use your interface's own ASIO driver when it exists; Image-Line recommends it for recording. FL Studio ASIO selects one input and one output and works as a compatibility option, and ASIO4ALL can combine several inputs and outputs from separate devices.

Why isn't FL Studio listed in the Mac microphone settings?

Image-Line traces this to an earlier install under Rosetta 2. Start FL Studio once in Rosetta mode so macOS asks for microphone access, grant it, then switch back to Apple Silicon mode.

Eric Norris
Eric Norris Nashville-based FL Studio producer and editor focused on practical workflow, mixer routing, troubleshooting, sampling and native Image-Line tools.
Explore all Recording guides