RECORDING

Recording with USB Microphones and Headsets

This section covers the special issues raised by USB microphones.

The problem: If you use the F10 audio settings to select your USB microphone, then you can't hear sound from FL Studio and if you select your soundcard you can't record your microphone. Most ASIO soundcard drivers only support one audio device, that means you can select either to your USB microphone or soundcard but not both at the same time. You need both!

The solution: ASIO4ALL allows you to select independent input and output audio devices within the same soundcard driver. This section will assist you in setting up ASIO4ALL to work with your soundcard (output) and USB mic (input), or another soundcards inputs, simultaneously. After these steps you can review the normal recording procedure here.

NOTE: While there is no technical reason for a USB microphone to be inferior to a traditional analog-output microphone, USB mics can compromise your positioning, routing and monitoring options. If you haven't purchased a mic yet, we recommend using a traditional analog mic connected to FL Studio through a external audio interface for the widest compatibility and utility in the studio. This includes longer cable runs, direct monitoring and the option to use the highest quality microphones and mic preamps.

Using a USB Microphone or Headset

This procedure is provided for your convenience, we can't guarantee that it will work as not all soundcards are compatible with ASIO4ALL, but most are. The aim is to set your USB mic as the ASIO input device and your soundcard as the ASIO output device.

  1. Install ASIO4ALL - The default FL Studio installation includes ASIO4ALL so it should already be on your PC. It not, Download ASIO4ALL here.
  2. Select the ASIO4ALL driver - In FL Studio press F10 to open the Settings window and open the audio settings options. Select 'ASIO4ALL v2' in the Output window.
  3. Open the ASIO4ALL driver settings - Click on 'Show ASIO Panel' in the 'ASIO properties' section to open the ASIO4ALL driver window.
  4. Select the 'Advanced' options - ASIO4ALL should open in Advanced mode (as shown below) if not, click on the Spanner in the lower right of the window to change between modes.
  5. NOTE: If any of the inputs/outputs of the devices in the 'WDM Device List' have against them, it means they are unavailable. means beyond logic. See the ASIO4ALL System Settings page for details on troubleshooting ASIO4ALL input/output issues.

  6. Select the input (ASIO mic) and output devices (your regular soundcard) - In the example above the host PC has an X-Fi Soundcard and a Plantronics USB Headset (with mic), your options will probably differ. Enable all the devices you wish to use (at the highest level in the list) and then expand the options for each device by clicking on the [+] tree-view symbol to the left of each device name. You must (at least) ensure that the input associated with your USB Microphone/Headset and the output on your soundcard are both enabled. In the picture shown above, the lighted blue buttons and arrows show the active devices and active inputs/outputs. Disabling unused inputs/outputs is not necessary, but it will simplify the number of options that appear in the Mixer IN and OUT menus. If you are unsure what input you need, just make sure all inputs and outpts are enabled at all levels.
  7. Success? If you have set ASIO4ALL correctly, your USB microphone should appear as an Mixer IN option on any selected Mixer track, while the audio out from the mixer (Master track) should be routed to your soundcard, as usual.
  8. Return here to follow the normal recording procedure.

Note about latency: USB microphones generally only allow you to hear the sound being recorded after it has passed through FL Studio. As the latency of USB microphones depends on the ASIO4ALL latency settings, there may be a troublesome delay between the sound made and it being reproduced from your speakers or headphones. For example, low latency monitoring is particularly important to vocalists as high latencies cause a distracting echo effect. The only solution to this problem is to lower your buffer length settings (there are limits) or obtain a new soundcard with direct-monitoring.