Microphone delay can ruin recordings, live streams, and online calls. Most cases come from a small number of fixable issues. Finding the correct cause solves half the problem. First, identify the type of delay you are experiencing. You may hear your voice late through headphones while recording. Or your recorded audio may not match the video timing. These are separate issues and need different fixes.
What’s Actually Causing Your Microphone Delay?
Microphone delay usually appears in two different forms. One is monitoring the delay during live recording sessions. This happens when your voice reaches the headphones too late. The other is a sync delay in recorded or streamed content. This occurs when audio falls behind the video timing. Knowing which type you have points you directly to the right fix below.
The six most common root causes are:
-
High buffer size: Your recording software is processing too much audio data per cycle, adding latency before playback.
-
Wrong or outdated audio drivers: Default Windows WDM drivers carry inherent latency; outdated drivers make it worse.
-
Software monitoring enabled: Your DAW routes the mic signal through the software chain before sending it to your headphones, and that processing takes time.
-
Wireless transmission lag: Bluetooth and lower-quality wireless systems introduce 100–300ms of delay at the hardware level.
-
Streaming or editing software offset: OBS, Premiere Pro, and similar tools may have an audio offset set incorrectly.
-
OS audio processing enhancements: Windows audio enhancements and macOS sample rate mismatches silently add latency with no obvious indicator.
Fix 1 — Lower the Buffer Size in Your Recording Software
Buffer size controls how many audio samples your system collects before processing them. A larger buffer is easier on your CPU but adds more latency. A smaller buffer processes audio faster but demands more processing power. For recording sessions, target a buffer size of 64 to 256 samples. Start at 128 samples, then lower it if latency persists or raise it if you hear audio dropouts.
Here is how to adjust it in the most common recording applications:
Audacity
1. Go to Edit > Preferences (Windows) or Audacity > Preferences (Mac).
2. Select Audio Settings, then Latencysection from the left panel.
3. Find the Latencybuffer length field.
4. Set it to 100ms or lower as a starting point (Audacity uses milliseconds rather than samples).
5. Click OK and test with a short recording.
GarageBand
1. Go to GarageBand > Preferences and click the Audio/MIDI tab.
2. Find the I/O Buffer Size dropdown.
3. Select 128 or 64 samples.
4. Close Preferences and monitor for improvement.
Adobe Audition
1. Go to Edit > Preferences > Audio Hardware (Windows) or Audition > Preferences > Audio Hardware (Mac).
2. Click Settings next to your audio device.
3. Set the Buffer Size to 128 or 256 samples.
4. Click OK twice to confirm.
Note: On older or lower-spec machines, setting buffer size below 64 samples can cause clicks, pops, or audio dropouts. If that happens, increase the buffer one step at a time until the recording is clean.
Fix 2 — Update or Replace Your Audio Driver
Audio drivers control how your operating system communicates with your microphone hardware. The default Windows audio driver stack (WDM/WASAPI) is built for general use and carries higher latency than drivers designed specifically for audio work. Outdated drivers on either platform can make the situation worse.
Windows
1. Press Windows + X and open Device Manager.
2. Expand Sound, video and game controllers.
3. Right-click your audio device and select Update driver.
4. Choose Search automatically for drivers and follow the prompts.
5. Restart your computer and retest.
If updating the driver does not resolve the issue, install ASIO4ALL — a free third-party driver layer that bypasses the Windows audio stack and communicates more directly with your hardware. Download it from asio4all.org, install it, then select ASIO4ALL as your audio device inside your DAW’s audio preferences. It consistently delivers lower latency than WDM on systems without a dedicated audio interface.
Pro Tip: If you are using a USB audio interface (Focusrite Scarlett, SSL 2, Behringer UMC series), use the manufacturer’s own ASIO driver instead of ASIO4ALL. Manufacturer-specific drivers are optimized for their hardware and will outperform a generic layer.
Mac
1. Open System Settings > General > Software Update and install any pending macOS updates, which include Core Audio driver updates.
2. Open Audio MIDI Setup (Applications > Utilities).
3. Select your microphone from the left panel and verify the Format sample rate matches your DAW’s project sample rate (commonly 44100 Hz or 48000 Hz).
A driver version mismatch between your audio device and your OS is one of the most overlooked causes of persistent latency. It is worth ruling out early.
Fix 3 — Enable Direct Monitoring
Direct monitoring routes your microphone signal straight from the hardware input to your headphone output, completely bypassing the software processing chain. Because the signal never travels through your DAW, you hear it with near-zero latency. This fix addresses the monitoring delay only, and it does not correct sync issues in your recorded file.
Important: Built-in laptop audio hardware almost never supports true direct monitoring. You typically need a dedicated USB audio interface to use this feature.
On a USB audio interface:
1. Locate the Direct Monitor button or switch on the front panel of your interface. Most Focusrite, SSL, and Behringer interfaces label it clearly.
2. Toggle it On. Some audio interfaces include a blend control for monitoring. Turn it more toward the direct hardware monitoring side.
3. On interfaces without a physical switch, open the companion software (Focusrite Control, SSL 360) and enable direct monitoring there.
In your DAW:
1. Open the input track settings in your DAW.
2. Find the Software Monitoring or Input Monitoring toggle on that track.
3. Turn it off. With direct monitoring active on the hardware, leaving software monitoring on creates a second, delayed signal path and produces an audible echo.
You should now hear your microphone in real time with no perceptible delay.
Fix 4 — Reduce Wireless Microphone Latency
Wireless microphones add a small delay during signal transmission. Audio must be processed, sent wirelessly, and received again. No software setting can remove this delay completely. Different wireless systems also perform differently in real-world use.
Bluetooth vs. 2.4GHz wireless: Bluetooth A2DP — the profile most Bluetooth microphones use — introduces between 100 and 300ms of transmission delay by design. Dedicated 2.4GHz wireless systems built specifically for audio operate at under 20ms. If your wireless microphone uses Bluetooth, the protocol itself is the bottleneck, and the practical fix is switching to a dedicated 2.4GHz system.
Environmental interference: Even on 2.4GHz, walls, distance, and competing devices such as Wi-Fi routers or other wireless microphones can degrade the signal and introduce variable latency. Keep the transmitter within the manufacturer’s specified range and reduce obstructions between transmitter and receiver.
General steps to reduce wireless latency:
1. Confirm whether your system uses Bluetooth or 2.4GHz — check the product page or manual.
2. If you are using Bluetooth for recording or streaming work where sync matters, switch to a dedicated 2.4GHz wireless microphone.
3. Position the receiver within clear line-of-sight of the transmitter wherever possible.
4. Reposition or remove competing 2.4GHz devices from the immediate recording environment.
5. After connecting the receiver to your camera or phone, run a short test recording to confirm audio-to-video alignment before starting your main session.
Using the Hollyland LARK MAX 2 for Low-Latency Wireless Recording
The Hollyland LARK MAX 2 is a practical example of how a well-designed 2.4GHz wireless microphone addresses the latency issues outlined above. Its transmission operates at 20ms, and it includes a dedicated real-time wirelessmonitoringoption via OWS earphones, which solves the “I hear myself late” problem without any software configuration.
Pairing the transmitter and receiver:
1. Power on the receiver first. The LED will blink, indicating it is searching for a transmitter.
2. Power on the transmitter. Both LEDs will blink rapidly during the pairing process.
3. When pairing completes, both LEDs turn solid blue. The connection is active, and low-latency transmission begins immediately.
Setting up real-time monitoring through the OWS earphones:
1. Place OWS earphones inside its charging case with the lid open.
2. Press the mode button three times to select wireless monitoring over either Bluetooth or 2.4GHz wireless modes.
The blue light on the earphones represents Bluetooth. Whereas the white light is for the 2.4GHz connectivity. Then, long-press the same button to enter pairing mode.
3. Once connected with the RX, wear it and speak into the microphone. You will hear your voice in the earphones with near-zero lag because this monitoring loop closes at the transmitter hardware itself, not at the recording device or any software chain.
This is the core advantage for wireless users who have been experiencing monitoring delay: the signal never has to travel to a camera or computer and back.
AI Noise Cancellation and its latency effect:
1. The AI Noise Cancellation feature can be enabled or disabled from the transmitter by pressing the power button once.
Or by toggling on NC Level through the HollyAudio (LarkSound) app.
When noise cancellation is active, the TX and RX LED indicators will turn solid green.
2. When this option is turned on, it adds extra processing to the signal path. This can slightly increase the delay during real-time use. For the lowest possible latency, keep it turned off during critical recording sessions. Turn it on only when reducing background noise matters more than speed.
Managing signal strength and receiver placement:
1. Watch the signal strength LED on the receiver during operation. A solid, steady indicator means optimal transmission; a flickering indicator suggests interference or excess distance.
2. Keep the transmitter within the manufacturer’s recommended operating range. Moving beyond that range does not just risk dropouts. It can also introduce variable transmission delay that is difficult to compensate for in post.
Connecting the receiver to your recording device:
1. Use the USB-C output for smartphones and USB-C compatible cameras, or the 3.5mm output for DSLR, mirrorless, and traditional camera inputs.
2. After connecting, play back a short test clip and verify that the audio aligns with the video at this connection point before starting your main recording session.
Fix 5 — Correct Audio Sync in Streaming and Video Software
If your microphone audio and video are out of sync in a final recording or live stream, the software itself may be introducing or misreporting the offset. Each platform has a specific adjustment point.
OBS Studio
1. In OBS, go to Edit > Advanced Audio Properties (or right-click any source and select Advanced Audio Properties).
2. Find your microphone source in the list.
3. Locate the Sync Offset (ms) field for that source.
4. If audio comes before the video timing, increase the offset value. This will push the audio slightly later to match properly.
5. If audio arrives late, decrease the offset value.
6. Test with a short recording and adjust in 10ms increments until the tracks align.
1. Unlink the audio and video clips on the timeline by right-clicking and selecting Unlink.
2. Manually slide the audio clip left or right to align it with the video.
3. Use the audio waveform view to line up visible peaks with corresponding visual cues (a hand clap works well as a reference point).
1. Unlink audio and video on the timeline, then drag the audio track to align it visually.
2. Alternatively, use the Auto Align Audio option under the Clip menu when you have a reference signal, such as a clap or slate, at the start of the recording.
Zoom and Microsoft Teams
1. In Zoom: go to Settings > Audio > Microphone modes. Then select the “Original sound for musicians” option. Uncheck echo cancellation and check the High-fidelity music mode box. When you select this option, it will disable all processing options, including noise suppression.
2. Confirm the microphone input is set to the native device, not a software virtual device.
3. In Teams: go to Settings > Devices and verify the direct microphone input is selected.
4. On both platforms, close any other applications using the microphone before joining the call to prevent driver contention.
Fix 6 — Disable Audio Enhancements in Windows or Match Sample Rate on Mac
If you have worked through Fixes 1 through 5 without fully resolving the delay, the operating system itself may be the remaining source. This section is specifically for users who have already tried the fixes above.
Windows — Disable Audio Enhancements
1. Open Control Panel and navigate to Sound.
2. Click the Recording tab and select your microphone.
3. Click Properties, then open the Enhancements tab.
4. Check Disable all enhancements and click Apply.
Note: If the Enhancements tab is not available in your Windows 10/11, check your audio manufacturer’s app, such as Realtek Audio Console, Waves MaxxAudio, etc.
5. Open the Advanced tab and enable Exclusive Mode — this lets the recording application take direct control of the audio device, bypassing the Windows audio mixing layer and reducing system-level latency.
macOS — Match Sample Rate in Audio MIDI Setup
1. Open Finder > Applications > Utilities > Audio MIDI Setup.
2. Select your microphone from the device list on the left.
3. Note the Format value shown (for example, 44100 Hz or 48000 Hz).
4. Open your DAW and confirm the project sample rate matches this value exactly.
5. A sample rate mismatch forces macOS to perform real-time conversion, which adds measurable latency and can degrade audio quality simultaneously.
Frequently Asked Questions
Why does my microphone have a delay when I talk?
The three most common triggers are a high buffer size in your recording software, software monitoring being active on your input track, and wireless transmission lag if you are using Bluetooth or a low-quality wireless microphone. Start by checking the buffer size in your DAW’s audio preferences and confirming whether direct monitoring is enabled on your audio interface.
How do I fix the microphone delay in OBS specifically?
Open Edit > Advanced Audio Properties in OBS and locate the Sync Offset (ms) field next to your microphone source. Increase the value to delay audio relative to video, or decrease it to move audio earlier in the timeline. Adjust in 10ms increments and test each change with a short recording until audio and video are visually aligned.
Is the Bluetooth microphone delay worse than 2.4GHz wireless?
Yes, significantly. Bluetooth A2DP averages 100 to 300ms of transmission delay due to how the protocol handles audio encoding and packet delivery. Dedicated 2.4GHz wireless microphone systems, such as the Hollyland LARK MAX 2, typically operate well under 20ms. For recording or streaming work where sync matters, Bluetooth is not a practical protocol choice.
Can a wireless microphone cause audio delay in recorded video?
Yes. If a wireless system uses heavy digital encoding, it can add delay. Extra processing inside the receiver can also shift timing. This causes audio to fall out of sync with video. Always check the timing when the receiver connects to the camera. Record a short test clip with a clear sound cue. A simple clap helps compare audio and video alignment.
Conclusion
Most microphone delay issues follow a simple check process. Hearing your voice late in headphones usually links to monitoring settings or buffer size. If recorded audio is out of sync, adjust timing settings in your editor or in OBS. Wireless delay often comes from 2.4GHz signal limits or a weak range. Next, check your specific setup in OBS, GarageBand, or Zoom. If problems continue, review wireless range and interference issues.
