No Sound After Selecting a Virtual Audio Device on Mac
Trace a silent Mac audio path from source app to virtual device, processing engine, physical output, format, and mute state.
A virtual audio device is usually an input to a processing engine, not the final transducer. If selecting it produces silence, confirm the companion engine is running, the correct physical output is selected inside that engine, meters show incoming audio, sample rates agree, and neither path is muted.
Key takeaways
- The Mac app sends to the virtual device; the engine must forward to hardware.
- Meters reveal whether silence begins before or after processing.
- A system extension may be waiting for approval rather than failing.
- Some apps hold a device reference and need restarting after a change.
- Device changes and sleep can leave a stale physical-output reference.
Understand the route
Apple’s Core Audio framework allows virtual devices to appear alongside hardware devices. Selecting one does not guarantee it has a speaker attached. The owning application must receive the stream, process it, and write it to a real interface, built-in output, DAC, or headphones.
This is the single most common misunderstanding behind the symptom. The virtual device looks exactly like hardware in the output menu, so selecting it feels like selecting headphones. It is closer to selecting an input on a mixing desk: audio goes in, and something else has to be running for anything to come out.
Check that the extension is actually loaded
On current macOS, a virtual audio device is often delivered as a system extension that requires explicit user approval the first time it is installed. If that approval was dismissed or never appeared, the device may be present in the menu while the driver behind it is not running, which produces silence with no obvious error.
Approval lives in System Settings under Privacy and Security, and a pending request may need scrolling to find. A restart is sometimes required before the extension becomes active. If the application was installed from a location other than the Applications folder, some installers behave inconsistently, so moving it there and reinstalling is worth trying before deeper investigation.
Find where the signal stops
Play a continuous source and watch the processing app’s input meter. If it is inactive, the source app may use its own output setting or need to be restarted after the device change. If input is active but output is silent, inspect the physical output, master gain, bypass state, and device format.
This single check divides the problem in half and is worth doing before anything else. A silent input meter is a routing problem between the source application and the virtual device. An active input meter with silent output is a problem inside the engine or between the engine and the hardware. The two have almost no fixes in common, so establishing which one you have saves most of the work.
- Source app output: virtual device selected.
- Engine input: meter moving.
- Engine output: physical device present and unmuted.
- macOS output: no competing exclusive or aggregate configuration.
Check sample rate and channel layout
A stereo source, virtual device, and physical output should agree on a supported rate and channel layout. Core Audio can convert many formats, but a driver or application may reject an unexpected configuration. Start with 48 kHz stereo, then restore the desired rate after sound returns.
Audio MIDI Setup is where these settings live and where mismatches are visible. Setting both the virtual device and the physical output to the same rate removes conversion as a variable. If audio returns at 48 kHz stereo and disappears again at a higher rate or a multichannel layout, the problem is format negotiation rather than routing, which points at the physical device's capabilities.
Recover after device changes
Disconnecting a DAC or waking the Mac can invalidate the stored output. Select the built-in output temporarily, then return to the intended device. Restart the source app if it opened the previous device directly. Reinstalling the virtual driver should be a last step after routing and engine state are confirmed.
Applications differ in how they handle device changes. Many follow the system default automatically; others open a specific device at launch and hold that reference until they are restarted. If most audio works and one application is silent, that application is almost certainly holding a stale reference, and restarting it is the fix rather than anything system-wide.
Frequently asked questions
Why does one app remain silent while others work?
That app may have its own output selection or may need to reopen its Core Audio stream after the device change.
Should the virtual device be selected as both input and output?
Usually only as the source app’s output. Select the real headphones or speakers as the processing engine’s physical output.
The device appears in the menu but produces no sound at all. Why?
The device entry can exist while the driver behind it is not running, typically because a system extension is still waiting for approval in Privacy and Security. Approve it and restart if prompted.
Do I need to keep the processing app open?
Yes. The virtual device is an input to that engine, so if the engine is not running there is nothing forwarding audio to your headphones.
Audio works at 48 kHz but not at higher rates. What does that mean?
The problem is format negotiation rather than routing. Check what rates the physical output actually supports in Audio MIDI Setup and set the chain to a rate all stages accept.