Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Pushing WebRTC Up That Broadcast Hill
Search
danjenkins
June 01, 2023
Technology
0
67
Pushing WebRTC Up That Broadcast Hill
danjenkins
June 01, 2023
Tweet
Share
More Decks by danjenkins
See All by danjenkins
Building ICEPerf.com
danjenkins
0
79
Using GStreamer to build real-time applications with Golang
danjenkins
0
1.1k
VON: Builder - Controlling Physical Devices with WebRTC
danjenkins
0
85
When Worlds Collide: The Blurring Lines of Real-Time and Traditional Media
danjenkins
0
130
Passkeys, FIDO2, WebAuthn… What does it all mean?
danjenkins
0
160
Spiderman's Uncle Ben and his advice for casting your Web(RTC)
danjenkins
0
120
Don't talk SRT about my WHIP
danjenkins
0
800
WebRTC 101 - How to get started building your first WebRTC application
danjenkins
1
200
WebRTC Reborn London Node User Group
danjenkins
0
130
Other Decks in Technology
See All in Technology
複数サービスを支えるマルチテナント型Batch MLプラットフォーム
lycorptech_jp
PRO
0
330
会社紹介資料 / Sansan Company Profile
sansan33
PRO
6
380k
Codeful Serverless / 一人運用でもやり抜く力
_kensh
7
400
La gouvernance territoriale des données grâce à la plateforme Terreze
bluehats
0
170
Platform開発が先行する Platform Engineeringの違和感
kintotechdev
4
560
データアナリストからアナリティクスエンジニアになった話
hiyokko_data
2
450
大「個人開発サービス」時代に僕たちはどう生きるか
sotarok
20
9.9k
初めてAWSを使うときのセキュリティ覚書〜初心者支部編〜
cmusudakeisuke
1
240
ハードウェアとソフトウェアをつなぐ全てを内製している企業の E2E テストの作り方 / How to create E2E tests for a company that builds everything connecting hardware and software in-house
bitkey
PRO
1
130
BPaaSにおける人と協働する前提のAIエージェント-AWS登壇資料
kentarofujii
0
140
Firestore → Spanner 移行 を成功させた段階的移行プロセス
athug
1
470
なぜスクラムはこうなったのか?歴史が教えてくれたこと/Shall we explore the roots of Scrum
sanogemaru
5
1.6k
Featured
See All Featured
GraphQLの誤解/rethinking-graphql
sonatard
72
11k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
Optimizing for Happiness
mojombo
379
70k
Embracing the Ebb and Flow
colly
87
4.8k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
8
520
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
2.5k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
23
1.4k
XXLCSS - How to scale CSS and keep your sanity
sugarenia
248
1.3M
Six Lessons from altMBA
skipperchong
28
4k
Testing 201, or: Great Expectations
jmmastey
45
7.7k
RailsConf 2023
tenderlove
30
1.2k
The Pragmatic Product Professional
lauravandoore
36
6.9k
Transcript
Streaming Tech Sweden 2023 Pushing WebRTC Up That Broadcast Hill
Dan Jenkins
Dan Jenkins WebRTC & Real Time Media Geek @dan_jenkins @
[email protected]
Founder - Everycast Labs / Nimble Ape Organiser CommCon (19-23 June - UK)
Broadcast Bridge - bring remote collaborators into your professional work
fl ow @everycastlabs broadcastbridge.app everycastlabs.uk
Pushing WebRTC Up That Broadcast Hill
WebRTC Is Now 12 Years Old.
And It Has Barely Been A "Thing" Inside Broadcast Media.
So First... Let's Define WebRTC
WebRTC Allows Two Peers behind NATs To Connect to One
Another
It Uses an ICE Process To Make Those Connections.
WebRTC Allows for Media and Data To Be Sent Over
a Peer Connection
WebRTC Is Encrypted by Default.
A Peer Doesn't Need To Be a Client
An SFU or MCU Is Also a Peer.
WebRTC Media Is Sent as RTP
Which Allows for RTP Extensions To Be Used.
RTX
Absolute Capture Time
Audio Levels
Absolute Send Time
Video Orientation
Playout Delay
Video Content Type
That's Just a Few.
It's a Fantastic Toolset To Have at Your Fingertips.
Some May Say It's Rather Prosumer https://twitter.com/OpenBroadcastSy/status/1662075098172358657
But In Order To Understand Some Of The Whys...
We Need To Look at WebRTCs Past
Google Acquired Global IP Solutions...
And Then Open Sourced WebRTC (YAY!)
The IETF And The W3C Were Then Involved With Standardisation
But at its Core...
WebRTC Was Designed for Conference Calls
"Real Time Media on the Web"
And the IETF Process Was Led by VoIP People
Real Time Media = (Web) Real Time Media
And This Led to Decisions.
Like Using SDP To Handle Negotiation of a Session.
But The Biggest* Decision Was Having No Standard Signalling Method.
(*At Least in my mind)
People Could Use What They Wanted.
JSON Over Websocket
SIP Over Websocket
XMPP
GraphQL
Some Proprietary Binary Format Over Websocket
*N
You Could Do It Your Way
Whatever Made Sense for Your Application
Include SDP? Sure!
Get Rid Of SDP And Fill It In Later?
That Works Too!
But No Standard Signalling Isn't Ecosystem Friendly
SRT, RTMP, NDI, HLS & DASH (And many others)
They Just Work (Mostly)
The Lack of a Common Signalling Layer Was Both Great
and Terrible
Now...
The Lack Of Common Signalling Wasn't The Only Issue.
Lack Of Controllable Latency
Lack Of Encode/ Decode Control In A Browser
Lack Of Control Generally.
Pray Be To The Browser Gods.
But.
WebRTC Has Its Own Superpowers
None
WebRTCs Superpower Is That It Works on Billions of Devices
Without Installing A Thing
Use The Right Tool For The Right Job.
WebRTC In A Browser Is The Right Tool.
For The Right Job.
It Might Just Be A Different Job Than You Expected.
Now...
Let's Take A Look at WebRTCs Present
Works In All Browsers Yes, even on Mobile (Safari, Chrome,
Firefox - Edge is a clone)
Supports New Codecs (AV1, H265)
OPUS RED.
More Than Just libWebRTC (Pion, WebRTC.rs, aiortc, |pipe| to name
a few)
SVC (One Video encoded once resulting in one stream with
multiple qualities)
...But Different Support in Every Browser
Simulcast (Multiple encoded videos sent independently as multiple streams) (Now
includes VP9 and AV1 in Chrome)
...But Different Support in Every Browser
X & Y Features
...But Different Support in Every Browser
Scaling Isn't Simple
Scaling To 100,000s Of Connections
It's Tricky
And Expensive
So WebRTCs Present Is Just Tricky.
However.
Something Is Becoming Simpler...
Standardised & Simple Signalling
WHIP (WebRTC HTTP Ingest Protocol)
WHEP (WebRTC HTTP Egress Protocol) https://eyevinntechnology.medium.com/whip-whpp-for-webrtc-based-broadcast-streaming-2cf469e95299
They Go Hand In Hand.
Let's Take A Look At WHIP
At The Heart Of Both Is A HTTP POST Request/
Response
POST /whip/endpoint/test HTTP/1.1 Host: localhost:7080 Content-Type: application/sdp Authorization: Bearer verysecret
Accept-Encoding: gzip, de fl ate Connection: Keep-Alive Content-Length: 1162 v=0 [..sdp] (WHIP) POST with an OFFER
HTTP/1.1 201 Created Location: /whip/resource/test Content-Type: application/sdp Connection: keep-alive Transfer-Encoding:
chunked Content-Length: 569 v=0 [..sdp] (WHIP) POST RESPONSE WITH ANSWER
WHEP Is the SAME
Super Simple.
And Finally Means Ecosystem Friendliness
Both WHIP and WHEP Are Getting Industry Support
Dolby.io
Cloudflare
Osprey Talon Encoders
OBS
Flowcaster
LiveU
And Lastly...
Broadcast Bridge
What's Coming in WebRTCs Future?
Or...
What Do I Hope We Will See Soon?
WebCodec Support
DRED (Deep Audio Redundancy)
Bringing All Browsers Up To The Same Spec
LOL.
This Is a Web Problem Generally.
So What's In It For You?
Lack of Control?
Issues Scaling?
You're Not Selling Me on This Dan...
But Seriously.
Use WebRTC Right...
And It Will Work Well for You.
WebRTC Isn't Right for Broadcasting to 100,000 People
WebRTC Isn't Right for Broadcasting to 100,000 People (Usually)
WebRTC Is Not Right for Transporting Media Inside a Studio.
WebRTC Is Right for Real Time Collaboration
Where You Need the Lowest Friction
WebRTC Is Right for Weird Network Scenarios
It Is a Tool in the Toolbelt.
And Even Though Web Browsers Frustrate Me
A LOT.
It Is Only Because of the Web Browser That WebRTC
Has Its Superpower
It Works Everywhere
Not Everything Is a Nail Needing a Hammer.
I've Seen Stranger Things Than WebRTC Being Used in Broadcast
That's Me!
Cheers!
Thanks! We're hiring in the UK! https://jobs.everycastlabs.uk @dan_jenkins @
[email protected]
@everycastlabs