The WAVE Media Engine
One engine for getting audio and video anywhere — intact, on time, and metered. We build the hard parts once; every transport is a thin adapter on top.
Solved once — for every transport
Timing, integrity, sync, reliability, and metering are handled by the engine itself. Add a protocol — NDI, SRT, Dante, ST 2110, MoQ — and it inherits all of it. No rebuilding the hard parts per format.
WAVE Clock
LiveA single media clock — PTP (IEEE 1588 / SMPTE 2059-2) → NTP → monotonic — with 100 ns media time + UTC wallclock, so every stream shares one timebase.
Adapter + metering
LiveA uniform duplex adapter interface (open · send · recv · meter · close) and a single wave.usage meter — so every transport is measured and billed the same way.
Integrity
BuildingPer-unit sequence, media-time, and a content fingerprint — so a receiver can verify it got exactly what was sent. ("We get what we send.")
A/V sync
BuildingAudio and video locked to the same media time across adapters — no drift between the ears and the eyes.
Reliability
BuildingSupervised discovery, watchdogs, and circuit-broken reconnect — so a flaky link recovers instead of failing.
Control plane
PlannedAMWA NMOS (IS-04/05/07/08) registration, connection, and control for broadcast interop.
File & record
PlannedMXF, MP4/MKV, and BWF capture/playout alongside the live path.
Cloud fabric
PlannedEBU MXL flow nodes — the same engine, federated across the network.
Every layer, one engine
Open core
The engine core is Apache-2.0 and dependency-free C++17 — an open foundation anyone can build on. Commercial adapters and edge services build on top. Open where it earns trust; metered where it earns revenue.