Dante Virtual Soundcard Setup: Record and Play Back Reliably

TL;DR — Dante Virtual Soundcard turns a wired Windows or macOS computer into a Dante audio endpoint. Before starting it, choose the correct Ethernet interface, driver mode, channel count, sample rate, and Dante latency. Then select DVS in the audio application, route channels in Dante Controller, record a labeled test, and play it back end to end. A visible computer is not proof that the format, clock, route, or DAW is ready.

Dante Virtual Soundcard makes the computer a Dante device

Dante Virtual Soundcard (DVS) presents a computer to audio software as an ASIO or WDM interface on Windows, or a Core Audio interface on macOS. On the network, the same computer appears as a Dante transmitter and receiver. Dante Controller creates subscriptions between its channels and other Dante devices.

DVS is useful for multitrack recording, playback, broadcast capture, conferencing, and virtual soundcheck. It is not a replacement for Dante Controller, a network switch, or a hardware clock source. Standard DVS cannot establish a conventional DVS-to-DVS network by itself because the network still needs a suitable Dante leader clock.

The virtual soundcheck guide explains when playback can support a live workflow. This guide owns the computer and Dante configuration that makes the record-and-playback path reliable.

Prepare the computer before starting DVS

Use a supported, maintained computer with a wired Ethernet connection. Disable sleep for the show window, connect power, confirm adequate free storage, and close unnecessary applications. Treat USB Ethernet adapters, docks, and cable paths as production components: label them and test the exact combination that will travel.

Estimate storage before recording. Use the intended track count, sample rate, bit depth, and duration rather than a generic “plenty of space” assumption. Set the DAW project folder explicitly and confirm that the destination volume can sustain a full-length test.

Only one application can own some professional driver modes at a time. Close applications that may have opened DVS, and stop Dante Via before starting DVS; the two Audinate applications cannot run simultaneously on the same computer.

Choose the audio interface mode

Use ASIO for professional Windows audio applications

ASIO is normally the appropriate Windows choice for DAWs and other professional applications that support it. It exposes the configured multichannel interface and provides application-level buffer controls. Begin with a stable buffer rather than the smallest possible value; reduce it only after a sustained test passes.

Use WDM for Windows communication and media applications

WDM is intended for applications that use normal Windows audio devices. It presents stereo pairs rather than the full ASIO-style multichannel workflow. Match the Windows shared-mode format to the DVS sample rate when shared mode is involved, or Windows may resample the signal.

Use Core Audio on macOS

On macOS, select Dante Virtual Soundcard in the application's audio preferences. Confirm microphone or audio permissions where required by the operating system. Do not assume the system default input or output is the interface selected by the DAW.

Configure DVS before pressing Start

1. Select only the required channels

Choose a channel count that covers the show with a small documented reserve. More channels consume more computer resources and complicate track assignment. Available counts depend on DVS edition, driver mode, and sample rate, so verify the installed version rather than copying another machine's plan.

2. Match the sample rate

Set the DVS sample rate to the production rate, then confirm the audio application uses the same value. A mismatch can prevent subscriptions, force unwanted operating-system conversion, or create files that do not match the handoff. The Dante sample-rate mismatch guide covers network-side format diagnosis.

3. Start with a conservative Dante latency

DVS offers a larger receiver-latency range than many hardware endpoints because a general-purpose computer has scheduling jitter. A 4 ms setting may work on a well-tuned computer; 6 ms or 10 ms provides more tolerance when the system is busy. This DVS setting does not force every other Dante receiver to use the same latency.

4. Choose the correct wired network interface

Select the Ethernet adapter connected to the intended Dante network. Do not select Wi-Fi, a VPN, an inactive dock port, or the wrong redundant-network leg. Check the address and interface identity before the show, especially when several adapters have similar names. The Dante Controller interface guide owns the broader NIC-selection workflow.

Route DVS in Dante Controller

1. Start DVS and open Dante Controller on an authorized workstation.
2. Confirm the DVS device name, IP address, sample rate, channel count, clock state, and domain membership where applicable.
3. Rename DVS channels deliberately if the workflow permits, or keep an external channel map tied to DAW track names.
4. Subscribe the required hardware transmit channels to DVS receive channels for recording.
5. Subscribe DVS transmit channels to the approved destinations for playback.
6. Wait for stable route states and investigate warnings before opening the show file.

Keep capture and playback maps separate. A one-row offset can record the wrong source and later send playback to the wrong destination. The Dante device and channel naming guide explains how stable names support recovery.

Build the DAW session from the channel map

Create one track per approved input, select the matching DVS input, and label the track with source, channel number, and stage ownership. Record-enable only intended tracks. For playback, route each track or stem to the documented DVS output and confirm the console or processor input receiving it.

Do not discover the map by speaking into channels during a show. Run a controlled line test, record at least one identifiable source per path, stop, save, and play the file back. Listen at the destination and compare meters at the Dante transmitter, DVS, DAW, DVS output, and receiver.

Diagnose problems in path order

Preserve evidence before restarting. Capture the time, DVS state, Controller events, DAW meter state, CPU and disk load, and affected channels. Use the Dante network health guide when packet, clock, or switch evidence points beyond the computer.

DVS acceptance checklist

• The computer, operating system, DVS version, license, power, and storage are ready.
• The correct wired Ethernet interface is selected and labeled.
• ASIO, WDM, or Core Audio matches the intended application.
• Channel count, sample rate, encoding, and Dante latency are documented.
• A suitable Dante leader clock is present and DVS is synchronized.
• Controller subscriptions match the input and playback maps.
• DAW tracks and outputs match DVS channel numbers and names.
• A sustained record test completes without dropouts or storage warnings.
• Saved files replay through every approved destination.
• Stop/start, computer restart, and recovery ownership are documented.

FAQ

How do I set up Dante Virtual Soundcard?

Connect the computer by wired Ethernet, choose the correct interface, driver mode, channel count, sample rate, and Dante latency, then start DVS. Select it in the audio application and create the required subscriptions in Dante Controller. Finish with a recorded and replayed end-to-end test.

Should I use ASIO or WDM with Dante Virtual Soundcard?

Use ASIO on Windows for professional multichannel DAWs that support it. Use WDM for applications that rely on standard Windows audio devices. On macOS, DVS uses Core Audio. The application and channel workflow should decide the mode.

Why is Dante Virtual Soundcard not showing in Dante Controller?

Confirm DVS is started, the correct Ethernet interface is selected, addressing is valid, Controller is using the intended network, firewall services are permitted, and the user has access to the managed domain if DDM is present.

Does Dante Virtual Soundcard need a clock leader?

Yes. Standard DVS participates in Dante clocking but does not normally provide the leader needed for a DVS-only network. Keep a suitable Dante hardware clock leader present, or use a specifically supported architecture such as an applicable DVS Pro design.

What latency should I use with Dante Virtual Soundcard?

Use the lowest value that passes a sustained test on the actual computer and workload. Four milliseconds can suit a well-tuned system; 6 ms or 10 ms gives more tolerance for scheduling jitter and busy recording sessions.

Put the computer audio path in the production handoff

Record the computer, adapter, driver mode, channel count, format, latency, Controller subscriptions, DAW map, storage path, test result, and recovery owner in Techrider.live. Invite the recording and system engineers to edit the same rider, save the accepted map, and inspect history before the next show.