By Erick Finn, independent music producer and audio engineer.
Part of the Sound Forge Pro 2026 Guide — start there if you're new to the editor.
This fix is part of the Sound Forge Pro Core Editing hub. If playback or recording is working again, continue with recording, cutting, normalizing and exporting.
This guide is part of the Sound Forge Pro Troubleshooting hub. Start there if you need symptom-first fixes for no sound, recording/input problems, ASIO routing, Windows audio devices or missing VST plugins.
Tested with Sound Forge Pro 17 and 18 on Windows 11, using a Focusrite Scarlett interface, built-in Realtek audio, a USB microphone, and ASIO4ALL. Last tested July 2026.
Sound Forge Pro recording no sound is almost always fixable without reinstalling anything. Sound Forge Pro shows silence. No meters move. The Record dialog lists no devices. If you haven't set up recording yet, start with the recording guide instead. If setup is done and it still won't record, work through this list in order. Most recording failures trace back to one of four things: Windows blocking microphone access, the wrong driver selected, input routing not set up, or another application holding the audio device hostage.
Quick answer: Go to Windows Settings, Privacy and Security, Microphone, and turn on "Let desktop apps access your microphone." That single toggle sits at the bottom of the page and is easy to miss. It's the most common reason Sound Forge sees no input at all. If that doesn't fix it, work through the ASIO and exclusive mode steps below.
Before You Start: Identify the Exact Problem
Different symptoms point to different causes. Find yours here, then jump to the matching fix.
No input devices appear in the Record dialog. This is almost always Windows microphone permissions or a driver that hasn't been selected and applied. Go to Fix 1 and Fix 2.
An input device appears, but the meters don't move. Input routing is pointing at the wrong channel, or the gain is at zero. Go to Fix 5.
Meters move during recording, but the file plays back silent. Check that you selected the correct channel in File → New before recording, not just in the input routing. A stereo file with only the left channel routed will show meters but leave the right channel empty.
Sound Forge records, but audio has gaps or glitches. This is a buffer size problem or background CPU load. Go to Fix 6.
Your interface works in Audacity, Zoom, or Teams, but not in Sound Forge. Another application has exclusive control of the device, or ASIO4ALL only allows one app at a time. Go to Fix 4.
You're trying to record what's playing through your speakers. Sound Forge has no built-in loopback. Go to Fix 7.
Fix 1: Windows Microphone Permissions
Windows 10 and 11 block microphone access for desktop apps by default. Sound Forge is a desktop app, so it needs a specific toggle turned on. Check this first. Sound Forge gives no error message when the setting is off. The meters just sit at zero and you're left guessing.
On Windows 11:
- Open Settings
- Go to Privacy and Security, then Microphone
- Turn on "Microphone access"
- Scroll to the bottom and turn on "Let desktop apps access your microphone"
On Windows 10:
- Open Settings
- Go to Privacy, then Microphone
- Turn on "Allow apps to access your microphone"
- Scroll down and turn on "Allow desktop apps to access your microphone"
The desktop apps toggle is what actually controls Sound Forge. The per-app list above it only applies to Microsoft Store apps. After turning it on, restart Sound Forge and check the Record dialog again.
Windows updates sometimes reset this setting without warning. If recording worked last week and stopped after an update, check here first. The Microsoft support page for this setting is at the official microphone permissions guide.
Fix 2: ASIO Driver Not Selected or Not Applied
Sound Forge Pro supports three driver types: ASIO, Windows Classic Wave, and Microsoft Sound Mapper. If your interface has an ASIO driver installed, it won't show up as an input source until you select and apply it in Preferences.
Go to Options, Preferences, Audio. In the "Audio device type" dropdown for the Record device, select your ASIO driver by name. Focusrite interfaces show as "Focusrite USB ASIO." Universal Audio interfaces show as "UA ASIO." After selecting it, click Apply before doing anything else. The driver won't activate until you click Apply. This one step trips up more people than any other in the setup.
Once the ASIO driver is applied, click the Input button in the same Preferences panel to open input routing. Select the channel your microphone is plugged into. For a mono vocal mic on input 1 of a Scarlett, select channel 1 as the record input. Recording a mono source as stereo wastes disk space and gives you a file where both channels are identical. The voice-over recording guide walks through mono versus stereo routing step by step.
Which driver should you actually use? ASIO if your interface supports it, for lower latency and direct hardware access. Windows Classic Wave for simple USB microphones or built-in audio where latency doesn't matter much. Microsoft Sound Mapper as a last resort if nothing else detects your device.
If no ASIO driver shows up for your interface, the interface driver probably isn't installed. Most audio interfaces need a driver download from the manufacturer's site, separate from just plugging in the hardware. Plug-and-play USB devices often skip this step, but they also won't have a named ASIO entry. That's where ASIO4ALL comes in.
Fix 3: ASIO4ALL for Interfaces Without Native ASIO
If your interface has no native ASIO driver, or you're using a built-in sound card, download ASIO4ALL from asio4all.org. Install it, select ASIO4ALL in Sound Forge's Preferences, click Apply, then open its control panel through Advanced, Configure. Enable your input device by clicking the power button next to it.
If you see a red X next to your device in the ASIO4ALL control panel, the device is unavailable. This usually means one of three things: another application already has it open, the USB connection dropped, or a previous session didn't release the device cleanly. Unplug and replug the USB device. Close every other application that touches audio, including browser tabs. A YouTube video playing in a background Chrome tab can hold onto the audio device and block ASIO4ALL from seeing it. Restart Sound Forge after clearing everything else.
ASIO4ALL allows only one application to access the device at a time. If Audacity, OBS, or a screen recorder is open and using the same device, Sound Forge won't be able to start recording. Close everything else first.
Fix 4: Exclusive Mode Conflict
Windows has an Exclusive Mode setting that lets one application take full control of an audio device and lock everyone else out. If another app grabbed exclusive control before Sound Forge opened, Sound Forge sees nothing from that device, even though the hardware is working fine.
Two ways to fix it.
Close the conflicting application. Common culprits: a voice assistant running in the background, Teams or Zoom minimized to the tray, a browser tab that previously asked for mic access, or a screen recorder. Close them, restart Sound Forge, and try again.
Disable Exclusive Mode on the device itself. Open the Windows Control Panel, go to Sound, click Recording, right-click your microphone or interface, select Properties, then open the Advanced tab. Uncheck "Allow applications to take exclusive control of this device." Click Apply. Every application can now share the device at once. Sound quality doesn't change.
Native ASIO drivers are built to allow one application at a time. That's normal behavior, not a bug. If you're on a native ASIO driver, close everything else before you start recording.
Fix 5: No Input Signal Despite Correct Setup
Permissions are on. The driver is selected and applied. Exclusive mode isn't the issue. Meters are still dead. Try these in order.
Check the physical connection. Unplug the interface and plug it into a different USB port, directly on the motherboard rather than a front panel port or a hub. Front panel ports on desktop PCs cause more problems than people expect.
Check the input level in the Record dialog. Set it to 0 dB as a starting point. If your hardware has its own gain knob, turn it to the middle and watch the meters while you speak or play. A USB mic not working in Sound Forge often comes down to this single step, since USB mics rarely have a hardware gain control of their own and rely entirely on the software level.
Check the Windows default input device. Right-click the speaker icon in the taskbar, open Sound Settings, and look under Input. Confirm your interface is listed and set as default. If Windows doesn't show it at all, the operating system isn't detecting the hardware, which means this is a driver or connection problem before it's a Sound Forge problem.
Test in another application. Open Windows Voice Recorder and try recording there. If that also shows nothing, the problem sits at the Windows or hardware level. Fix it there first, then come back to Sound Forge.
Fix 6: Audio Dropouts or Gaps During Recording
Sound Forge records, but the file has stutters, clicks, or missing chunks.
Increase the buffer size. Go to Options, Preferences, Audio, Advanced, Configure. This opens your interface's ASIO control panel. Raise the buffer from 64 or 128 samples to 256 or 512. A larger buffer means slightly more latency during monitoring, but you likely won't notice 512 samples on playback, and the gaps disappear.
Turn off input monitoring in the Record dialog. Monitoring adds processing overhead. If you don't need to hear yourself through Sound Forge while recording, monitor through your interface's own hardware monitoring instead. Zero latency, zero CPU cost.
Close background applications. Antivirus scans, cloud sync, and a browser tab with video playing can all interrupt the audio buffer at the worst moment. Run as little else as possible during a take. Check the system requirements if dropouts happen consistently even with a clean background, since underpowered hardware causes the same symptom.
Fix 7: Recording System Audio (Loopback)
Sound Forge Pro has no built-in loopback for capturing what plays through your speakers. Two routes around this.
Stereo Mix, if your device has it
Open the classic Control Panel, go to Sound, click Recording. Right-click an empty area of the device list and check "Show Disabled Devices." If Stereo Mix appears, right-click it and enable it. In Sound Forge's Preferences, select Stereo Mix as the record input.
Most professional audio interfaces don't expose Stereo Mix, because loopback isn't what they're built for. Built-in Realtek chipsets on laptops and desktops are more likely to have it. If it's not in the list even after checking "Show Disabled Devices," your hardware probably doesn't support it.
When Stereo Mix is missing: FlexASIO and WASAPI loopback
If Stereo Mix isn't available, FlexASIO gives you a more reliable path. Install FlexASIO, select it as the driver in Sound Forge, click Apply, then open Advanced, Configure. Set the backend to Windows WASAPI. Set the input device to your speaker's loopback entry, usually listed as "Speakers [Loopback]." Set the output device to your regular speakers. Set buffer size to 1024 to start, then adjust down if you need lower latency.
This setup works even on hardware that has no Stereo Mix option at all, because it captures at the Windows audio engine level rather than through a hardware feature. It takes more steps to configure than Stereo Mix, but it's the more dependable option on modern laptops and interfaces.
Common Causes at a Glance
| Symptom | Most likely cause | Fix |
|---|---|---|
| No devices in Record dialog | Windows microphone permissions | Settings, Privacy and Security, Microphone, enable "Let desktop apps access your microphone" |
| Interface doesn't appear as an input option | ASIO driver not selected, or Apply not clicked | Options, Preferences, Audio, select ASIO driver, click Apply |
| Input device shown, meters dead | Wrong input channel selected, or gain at zero | Preferences, Audio, Input button, select correct channel and raise gain |
| Works in Audacity or Zoom, not Sound Forge | Exclusive mode conflict, or ASIO4ALL single-app limit | Close the other app, disable Exclusive Mode in Windows Sound settings |
| ASIO4ALL shows a red X | Device in use elsewhere, or USB not seated properly | Unplug and replug the device, close other audio apps and browser tabs, restart Sound Forge |
| Gaps, clicks, or dropouts in the recording | Buffer too small | Increase buffer in ASIO control panel, disable input monitoring |
| Stopped working after a Windows update | Permissions reset, or driver replaced | Re-check microphone permissions, reinstall interface driver from the manufacturer |
| No Stereo Mix option available | Hardware doesn't expose loopback | Use FlexASIO with Windows WASAPI backend instead |
Frequently Asked Questions
Why does Sound Forge Pro show no input devices in the Record dialog?
Usually Windows microphone permissions. Go to Settings, Privacy and Security, Microphone, and turn on "Let desktop apps access your microphone." If that's already on, check that your ASIO driver is selected in Options, Preferences, Audio, and that you clicked Apply after selecting it.
Why does my audio interface work in Audacity but not Sound Forge Pro?
Audacity often uses WASAPI or WDM. If Sound Forge is set to ASIO and another app already has exclusive access, Sound Forge can't reach the same device. ASIO drivers typically allow one application at a time. Close Audacity first, then open Sound Forge. If you're on ASIO4ALL specifically, only one program can use it at once.
Why does ASIO4ALL show a red X in Sound Forge Pro?
The device is unavailable to ASIO4ALL. Another application already has it open, the USB connection isn't seated properly, or a previous session didn't release the device. Unplug and replug the interface, close other audio software and any browser tabs playing audio, and restart Sound Forge.
Should I use ASIO, Windows Classic Wave, or Microsoft Sound Mapper?
ASIO first, if your interface supports it. It gives you lower latency and direct hardware access. Use Windows Classic Wave for a basic USB mic or built-in audio where latency isn't critical. Try Microsoft Sound Mapper only if neither of the other two detects your device.
Can Sound Forge Pro record multiple microphones at once?
Yes, if your audio interface exposes multiple inputs to Sound Forge. Create a new file with the matching channel count, then confirm that each Sound Forge input channel is routed to the correct hardware input. Sound Forge records into an audio file rather than separate DAW-style tracks, so plan the channel layout before you start recording.
How do I fix Sound Forge Pro recording gaps and dropouts?
Increase the buffer size in your ASIO driver's control panel. Go to Options, Preferences, Audio, Advanced, Configure, and raise the buffer from 64 or 128 to 256 or 512 samples. Also turn off input monitoring in the Record dialog if you're monitoring through your interface directly.
Sound Forge Pro stopped recording after a Windows update. What happened?
Windows updates sometimes reset microphone privacy settings and can replace manufacturer audio drivers with generic ones. Check Settings, Privacy and Security, Microphone, and re-enable "Let desktop apps access your microphone." If the interface driver got replaced, download the current one from the manufacturer's site, reinstall it, then reselect it in Sound Forge Preferences and click Apply.
Why is Stereo Mix missing on my computer?
Most modern audio interfaces and many laptops don't expose Stereo Mix at all, since it's a loopback feature tied to older Realtek-style chipsets rather than something built into every driver. Check "Show Disabled Devices" in the Windows Sound Recording tab first. If it's still not there, use FlexASIO with a WASAPI loopback device instead.