WEBVTT

00:00:00.000 --> 00:00:01.950
There is a class of video where a second

00:00:01.997 --> 00:00:04.923
of delay breaks the experience: a guest on a

00:00:04.969 --> 00:00:08.615
live show, an agent answering in a conversation, two

00:00:08.684 --> 00:00:12.005
operators in a shared control room. For that class,

00:00:12.063 --> 00:00:15.522
the transport is Web R T C — built

00:00:15.568 --> 00:00:19.516
for low-latency, two-way media in the browser. WAVE runs

00:00:19.609 --> 00:00:23.034
real-time on its own edge. The real-time layer is

00:00:23.080 --> 00:00:25.727
an edge Web R T C S F U

00:00:25.901 --> 00:00:29.175
on Cloudflare — whip to publish, whep to play,

00:00:29.291 --> 00:00:31.857
terminated close to the user so the round trip

00:00:31.915 --> 00:00:36.234
stays short. WAVE adds the rest: broadcast transports next

00:00:36.269 --> 00:00:39.671
to it (N D I, Dahn-tay, O M T,

00:00:39.868 --> 00:00:43.304
Mock), captions and voice, and one open A P

00:00:43.467 --> 00:00:47.438
I over the whole set. Edge-native, open on top.

00:00:48.413 --> 00:00:50.596
When to reach for Web R T C. -

00:00:50.735 --> 00:00:54.728
Two-way interaction. Anything where both ends talk and latency

00:00:54.775 --> 00:00:58.583
is felt. - Browser-first. No plugin, no app —

00:00:58.908 --> 00:01:02.089
it runs where the viewer already is. - Sub-second

00:01:02.136 --> 00:01:05.816
targets. When the budget is hundreds of milliseconds, not

00:01:05.886 --> 00:01:09.369
seconds. For one-to-many delivery where a few seconds of

00:01:09.427 --> 00:01:12.480
latency is fine, H L S is cheaper and

00:01:12.550 --> 00:01:15.789
simpler. Web R T C is the tool when

00:01:15.812 --> 00:01:20.874
the interaction is the point. What "sub-second" depends on.

00:01:21.199 --> 00:01:23.846
Latency is a chain, and the transport is one

00:01:23.893 --> 00:01:27.852
link: - Network path. Pushing media to the edge

00:01:27.910 --> 00:01:31.567
keeps the round trip short. - Encode and decode.

00:01:31.950 --> 00:01:35.096
Real-time codecs and modest G O P settings over

00:01:35.166 --> 00:01:39.230
long ones. - Jitter buffer. Smaller buffers cut delay

00:01:39.299 --> 00:01:42.318
and cost a little resilience — a deliberate trade.

00:01:42.759 --> 00:01:45.348
- The far end. A caption that is two

00:01:45.417 --> 00:01:48.564
seconds late is useless; an agent that takes 800

00:01:48.622 --> 00:01:52.709
ms to answer breaks the turn. WAVE runs this

00:01:52.790 --> 00:01:56.319
layer edge-native so the path stays short, and exposes

00:01:56.377 --> 00:01:58.885
the controls through the A P I instead of

00:01:58.943 --> 00:02:03.645
burying them in a console. Using it through WAVE.

00:02:04.028 --> 00:02:06.884
The real-time transport is one option on the same

00:02:06.942 --> 00:02:10.541
A P I as everything else: Start a real-time

00:02:10.576 --> 00:02:13.734
session, or fan the same source out to H

00:02:13.850 --> 00:02:16.393
L S for the audience that does not need

00:02:16.428 --> 00:02:20.270
to interact — one A P I, two transports.

00:02:20.874 --> 00:02:23.301
Under the hood that publishes over whip and plays

00:02:23.347 --> 00:02:25.948
back over whep at the edge (), but you

00:02:26.006 --> 00:02:28.130
address it the same way you address any other

00:02:28.177 --> 00:02:32.124
transport — by naming it in the call. Where

00:02:32.171 --> 00:02:35.863
it fits. Web R T C is the conversational

00:02:35.909 --> 00:02:40.193
link. WAVE makes it one transport among many, agent-payable

00:02:40.228 --> 00:02:43.247
through the same gateway, so a real-time call and

00:02:43.305 --> 00:02:45.662
a broadcast delivery look the same from the A

00:02:45.813 --> 00:02:49.493
P I's point of view. - Real-time and transports:

00:02:49.876 --> 00:02:53.615
docs dot wave dot online - A P I:

00:02:54.056 --> 00:02:56.842
A P I dot wave dot online