All pages
Powered by GitBook
1 of 12

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Delay and echoes when recording

Learn about causes and fixes for this problem.

Causes

Audible input monitoring usually causes a delay (latency) of the live recording input due to the time it takes to reach your headphones.

Fixes

To prevent this, turn input monitoring off. This can be done by choosing Transport > Transport Options > Enable audible input monitoring and clicking it to remove the check (tick) mark.

To listen to the live recording input without playthrough latency requires hardware monitoring - that is; the input signal must be routed directly through the audio device from the input to the output rather than being passed through software from input to output.

If the troubleshooting steps aren't working for you, feel free to ask in our communities:

Forum
Discord

Solving recording problems

Audacity is only recording silence

Causes

  • Your microphone gain may be reduced. To fix this, see: Setting recording and playback levels

  • You may be attempting to record a Bluetooth device at an unsupported sample rate. To fix this, see Audacity records silence when using a Bluetooth headset as a recording device

  • You may be attempting to record a device which doesn't produce any sound. To fix this,

    • ensure that all parts of the device are connected properly (cables, microphone, interface, etc),

    • that microphones in need of phantom power are provided with that,

    • that no mute switches on any devices are turned on,

Audacity is not playing back what is being recorded

Learn about causes and fixes for this problem.

Causes

By default, Audacity doesn't play back the input.

Fixes

Go to

Audacity records silence when using a Bluetooth headset as a recording device

Learn about causes and fixes for this problem.

Causes

The default project sample rate in Audacity (and, indeed, most other devices) is 44100 Hz, whereas most Bluetooth headsets utilize different sample rates: 8000 Hz, 16000 Hz and, rarely, 24000 Hz.

Fixes

Only the left channel is recording

Learn about causes and fixes for this problem.

Causes

Most microphones are mono microphones, so they by default record on the left channel only.

Fixes

To hear your audio on both speakers, make sure you record in mono, and that the track is center-panned.

Audacity is not detecting the audio device I just connected

Learn about causes and fixes for this problem.

Causes

If you connect an external audio device (such as a USB microphone or USB headset) to your computer while Audacity is already running, it won't be detected automatically by Audacity.

Fixes

that no faders are turned down, and
  • that an input signal is being produced by the source.

  • Transport ->
    Transport Options -> Enable audible input monitoring
    .

    Notes:

    • You will hear what you are recording a noticeable time afterwards. This delay is called latency. You can somewhat reduce this latency as described in Latency Compensation but it cannot be fully removed if you're using input monitoring in Audacity - you will need an audio interface with realtime monitoring capabilities to completely remove latency when monitoring a recording.

    • If you want to listen to the input before recording, click the microphone in the recording meter and then Enable silent monitoring.

    • Input monitoring can also be enabled In the Recording section of the Preferences window.

    If the troubleshooting steps aren't working for you, feel free to ask in our communities:

    • Forum

    • Discord

    In order for Audacity to record audio from a Bluetooth headset, the sample rate must be set to a value supported by your Bluetooth device. To do that, go to Audio Setup -> Audio Settings and then set Project Sample Rate to a setting supported by your headset. Typically, this will be 16000 Hz. Make sure you record on a new track.

    If the troubleshooting steps aren't working for you, feel free to ask in our communities:

    • Forum

    • Discord

    If the troubleshooting steps aren't working for you, feel free to ask in our communities:

    • Forum

    • Discord

    To solve this, make sure the device is detected by the operating system, then go to Audio Setup -> Rescan Audio Devices . The new device should appear as an option on the Recording or Playback device selection dropdown in the Device toolbar.

    If the troubleshooting steps aren't working for you, feel free to ask in our communities:

    • Forum

    • Discord

    Crackles, pops and distortion in the recording

    Learn about causes and fixes for this problem.

    Causes

    If you hear crackles, pops, or distortion when the recording is loud, or if the waveform is clearly touching the top and bottom edges of the track, you probably have clipping, which means that the signal has exceeded the maximum allowed level.

    Fixes

    Try lowering the recording level using the recording slider or the slider in the operating system.

    You can also check to see if you can lower the volume on the input source itself (such as the tape deck, record player or microphone). Many sound cards and USB turntables or USB tape decks have an independent volume control for the playback signal level. See Recording with USB turntables or USB cassette decks for more help with USB turntables or tape decks.

    When recording, try to aim for a maximum peak of around –6 dB in the Recording Meter so as to prevent the meter's red clipping warning coming on. If the meters are set to linear, the equivalent level to aim for is 0.5. Clicking and dragging on the meter's right edge lets you expand the meter to gauge levels more easily. After recording, you can boost the level safely using the Amplify or Normalize effects.

    Help with repairing clipped recordings: If there is only a small amount of clipping (just the tops of a few isolated peaks), Effect -> Noise Removal and Repair -> Clip Fix can be applied to just the clipped sections. This will attempt to reconstruct the missing peaks by interpolating the lost signal.

    In other cases where there is mild distortion throughout a recording, using Effect -> EQ and Filters -> Filter Curve EQ to reduce the higher frequencies can help to mitigate the damage. Sometimes a bass cut will help also by making the result sound less "muddy".

    If the troubleshooting steps aren't working for you, feel free to ask in our communities:

    Vertical red lines in the recording

    Learn about causes and fixes for this problem.

    Causes

    This is a visual indication that your recording has clipping. See Crackles, pops and distortion in the recording for more information.

    Fixes

    The vertical red lines show where the clipping has occurred; these clipping indicators can be turned on and off (Audacity default setting is "off") by selecting View -> Show Clipping in Waveform.

    If the troubleshooting steps aren't working for you, feel free to ask in our communities:

    Recording volume slider cannot be moved

    Learn about causes and fixes for this problem.

    Causes

    The recording slider is purposely disabled if it cannot directly manipulate the operating system's slider for the sound device, or if that device has no system slider. Turning down the Audacity slider to prevent distortion would be inadequate unless it also turned down the system slider. It would only make existing distortion quieter instead of removing it.

    Fixes

    • If the slider is disabled, check first via Audio Setup -> Recording devices that you are selecting the correct device. Audacity should be able to control the recording level of most built-in sound devices subject to the device having appropriate Sound Device Drivers.

    • External recording devices such as USB turntables or tapedecks or interfaces may not have an operating system slider, especially on Mac. For all cases where there is no system slider, try to adjust the playback level on the recording device itself.

    • Sometimes, switching the host via Audio Setup -> Host may help.

    If the troubleshooting steps aren't working for you, feel free to ask in our communities:

    Recording dropouts, gaps, skips and glitches

    Learn about causes and fixes for this problem.

    Causes

    Recording gaps are typically caused by an overloaded computer, or by broken cables and connectors.

    Computer load

    Audacity is for the most part a single-core application. On modern multi-core systems it typically isn't possible to bring it down with normal computer use, but it may be bottlenecked by hard drive access, and by creating very complex projects with many realtime effects.

    You may be able to see the bottleneck in the performance tab of the task manager (macOS: activity monitor). Typical bottlenecks are CPU or storage.

    Note: To view single-core capability, you need to view logical cores. Overall system performance averages an overloaded core with many idle cores, creating the impression that everything is fine.

    Broken cables and connectors

    There are several parts on the path between a mic and Audacity which can break: The mic itself, the cable, the port for the cable on the computer, and the computer itself.

    Fixes

    Reducing computer load

    Reducing CPU load

    • Close all other programs which aren't necessary to run for your recording task.

    • Increase the buffer length in Audio Setup -> Audio Settings.

    • Disable playback of other tracks, as well as input monitoring during recording (Transport -> Transport options -> Hear other tracks during recording and Enable audible input monitoring)

    • End background tasks, or wait for them to finish. These often may be antivirus scans, system updates or updates of other applications (like games).

    • Render all tracks in Audacity via Tracks -> Mix -> Mix and Render.

    • Shrink the size of the Audacity window and zoom out.

    Reducing hard drive load

    • Record to a hard drive which still has a lot of capacity.

    • End background tasks, or wait for them to finish. These often may be antivirus scans, system updates or updates of other applications (like games).

    • Record to a hard drive which is directly attached to the computer (as opposed to a USB hub or similar).

    • Reduce the amount of data being written. In particular:

      • Record Mono instead of Stereo (Audio Setup -> Recording channels)

      • Record in 16-bit instead of 32-bit (Audio Setup -> Audio Settings)

    Working around broken cables, connectors and other broken hardware

    • Try using a different cable.

    • Try plugging the cable into a different port on the computer

    • Try using a different microphone.

    • Try using a different computer.

    If the troubleshooting steps aren't working for you, feel free to ask in our communities:

    • Forum

    • Discord

    Forum
    Discord
    Forum
    Discord
    The recording slider is the one with the microphone - the top one in this case
    Forum
    Discord
    A waveform with clipping

    Latency Compensation

    By default Audacity will compensate the latency present in your system by 130 milliseconds. Using this procedure you can estimate and set the proper value for your system.

    Note: Latency Compensation is only important for the following recording scenarios:

    • Overdubbing: recording a new audio track while listening to previously-recorded track(s). You want what you play to be synchronized with the tracks you are listening to.

    • Punch and roll recording

    Measuring latency in your system

    There is an automated method available now, which is available at

    It's currently in beta, so please leave your feedback in the forum thread

    Step 1: Adjust your Audacity preferences

    1. Set your Devices Preferences

    • On Windows open the Edit menu and select Preferences... or press Ctrl + P in your keyboard. On macOS open the Audacity menu and select Preferences... or press Cmd + P

    • Select Devices in the left pane of the Preferences window

    • Select the preferred Interface Host:

    2. Set your Recording Preferences

    • Select Recording in the left pane of the Preferences window

    • Enable Overdub: Check Play other tracks while recording (overdub)

    • Make sure Software playthrough of input is not checked

    3. Set your Selection preferences

    At the bottom of the Audacity window you will find the Selection toolbar

    • Disable snapping, if you have it enabled

    • Select Start and Length of Selection as your selection format

    Step 2: Measuring the latency

    Hardware Setup

    To measure the latency you will need to record the audio from your playback device using your microphone. To do this place your microphone next to your speakers/headphones

    Recording while playing a test track (Overdub)

    • Open the Generate menu and select the Rhythm Track... option. Set Number of Measures (bars) to 2 and set the Beat Sound to Ping (short). Click OK to generate the track.

    • Press Shift + R to record a new track. The rhythm track will be played back and recorded on a new track.

    • Zoom in so you can see the clicks on the top track and its delayed version on the bottom track

    • Create a selection that goes from the start of one click to the next

    You should see something like this:

    You can read the latency directly from the second panel of numbers. In this case it is 0.184 seconds or 184 milliseconds.

    Click on Edit > Preferences, click on Devices tab and enter the negative of this number in the Latency compensation box. In this case it would be -184. Press OK to save your preferences.

    Step 3: Checking the result

    • Delete the second track by clicking the close box in its Track Control Panel

    • Click in the Track Control Panel of the remaining track to select it

    • Press Shift + R to record a new track

    After the recording is finished Audacity will apply the Latency compensation by pushing the newly-recorded track back by the Latency compensation value.

    Note: If you change any of your recording or playback devices (for example, if you change from using the line input port on your computer to using a USB audio interface) or if you use the same device but change the in , then you will need to do this test again. The test you just did only applies for the specific inputs and outputs and host used during the test.

    MME or Windows WASAPI should work
  • Verify your preferred Playback Device is selected

  • Verify your preferred Recording Device is selected

  • Set the Latency compensation to 0 (zero) milliseconds

  • Click OK to save your preferences

  • Click OK to save your preferences
    https://forum.audacityteam.org/t/latency-test/65001
    Audio Host
    Device Toolbar
    Select Edit > Preferences... or press Ctrl + P to open Audacity Preferences and click on Devices
    Select Edit > Preferences... or press Ctrl + P to open Audacity Preferences and click on Recording
    Audacity Selection Toolbar
    Place your microphone next to your speakers or headphones
    Recording a new track while playing the previously generated track (Overdub)
    Drag a selection to measure the latency
    Set Latency compensation value according to the measured latency
    Recording with latency compensation applied to the second track
    This video explains how to compensate latency in Audacity