Audio Host (MME): Sound Card Interaction in Audacity
Audiodrome is a royalty-free music platform designed specifically for content creators who need affordable, high-quality background music for videos, podcasts, social media, and commercial projects. Unlike subscription-only services, Audiodrome offers both free tracks and simple one-time licensing with full commercial rights, including DMCA-safe use on YouTube, Instagram, and TikTok. All music is original, professionally produced, and PRO-free, ensuring zero copyright claims. It’s ideal for YouTubers, freelancers, marketers, and anyone looking for budget-friendly audio that’s safe to monetize.
What Is an Audio Host (MME) in Audacity?
An audio host is a software layer that manages communication between Audacity (or any digital audio workstation) and your computer’s audio hardware. It determines how audio data is transferred between the DAW and the sound card or audio interface, directly affecting latency, stability, and real-time playback or recording performance.
MME is the default audio host used by Audacity on Windows systems. It provides a basic, stable method of accessing audio devices but with higher latency compared to modern alternatives.
- Pros: High compatibility with virtually all Windows sound devices.
- Cons: Noticeably high latency during real-time monitoring (typically 50–200 ms). No exclusive access to hardware.
Audio Host (MME) and Other Options in Audacity
Audacity provides several audio host options based on the operating system and available drivers. Each host varies in terms of latency, device control, and use cases.
Host | Operating System | Latency | Best For |
---|---|---|---|
MME | Windows | High | Basic recording/playback |
WASAPI | Windows | Medium-Low | Podcasting, internal audio capture |
DirectSound | Windows | Medium | Casual recording/gaming |
ASIO | Windows | Very Low | Music production, professional input |
Core Audio | macOS | Low | Default for Apple hardware |
JACK | Linux/macOS | Adjustable | Advanced routing and multi-app setups |
The chosen audio host affects the responsiveness and quality of real-time monitoring, which is especially important in live recordings and overdubbing scenarios.
Key Differences Between Hosts
Audio host APIs determine how your computer interacts with audio hardware. Each system offers different performance, compatibility, and use cases depending on your goals and setup.
MME (MultiMedia Extension)
MME is the oldest Windows audio host and works with almost every device, including built-in speakers, USB mics, and webcams. Its latency is high, often over 100 milliseconds, so your voice or instrument will sound delayed when monitoring.
It also routes audio through the Windows mixer, which can introduce noise or timing problems if other programs are open. This host works best for light editing tasks where timing doesn’t matter, such as cutting or cleaning audio.
WASAPI (Windows Audio Session API)
WASAPI supports two modes: shared, which combines audio from multiple apps, and exclusive, which bypasses the system mixer for better quality. It allows loopback recording, which captures internal system audio – a useful option for streamers or podcasters.
Latency is lower than MME, often under 50 milliseconds, which makes it usable for real-time tasks with basic gear.
ASIO (Audio Stream Input/Output)
ASIO gives direct control of the audio interface with ultra-low latency – often under 10 milliseconds. It’s essential for multichannel recording, high sample rates, and live performance.
However, Audacity doesn’t support ASIO in its default version because of license conflicts. To use it, you’ll need an ASIO interface or a wrapper like ASIO4ALL, and possibly a custom Audacity build.
DirectSound
This older Windows driver still exists for compatibility but doesn’t offer low latency or hardware-level access. It’s fine for watching videos or gaming but not for recording music.
Core Audio
Apple devices rely on Core Audio, which offers stable, low-latency performance with automatic device detection. It supports professional work without needing extra drivers.
JACK
JACK is a complex but powerful system mainly for Linux. It’s highly customizable and ideal for advanced users who need flexible audio routing.
How to Change the Audio Host (MME, WASAPI, ASIO) in Audacity
Step 1: Open Audacity.
Step 2: Go to Edit ▸ Preferences (or Audacity ▸ Preferences on macOS).
Step 3: Select the Devices tab.
Step 4: Under Audio Host, choose your preferred host:
- MME (default, stable, high latency)
- WASAPI (recommended for lower latency)
- ASIO (only available with custom build)
Step 5: Adjust Buffer Size for performance:
- Lower buffer = less latency (but higher CPU load)
- Higher buffer = more stability (but more delay)
/%5BScreenshot%5D%20Audacity%20MME.png)
Tip: Always test the audio settings before recording. Poor configuration can result in crackling, dropouts, or no sound.
Best Practices for Audio Host Setup in Audacity
Choosing the right host helps you avoid glitches, reduce delay, and improve sound quality. Your selection depends on your equipment and what kind of work you’re doing.
For Recording
If you’re recording instruments or vocals and have a dedicated audio interface, use ASIO. It gives you the fastest response time and the most stable connection for multitrack sessions.
If you’re using a USB microphone or your computer’s built-in sound card, WASAPI is the better choice. It delivers lower latency than MME and works well even without extra drivers.
For Podcasting and Voice Editing
WASAPI is also a solid option for editing speech or voiceovers. It’s more efficient than MME and provides enough speed for monitoring without noticeable lag.
Avoid MME unless you have no other choice. It introduces more delay and is more likely to cause problems when recording or playing back audio.
By choosing the right host and matching it to your gear and goals, you’ll get cleaner recordings and smoother edits.
/%5BInfographic%5D%20Audacity%20Audio%20Troubleshooting.png)