The engine

The WAVE Media Engine

One engine gets audio and video anywhere, intact, on time, and metered. We build the hard parts once; every transport is a thin adapter on top.

2 live3 building3 planned
The hard parts

Solved once, for every transport

The engine itself handles timing, integrity, sync, reliability, and metering. Add a protocol: NDI, SRT, Dante, ST 2110, MoQ, and it inherits everything already solved. No rebuilding the hard parts per format.

WAVE Clock

Live

One media clock, PTP (IEEE 1588 / SMPTE 2059-2) → NTP → monotonic, carries 100 ns media time plus UTC wallclock, so every stream shares one timebase.

Adapter + metering

Live

One uniform duplex adapter interface (open · send · recv · meter · close) and one wave.usage meter measure and bill every transport the same way. Real SRT, RIST, AES67/RTP, and OMT adapters ship on it today.

Integrity

Building

Each unit carries a sequence number, 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

Building

Audio and video lock to the same media time across every adapter: no drift between what you hear and what you see.

Reliability

Building

The engine supervises discovery, runs watchdogs, and reconnects on a circuit breaker, so a flaky link recovers instead of failing.

Control plane

Planned

AMWA NMOS (IS-04/05/07/08) registration, connection, and control for broadcast interop.

File & record

Planned

MXF, MP4/MKV, and BWF capture/playout alongside the live path.

Cloud fabric

Planned

EBU MXL flow nodes, the same engine, federated across the network.

Three engines, one surface

Carry the media. Clear the payment. Choose the path.

Carry

Media Engine

Move the signal, intact, on time, metered. Clock, integrity, sync, reliability, and metering are solved once; every transport is a thin adapter on top.

 Clear

Money Engine

Move the value, priced, settled, screened, metered. People pay with cards and keys; agents pay over HTTP-402. Same rail, same enforcement.

 Choose

Dispatch Engine

Choose the path: which tier runs the work, at what cost, under whose keys. Metered per decision, so an agent can pay per turn the way it pays per stream.

One API. One gateway. Three planes. Agents transact on all three.

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.

What WAVE speaks