The interchange for live media.
Any protocol in. Any protocol out. Perfectly in sync. WAVE Interchange sits seven live-media formats — SRT, RTMP, WebRTC, HLS, MPEG-TS, fMP4, and Dante/AES67 — on one internal representation, so converting between any two of them is a round trip through the same fabric, not a one-off bridge.
Bidirectional, both proven live: mux — separate video + Dante audio into one synchronized stream — and demux — split a stream back out into its parts.
Seven formats, one internal representation
Each format is backed by its own round-trip conformance test proving lossless conversion through the shared representation.
How it works
Every format enters and leaves through the same internal representation, so adding a conversion path is a matter of implementing one codec's in/out adapter, not N² bespoke bridges.
1. Ingest
A source stream arrives in any of the seven supported protocols — contribution (SRT, RTMP), real-time (WebRTC), delivery (HLS, fMP4), broadcast (MPEG-TS), or pro audio (Dante/AES67) — and is normalized into the shared representation.
2. Synchronize
The sync engine aligns every frame against a shared clock, keeping audio and video locked to sub-millisecond precision — whether they arrived on the same wire or two completely different networks.
3. Emit
The synchronized IR is re-encoded out to whichever protocol the destination needs — the same fabric handles a straight remux (protocol A → protocol B) or a demux (one stream → its separate video and audio parts).
What teams build on the fabric
Interchange is the protocol-crossing layer under WAVE's real-time media rails — here's what it's built to carry.
Mux a camera feed with a Dante audio bed — in sync
Take a video contribution feed (SRT, RTMP, WebRTC, MPEG-TS) and a separate Dante/AES67 audio program, and interchange muxes them into one synchronized output stream — sub-millisecond drift, proven live.
Bridge protocol islands without a hardware gateway
SRT contribution in, HLS or fMP4 delivery out. RTMP in, MPEG-TS out to a broadcast chain. One shared representation in the middle means every protocol pair is a round trip, not a bespoke bridge.
Demux a synchronized stream back to its parts
Split one interchanged stream back out into its original video and Dante audio components — for monitoring, QC, or routing audio to a separate console — with the same sync guarantee running in reverse.
Remux and demux as a metered API
POST /v1/av/remux and /v1/av/demux on api.wave.online — Bearer-authenticated, metered per minute and per transform-second. Build protocol conversion into your own pipeline instead of standing up transcoding infrastructure.
A metered API, not a one-off tool
Auth, entitlement, and metering run through api.wave.online — this spoke is the front door. Call the API directly to build protocol conversion into your own pipeline.