The whole venue, one fabric
A venue is audio, video, captions, and a dozen operators each on a different system. WAVE puts the Dante audio bridge next to its own video and captions path as one addressable fabric.
A venue is never just audio. There's the console feed, the camera feeds, the captions running for accessibility and compliance, the stream going out to a platform, and a handful of operators who each need a different slice of it — the FOH engineer watching levels, the remote producer watching program out, the compliance team watching the caption track. Today, each of those tends to live in a different system, with a different login and a different vendor.
WAVE's answer is one fabric.
Dante audio — bridged and playing live in a browser, the way it already works today. SDI and NDI video, WAVE's own path, carrying the camera and program feeds. Live captions, riding alongside. All of it arriving through the same infrastructure, addressable as one flow instead of separate systems that happen to be running in the same building.
The takeaway
Dante does audio. WAVE's SDI/NDI handling does video, sitting next to the Dante bridge, not inside it. Keeping that line clean is what makes the fabric trustworthy.
This isn't audio pretending to be video, and it isn't video pretending to be Dante. Dante does audio — that's what it's built for, and that's all WAVE asks it to do. The video in this fabric is WAVE's own SDI/NDI handling, running alongside the Dante audio bridge, not inside it.
One pane, not five logins
The operational win isn't only technical — it's that a venue team stops context-switching between the Dante ecosystem, a separate video distribution tool, a separate captioning vendor, and whatever's stitching a stream together for remote viewers. One WAVE pane surfaces the audio, the video, and the captions as one live picture of the show. An operator watching the fabric sees what's actually happening in the building, not a fragment of it.
Reach, without new infrastructure per feed
The venue doesn't change. What changes is who can reach it. A feed that starts as a Dante source on a LAN in one building can be watched by a producer, a compliance reviewer, or a remote broadcast partner anywhere WAVE runs — the same way listen.wave.online proves it today for audio alone, extended across the rest of the fabric.
Metered as one flow
Vendors typically bill this as a stack of separate line items — a Dante license here, a video distribution fee there, a captioning subscription on top. WAVE doesn't resell any of the underlying licenses and doesn't mark up Dante — Dante interop stays what it's always been. What WAVE meters is the fabric itself: the flow of audio, video, and captions moving through WAVE's infrastructure and reaching the people who need it. One flow, one meter, instead of a stack of vendor invoices that don't talk to each other.
Where this is going
The Dante bridge proved the model: a closed, LAN-jailed system can reach a URL without asking anyone to buy new licenses to receive it. Extending that same model to video and captions is the next step of the same path — run through the same pane, metered the same way.
The building used to be the boundary. With one fabric, it's just where the show starts.