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, a Steinberg UR22C, and built-in Realtek audio. Last tested July 2026.
Sound Forge Pro plays a file. The meters move. You hear nothing. This is Sound Forge Pro audio not playing in its most common form: the waveform scrolls, playback runs, and your speakers or headphones stay silent. Sometimes it shows up differently, as one channel dropping out, or your Realtek speakers working but your headphones not, or the reverse. All of these are playback problems, not recording problems.
If Sound Forge won't record at all, that's a separate issue with a separate fix, covered in the Sound Forge Pro not recording audio guide. This guide is only about what happens after you hit Play and nothing comes out the way it should. The recording setup guide covers the input side from scratch if you're also setting up a new interface for the first time.
These fixes were tested with local WAV playback, ASIO interface playback, and Windows system output switching on three different setups.
Quick answer: Go to Options, Preferences, Audio, and check the Audio device type for playback. If it's set to your audio interface but you're actually listening through your computer's built-in speakers, or the reverse, switch it to match the device you're actually using. That single mismatch causes most silent playback in Sound Forge.
Don't reinstall Sound Forge yet. If the meters move while you play a file, Sound Forge is reading it correctly. The problem sits after the file leaves Sound Forge: the playback device, the ASIO output pair, the Windows Volume Mixer, or how your interface routes its outputs. Reinstalling won't touch any of those.
Before You Start: Identify the Exact Problem
Different symptoms point to different fixes. Find yours here.
Meters moving but no sound, complete silence. The wrong playback device is selected in Preferences. Go to Fix 1.
Speakers not working, or headphones no sound while the other one works. Windows has a different default playback device than what Sound Forge is using, or your interface has separate outputs for each. Go to Fix 1 and Fix 2.
One channel missing, the other works fine. This is a channel routing problem, usually tied to how your interface maps its outputs. Go to Fix 4.
You can record but output only goes to the recording device, not your speakers. Sound Forge is set up so input and output share one device. Go to Fix 2.
Playback works but you don't hear it, and Sound Forge itself seems muted. Check the Windows volume mixer. Go to Fix 3.
Clicks, pops, or gaps during playback. This is almost always a buffer size issue, or Channel Meters causing overhead. Go to Fix 5.
Playback device shows as None in Preferences. Sound Forge has nowhere to send audio at all. Go to Fix 1.
Fix 1: Wrong Playback Device Selected
Sound Forge Pro decides what to play through based entirely on the Audio device type set in Preferences, not on whatever your Windows default happens to be. If you set your default Windows playback device to your headphones last week, but Sound Forge is still pointed at your audio interface's ASIO driver, you'll hear nothing.
Go to Options, Preferences, Audio. Look at the Audio device type dropdown for the Playback device. Check what's selected. If you're listening through your computer's built-in speakers, this needs to be your Realtek or built-in device, not an ASIO driver for external hardware you're not using right now. If you're listening through an interface, it needs to match that interface's driver.
By default, Sound Forge uses the Wave Mapper, which is supposed to pick a working playback device automatically. If your playback device is set to None instead, Sound Forge can't play anything at all, and you won't get an error message explaining why. Check for that specifically. It's an easy setting to end up on by accident after uninstalling old audio software or swapping hardware.
After changing the device, click Apply. Then test playback on a short file before assuming it's fixed. Some device changes need a restart of Sound Forge to take effect cleanly.
Fix 2: ASIO Won't Let You Split Input and Output Devices
This one catches people who record through an audio interface but want to hear playback through their regular computer speakers. A Sound Forge Audio Studio user on Windows 11 documented this exact problem on the MAGIX forum in 2025: recording through a Steinberg UR22C worked fine while playing back through Realtek speakers, until one day it stopped. Setting the input to the Steinberg forced the output to the Steinberg too. There was no way to split them through the standard Preferences menu.
The fix lives inside the ASIO driver's own control panel, not in Sound Forge's Preferences. Go to Options, Preferences, Audio, Advanced, Configure. This opens your interface's ASIO control panel. Most ASIO control panels let you select audio input and audio output independently from there, even though Sound Forge's own Preferences menu ties them together.
If your interface's ASIO control panel doesn't offer that split either, the practical workaround is to record with the interface selected as your device, then switch Sound Forge's playback device back to your regular speakers afterward for monitoring and mixdown. It's an extra step, but it works reliably.
Fix 3: Windows Volume Mixer Has Sound Forge Muted or at Zero
Windows keeps a per-application volume control separate from your master volume. It's possible for your system volume to be turned up while Sound Forge specifically is muted or turned all the way down in the mixer, and you'd never notice unless you check.
Right-click the speaker icon in your taskbar and open Volume Mixer. Look for Sound Forge Pro in the app list. Confirm its slider isn't at zero and the mute icon isn't active. This is a common one after Windows updates, which sometimes reset per-app volume levels without any notification.
While you're in there, also check that the correct output device is selected at the top of the Volume Mixer window. Windows lets you choose a different playback device for the whole system separately from what any individual app requests, which can create a mismatch with what Sound Forge is trying to use.
Fix 4: One Channel Missing During Playback
Sound Forge shows a stereo waveform, both channels visible, meters moving on both sides, but you only hear one channel through your speakers. Switch to headphones and both channels come through fine. This points to a routing problem between Sound Forge's output and your physical speaker connections, not a problem with the file itself.
A user on Creative COW's forum ran into exactly this on a Focusrite Saffire LE interface: the right channel was missing through the speakers but present through the front headphone jack, even though the meters and waveform in Sound Forge showed both channels correctly. The fix was cycling through different Default Playback Device combinations in Preferences until the right pairing appeared, in that case a specific output pair on the interface rather than the generic default.
If you hit this, don't assume the file needs fixing. Try every playback device option listed under Preferences, Audio, one at a time, and test with a known-good stereo file after each change. Interfaces with multiple output pairs sometimes default to a pair that isn't physically wired to your speakers.
Fix 5: Clicks, Pops, or Gaps During Playback
Sound Forge plays, but you hear intermittent stutters, clicks, or short silent gaps.
Increase the buffer size first, step by step. Go to Options, Preferences, Audio, Advanced, Configure to open your ASIO control panel. Try 512 samples first. If playback still gaps, go up to 1024. One user on the RME hardware forum tracked a stutter to buffers that were too small for playback specifically, and landed on 1024 after 512 wasn't enough, using a different buffer size than what worked fine for recording on the same interface.
Turn off Channel Meters if gapping continues. The Sound Forge Pro manual states this directly: if you experience gapping during playback and the channel meters are displayed, turn them off through the View menu. The meters add real-time processing overhead that can interrupt playback on slower systems.
Check whether the file needs resampling. If your project's sample rate doesn't match what your ASIO device supports, Sound Forge resamples on the fly during playback. You can tell this is happening because the Sample Rate box in the Status Bar displays in italics when the output has been resampled, according to the same manual. Resampling itself rarely causes audible problems, but it adds processing load, which can tip an already strained system into audible gaps.
Fix 6: Sound Forge Sees Your Interface, But Windows Doesn't
An unusual but real scenario: Sound Forge plays through your audio interface without any problem, but Windows Sound Settings shows no audio device connected at all, and other apps like VLC or your browser can't see it either.
This happens because ASIO drivers talk directly to interface hardware and bypass the Windows WDM audio subsystem entirely. A Microsoft support thread from December 2024 confirms this pattern specifically with professional audio tools: Reaper and Sound Forge can use ASIO drivers directly without relying on the Windows default audio subsystem, which is why they work fine while Windows and other players don't recognize the same device.
If this is your situation and Sound Forge already works, you can generally leave it alone. It's only worth troubleshooting further if you also need other applications, like a browser or media player, to use that same interface. In that case, check whether your interface has a driver mode switch between ASIO-specific and Class Compliant modes, since Class Compliant mode is what lets Windows itself recognize the hardware.
Fix 7: Sample Rate, Output Format or Driver Mode Mismatch
If playback is silent, distorted, or plays at the wrong speed, check whether the file's sample rate matches what your selected playback device can actually handle. This is more likely with older built-in audio, an unusual driver mode, or an interface locked to a fixed clock rate than with any modern USB interface, but it's worth ruling out before you assume the problem is something more complicated.
Check your project's sample rate against what your device supports. Try switching the playback device in Preferences to see if a different one plays the file correctly. Open your ASIO control panel through Advanced, Configure and check for a clock source or sample rate setting that might be locked to something other than 44.1 kHz or 48 kHz. If none of that resolves it, use Process, Resample on a copy of the file to bring it to 44.1 kHz or 48 kHz for testing, since those two rates are supported by nearly every device made in the last fifteen years. If dropouts or mismatches keep happening even after these checks, confirm your setup meets the system requirements for the version of Sound Forge you're running.
Common Causes at a Glance
| Symptom | Most likely cause | Fix |
|---|---|---|
| Complete silence, meters moving, output not working | Wrong playback device selected in Preferences | Options, Preferences, Audio, select the correct playback device, click Apply |
| Output only reaches the recording interface, not speakers | Input and output tied to the same device | Split input/output in the ASIO control panel via Preferences, Audio, Advanced, Configure |
| Sound Forge seems muted despite correct device | Windows Volume Mixer has Sound Forge at zero or muted | Right-click speaker icon, open Volume Mixer, check Sound Forge's slider |
| One channel missing through speakers, both present in headphones | Wrong output pair selected on a multi-output interface | Cycle through playback device options in Preferences until the correct pair plays both channels |
| Clicks, pops, or gaps during playback | Buffer too small, or Channel Meters overhead | Raise buffer to around 1024 samples, turn off Channel Meters via the View menu |
| Windows doesn't see the interface, but Sound Forge does | ASIO driver bypasses the Windows WDM subsystem | Normal behavior if only Sound Forge needs the device; switch to Class Compliant mode if other apps need it too |
| Playback sounds wrong pitch or speed | Sample rate mismatch between file and hardware | Use Process, Resample to match your file to a supported rate |
Frequently Asked Questions
Why does Sound Forge Pro show no sound even though the meters are moving?
The meters reflect the audio data in the file, not whether it's actually reaching your speakers. Check Options, Preferences, Audio, and confirm the playback device matches what you're actually listening through. If you switched headphones or speakers recently, this setting doesn't update automatically.
Why can't I use different devices for recording and playback in Sound Forge Pro?
Sound Forge's Preferences menu often ties input and output to the same audio device, especially with ASIO drivers. Open your interface's ASIO control panel through Preferences, Audio, Advanced, Configure. Most ASIO control panels let you select separate input and output devices from there, even when Sound Forge's own menu won't split them.
Why is only one channel playing in Sound Forge Pro?
This usually means the wrong output pair is selected on an interface with multiple outputs, not a problem with the audio file itself. Confirm both channels show activity in Sound Forge's meters first. If they do, cycle through the playback device options in Preferences until you find the pair that's actually wired to both speakers.
How do I fix clicks and pops during playback in Sound Forge Pro?
Raise the ASIO buffer size. Go to Options, Preferences, Audio, Advanced, Configure, and increase the buffer toward 1024 samples. If gaps continue, turn off Channel Meters through the View menu, since the real-time meter display adds processing overhead that can interrupt playback on slower systems.
Does Sound Forge Pro use the Windows default playback device automatically?
No. Sound Forge uses whatever device is set in its own Preferences, Audio menu, independent of the Windows default. Changing your Windows default playback device in Sound Settings won't change what Sound Forge uses unless you also update it in Sound Forge's own Preferences.
Why does Windows Sound Settings show no device connected, but Sound Forge plays audio fine?
ASIO drivers communicate directly with audio hardware and bypass the Windows WDM audio subsystem. This means professional tools like Sound Forge can see and use an interface that Windows itself, or apps like VLC, report as disconnected. This is expected behavior with ASIO, not a fault. It only becomes a problem if you need another application to share the same device.
Why does Sound Forge Pro play through the wrong speakers or headphones?
Sound Forge uses the playback device set in its own Preferences menu, not whatever Windows currently treats as the default. If you plugged in headphones or switched to a different speaker set after opening Sound Forge, the app keeps using whatever was selected before. Go to Options, Preferences, Audio, and manually select the device you're actually listening through.
What does Wave Mapper mean in Sound Forge Pro?
Wave Mapper is a generic setting that tells Sound Forge to let Windows pick whatever playback device is currently set as the system default, rather than pointing at one specific device by name. It usually works fine for simple setups with one speaker or headphone output. It can cause confusion on systems with multiple audio devices, since it silently follows whatever Windows considers default rather than the device you meant to use. Selecting your device by name instead of Wave Mapper gives you more predictable behavior.