Dante Via vs Virtual Soundcard: Choose the Right Computer Audio Tool

TL;DR — Choose Dante Via when the job is to route individual computer applications or locally connected audio devices and expose selected sources to a Dante network. Choose Dante Virtual Soundcard when a DAW or other audio application needs a predictable multichannel Dante interface for recording or playback. They solve different layers and cannot run simultaneously on one computer. Define the source, destination, channel count, driver, and routing owner before choosing either tool.

Dante Via routes applications; DVS presents an audio interface

Dante Via discovers audio-capable applications and hardware connected to a computer, then lets an operator route those local sources and destinations or expose selected channels to a Dante network. It is designed for flexible application and device routing.

Dante Virtual Soundcard (DVS) turns the computer itself into a Dante audio interface. An audio application selects DVS through ASIO or WDM on Windows, or Core Audio on macOS, while Dante Controller handles network subscriptions.

The choice is not “simple versus professional.” It is application-centric routing versus interface-centric multichannel I/O. A production may use both on different computers, but their responsibilities must remain clear.

Choose Dante Via for application and local-device routing

Dante Via is useful when the source is a browser, media player, conferencing application, USB microphone, USB interface, or built-in computer audio device. The operator can expose only the intended source rather than broadcasting every system sound.

Common uses include:

• sending a video-call return to one Dante destination while sending music elsewhere;
• putting a USB microphone or small interface onto a Dante network;
• routing one local application into another supported local destination;
• monitoring selected Dante channels from a computer;
• keeping notification sounds out of a production route.

Application discovery differs by operating system. On Windows, an application may appear only while it is actively playing or recording. On macOS, software destinations are handled through Via application inputs rather than appearing as ordinary destination tiles. Build the procedure for the actual OS instead of assuming the interfaces are identical.

Choose DVS for a multichannel application interface

DVS is the clearer choice when a DAW, playout system, or capture application needs many named inputs and outputs. The application sees a conventional audio interface, and Dante Controller maps network channels to it.

Typical uses include:

• multitrack concert recording;
• virtual soundcheck playback;
• broadcast or stream capture with a fixed channel map;
• multichannel playback into a console or processor;
• repeatable recording templates tied to Dante channel names.

DVS channel capacity depends on edition, driver mode, and sample rate. Dante Via is not a substitute for a high-channel-count DVS session. The Dante Virtual Soundcard setup guide covers the detailed driver, channel, format, routing, and test workflow.

Decide from the signal path

Start with one sentence: “Route this source to this destination, using this many channels, under this operator's control.” Then choose the tool whose boundary matches the sentence.

Do not choose from a product name alone. A conferencing workflow may still need DVS if the application supports the required interface and fixed channel map; a small recording workflow may prefer Via when it is genuinely application-oriented. Prove the exact workflow.

Understand the routing boundary

Via owns the local graph

Via connects visible local applications and devices. To reach remote Dante hardware, enable the source or destination for Dante, then use Dante Controller for the network subscription. Local visibility and remote routing are separate checks.

DVS owns the computer's Dante interface

DVS exposes receive and transmit channels. The DAW chooses those channels through its audio settings and track assignments; Controller subscribes them to network devices. DVS does not provide Via's drag-and-drop application routing.

Controller remains the network authority

Use Dante Controller to inspect network devices, create remote subscriptions, verify format and clock state, and diagnose route status. Neither product makes network design, authorization, or acceptance testing optional.

Plan the switch between Via and DVS

Via and DVS cannot operate at the same time on one computer. Treat a change between them as a production-state transition, not a casual toggle.

1. Stop playback and recording, and notify affected operators.
2. Save the current Via routes or DVS/DAW state and capture the accepted channel map.
3. Close audio applications that may hold the current driver.
4. Stop the active Audinate application completely.
5. Start the other application and select its intended network interface and format.
6. Reopen dependent applications and choose the correct audio device.
7. Rebuild or confirm Controller subscriptions.
8. Pass identifiable test audio through every required destination.

Do not switch during a show without an approved interruption and rollback plan. The operating system may keep an old audio device selected even after the Audinate application changes.

Compare failure modes

When remote routes fail, use the Dante subscription errors guide. When local applications behave differently across computers, capture the OS version, driver mode, permissions, application state, and exact source-to-destination map.

Computer-audio decision checklist

• The source and destination are named, not described as “computer audio.”
• Required channel count and direction are documented.
• The workflow needs application/device routing or a multichannel interface.
• Operating-system discovery and permissions are tested.
• Via and DVS are not expected to run together on one computer.
• The correct wired Dante interface is selected.
• Sample rate, format, latency, and clock requirements are confirmed.
• Local routes and Controller subscriptions have named owners.
• Notifications, default devices, and unintended system audio are excluded.
• Restart, switch-over, failure, and rollback tests pass with real audio.

FAQ

What is the difference between Dante Via and Dante Virtual Soundcard?

Dante Via routes audio between individual applications, local computer audio devices, and selected Dante paths. DVS presents the computer to an audio application and the Dante network as a multichannel audio interface. Their routing responsibilities are different.

Can Dante Via and Virtual Soundcard run at the same time?

No. Via and DVS cannot run simultaneously on the same computer. Stop one completely before starting the other, reopen dependent applications, restore the intended audio device, and retest the route.

Should I use Dante Via or DVS for recording?

Use DVS for repeatable multichannel DAW recording. Via can suit smaller application-oriented routes or locally connected devices, but it is not the general replacement for a high-channel-count DVS interface.

Does Dante Via work with USB audio devices?

Yes. Via can expose supported audio devices connected to the computer, including USB microphones and interfaces, then route them locally or enable them for use on the Dante network. Verify the driver, permissions, channel map, and actual hardware.

Do I need Dante Controller with Dante Via?

Use Dante Controller when routing Via-exposed sources or destinations to remote Dante hardware and when inspecting network format, clock, and route state. Via handles its local application and device graph; Controller handles Dante network subscriptions.

Put the computer-routing boundary in the Rider

Document the chosen tool, computer, operating system, local source, destination, channel count, driver, Dante interface, Controller routes, test result, and switch-over owner in Techrider.live. Invite the broadcast, recording, and system engineers to edit the same rider, save the accepted design, and inspect history before changing the computer audio path.