DDMF VirtualAudioStream [WiN]

• Product: VirtualAudioStream
• Developer: DDMF
• Version: 2.0.2
• Format: VST, VST3
• Requirements: Windows 10 or later
• Source: virtualaudiostream.com

VirtualAudioStream is a Windows loopback audio driver and VST/VST3 effect rack from DDMF, providing four virtual stereo cables at 192 kHz/32-bit for routing audio between applications. The rack inserts any installed VST or VST3 plugin between one program’s output and another program’s input, processing up to four soundcards independently. It replaces a hardware patch bay on a single Windows machine. A streamer routing Discord and a DAW through one shared limiter, or an engineer capturing a Zoom call through DDMF’s own EQ, uses the same four cables.

Key Takeaway

Activation happens when a Windows setup needs plugin processing on signal that never touches a DAW — a livestream mix, a podcast call, or the system’s own output. It complements a DAW rather than replacing one; the effect rack carries no timeline or automation, just a saved routing graph. Anyone already inside one DAW skips it.

Four Cables, One Kernel-Level Buffer

Four virtual stereo cables install as Windows playback and recording devices, running eight channels at up to 192 kHz/32-bit. Selecting Stream 1 as the playback device for one application and Stream 1 as the recording input for another moves audio between them without a physical connection.

The DirectSound routing path has produced audible clicks and crackles independent of buffer size on some Windows installs, an artifact tied to the loopback driver’s kernel-level buffering rather than to any plugin riding on top of it. Switching the same stream to ASIO output removes the artifact on machines with a compatible interface.

A podcaster feeding one stream into OBS for a live broadcast gets four separate cable pairs to keep guest audio, a music bed, and voiceover physically isolated in the routing graph, without opening a mixer application to do it.

Patched Live, Never Automated

The effect rack hosts VST and VST3 plugins in a graphical patch view, one chain per soundcard, with up to four soundcards processed in parallel. Cables drag from the output pin of one module to the input pin of the next — the same gesture used to route a plugin into any of the four cable pairs.

Chain state isn’t versioned or automated. Closing the rack keeps the last saved graph, but there’s no timeline to ride a parameter change into a chorus or automate a bypass mid-broadcast; a move made now stays fixed until it’s changed by hand again.

A streamer building a Discord-plus-game chain drags in a compressor and a noise gate once and leaves the graph running for the session. A mastering engineer chasing per-track automation curves is working in the wrong tool.

A Limiter Bundled, Not Built In

Buying the higher tier adds DDMF’s own IIEQPro parametric equalizer and NoLimits2 brickwall limiter as ready-to-drop modules inside the same rack, instead of sourcing a third-party EQ and limiter separately for the routing chain. Both drop into any of the four soundcard chains the same way a free VST would.

The bundle costs $70 over the $39 base price, and neither plugin gains anything the rack doesn’t already extend to any other properly licensed VST or VST3 EQ and limiter — no tighter integration, no exclusive routing option tied to owning them.

A broadcaster who wants brickwall control on a live system mix without hunting a separate limiter plugin gets one purchase covering both cabling and processing. Anyone who already owns a preferred limiter can skip the $70 add-on entirely.

One Closed Window, Four Dead Streams

Setting a virtual stream as the Windows default playback device redirects all system audio — a browser tab, a game, a Skype call — into that stream’s recording input, where any standalone recorder or a DAW’s input can pick it up. This restores the system-audio capture that Windows removed as a default “Stereo Mix” option on many drivers.

All four cables depend on the same effect rack process. Closing the rack application drops every stream at once, including cables carrying no plugins at all — a background capture running unattended goes silent the moment the rack window closes, intentionally or not.

A podcaster capturing a co-host’s Skype audio alongside the local mic track keeps both on separate streams for independent mixing later. Anyone recording only their own microphone doesn’t need a second cable at all.

FAQs