SME 2017 - HTML5 workshop

Transitioning from Flash to HTML5
Streaming Media East – Streaming Media University
Monday, May 15, 2017
9:30 am to 12:30 pm

● Pioneers in hybrid video delivery systems to accompany growth in OTT traffic
● Experts in HTML5 video through integrations into open-source & proprietary
players
● Consultants in the transition from Flash to HTML5
Streamroot: Who are we?

And who are you?
Infinite scale, limitless delivery.

I. HTML5 basics
A. Why make the transition
B. APIs: the basics
II. Delving into the migration
A. Support
B. Encoding
C. Formats
D. Players
E. DRMs, ads and business features
F. HTTPs
III. Choosing a web player
A. Modern player architecture
B. Considerations & what to look for
C. Benchmark of open-source and proprietary options
What we’ll be talking about today.

IV. Choosing mobile & STB
Environments
Building blocks
Your player options
Native vs Webview
V. Examples: hls.js & dash.js
Debugging, subtitles, encryption, ads, Streamroot, ABR
VI. Going from POC to production
A. What could go wrong
B. What happens after I do a POC? Workflow, fallbacks, etc.
C. Smoothly transitioning into production: QoS metrics, AB testing
D. Useful tools & links
What we’ll be talking about today.

I. It’s time to switch to HTML5.

I. HTML5 Basics
APIs
1. Media Source Extensions
• Makes HTTP adaptive streaming
possible in HTML5
• Use JavaScript to build streams and
inject data into the video tag’s buffer
Source: W3C specs

I. HTML5 Basics
APIs
2. Encrypted Media Extensions
• Allows for DRMs in HTML5
• Provides a way to interact with
content protection systems
• Plugin-free
• Common Encryption (CENC):
standardized key and encryption
methods - multiple DRMs for same
file
Source: W3C specs

Consider every part of your workflow:
- MSE browser & device support
- Encoding
- Format
- Players
- DRMs
- Ads and other business features
- HTTPS?

Source: Bitmovin
HTML5 Format Support

Encoding
Significant changes on encoding side that
can take some time. Options:
- H.264/AVC → HEVC (H.265)
- VP9 → AV1
Either way:
- Encode to MP4 and then repackage as
necessary for target platforms
- Many vendors out there: Wowza,
Unified Streaming Platform, etc.
Source: Encoding.com 2017 Global
Media Format Report

HDS
Packaging & Formats
Source: Encoding.com 2017 Global
Media Format Report
72%
21%
7%

I. HTML5 Basics
Formats available
Source: Encoding.com

Formats: CMAF
Common Media Application Format:
- ISOBMFF + CENC + H.264/HEVC/etc. + Dash OR Hls manifest
- Apple supports fragmented MP4 in latest HLS version on iOS 10
PROs
Play DASH and HLS from single set of source files!
- Cut storage costs in half, efficient caching
- fMP4 involves less overhead than mpeg-ts
- No more need to transmux
- Single media engine for HLS and DASH
WARNING
- Legacy devices
- DRMs

Formats: CMAF

Standardization efforts

DRM
Switch from token authorization to HTML5 DRM
- Microsoft: PlayReady -> Dash/fMP4 -> CTR
- Chrome, FF: Widevine -> Dash/fMP4 -> CTR, CBC
- iOS: FairPlay -> HLS/TS -> CBC
Keep in mind Flash fallbacks.
Mobile and STB also have DRM capabilities.

DRM
For complete compatibility lists, including mobile and STB:
https://www.buydrm.com/keyos-platform-compatibility-matrix

Advertising
You’ll need to rewrite the client-side Ad selection in HTML5
Good news: Flash ads are dying too!
On Google Ad-exchange:
- No video ads can be added in Flash since April 2017
- No video ads will be served in Flash starting July 2017
But because of legacy, still need some Flash fallbacks...

Server-side ad insertion (SSAI)
A new approach on the market: SSAI.
PROs
- Not blocked by ad-blockers
- A smoother experience
CONs
- possible caching challenges
- not all players are ready

HTTPS
Beware!
Playing HTTP streams even in an HTTPS environment is not an option in HTML5.
Changing to HTTPs can be expensive and long, depending on your CDN.

III. Player architecture
Modern player architecture
Before choosing:
1. Understand the specificities of your use case: type of streaming, user habits,
target platforms, etc.
2. Know your feature requirements: ads, paywall, UX, channels, playlists,
analytics, etc.
More flexible architecture with separation between UX and media engine logic!

It’s like...

… your favorite burger.
It’s like...

UI

Skin
UI

Skin
Ads
Authentication
UI

Skin
Ads
Playlists
Authentication
UI
Social sharing

Skin
Ads
Playlists
Authentication
UI
Media Engine(s)
Social sharing

Skin
Ads
Playlists
Authentication
Media Engine(s)
UI
Media Engine(s)
Social sharing

Skin
Ads
Playlists
Authentication
Social sharing
Media Engine(s)
UI
Media Engine(s)
Playback
& DRM

Skin
Ads
Playlists
Authentication
Content
decryption
module
Media Engine(s)
DRM
Manager
UI
Media Engine(s)
Playback
& DRM
Social sharing

Skin
Ads
Playlists
DRM
Manager
Decoder /
Renderer
Authentication
Content
decryption
module
Media Engine(s)
UI
Media Engine(s)
Playback
& DRM
Social sharing

1. Skin - the graphic design
of your player
User Interface

1. Skin - the graphic design
of your player
2. UI logic - features defining
all interaction with the user
on top of video playback
Lots of plugins available, video.js for
example
User Interface

3. Business logic
Authentication
Payment
Ads
*Configuration / device detection logic!
User Interface

Sample UI workflow with authentication, channels and pre-roll ad
User Interface

Easily customizable, with many plugins available for use or inspiration.
Add features as plugins/modules to the core UI base.
Create a unified user experience across browsers, even if the media engine behind it
may vary from device to device.
Check out tools such as React native, Haxe
User Interface

Media Engine

Extremely important yet too often neglected.
Most often necessary to have several media engines to reach your audience.
Media Engine

Decoder & DRM manager

1. General criteria
- device, format and codec dependencies
III. What to look for
2. Custom features
- DRMs
- DVR subtitles
- QoS, etc.
3. Perfs & Quality
- startup time
- ABR
- error strategies
4. Street cred, robustness, ease of use

Light-touch dev:
- Simplicity and stability of the media engine
- Assess extensibility & ease of incorporating special features
- Media engine customization
- Events exposed
- Debugging
Digging deeper:
- Robust yet flexible core design
- Tests and testing coverage
- community & support
III. What to look for

III. What’s out there?
Disclaimer!
- What follows are all GOOD options.
- We’ve tried to be solely objective based on our research and experience.
- Features, support and upkeep are always changing.

PROs
Supported by DASH-IF
Pushed & maintained by Akamai + tier-1s (BBC)
Highest visibility, big community
Lots of features and use-cases handled
Widely used in production
Huge test suite + online test page
CONs
A little bit of technical debt and complexity
Non-trivial API and customization config
H264/AAC support only

PROs
Built by an entire at Google: solid & smart
Performances and robustness, quick to improve
Simple to get started, good tutorials
Only one supporting WebM, VP8, VP9, open audio codecs
Good support on github and Google groups
CONs
Google-centric
Today lacks some features for large broadcasters
Stricter PR & features policy
No ES6 support
Fewer OVP and open-source all-in-one integrations

PROs
Created by Dailymotion, built from scratch by author of Flashls
Enormous traction and visibility
Clear architecture design, easily extendable
Good robustness and debug demo, responsive support
Widely used in prod by all-in-one players + tier-1s
CONs
Some restrictions from the transmuxing & HLS: no DRMs today,
only AES128

PROs
Seamless Flash fallback with a MediaSource polyfill
De facto solution for HLS with VideoJS
Large community of users (Brightcove + Videojs)
In production with Brightcove with a wide range of customers
CONs
Videojs plugin: not usable without videojs
Lack of public debug tools or pages
Learning curve on providers & tech behind it

But there are also a lot of off-the-shelf options.

Different environments:
- Mobile web (Safari on iOS, Chrome on Android)
- Native Apps
Different APIs, different access levels… often more restrictive than web!
IV. Mobile and other platforms

Building blocks: iOS
Base player: AV Player
No low level-APIs
HLS
Fairplay
Browsers: no MSE on Safari, but native HLS support

-
Building blocks: Android
Base Player: MediaPlayer
Low level APIs:
- MediaCodec (like MSE)
- MediaDRM (like EME)
Extended open-source framework: ExoPlayer
DASH, HLS, mp4, Smooth...
Widewine
Browsers: as on Desktop, supports MSE!

-
Building blocks: Other devices
TVos: like iOS
Android TV: like Android + Playready
STBs:
- Android TV based
- Chromium/Opera Middle-ware based
- Proprietary frameworks (legacy)
SmartTVs:
- big fragmentation (Android, Tizen, proprietary…)
- Not following standards very well

-
What players to choose?
Build yourself:
- AV Player on iOS
- Exoplayer on Android
Off-the-shelf:
- all built on AV Player & ExoPlayer
- unified UX, UI & config
- adding some bonus features
(simpler DRMs, offline storage, etc)

-
HTML5 approach?
iOS:
- no MSE in Safari, nor in Webview
Android:
- can use MSE-based players directly with a WebView!
PROs
Same code and logic on Desktop & Mobile
Comparable performance
Easier UX & UI: HTML & CSS
CONs
Less options than with ExoPlayer
Need to know JS & HTML5

-
DRMs
iOS:
- Fairplay, only on the latest versions
Android:
- Widewine
So if you are using DRMs, you will need at least Widewine, Fairplay & Playready to
have a good devices support.

All available online on github:
https://github.com/streamroot/benchmarking-player
Contains:
Media engines code
Media samples
Examples
V. Examples

MSE example
https://github.com/streamroot/benchmarking-player/blob/master/samples/mse.html
V. Examples

Hls.js examples
https://github.com/streamroot/benchmarking-player/blob/master/samples/hls.js/hlsjs.html
https://github.com/streamroot/benchmarking-player/blob/master/samples/hls.js/hlsjs-AES.html
https://github.com/streamroot/benchmarking-player/blob/master/samples/hls.js/hlsjs-subtitles.html
https://github.com/streamroot/benchmarking-player/blob/master/samples/hls.js/hlsjs-ads.html
https://github.com/streamroot/benchmarking-player/blob/master/samples/hls.js/hlsjs-streamroot.ht
ml
Online debug demo: debug http://dailymotion.github.io/hls.js/demo/
Videojs Ads plugin: https://github.com/videojs/videojs-contrib-ads
Ads state diagram: https://raw.githubusercontent.com/videojs/videojs-contrib-ads/master/ad-states.png
Hls.js Events: https://github.com/dailymotion/hls.js/blob/master/API.md#runtime-events
Video Events simulator: http://docs.youbora.com/video-event-simulator/
Streamroot Clappr integration: https://github.com/streamroot/clappr-p2phls-plugin
Strearmoot Videojs integration: https://github.com/streamroot/videojs5-hlsjs-p2p-source-handler
V. Examples

Dash.js examples
https://github.com/streamroot/benchmarking-player/blob/master/samples/dash.js/dashjs.html
https://github.com/streamroot/benchmarking-player/blob/master/samples/dash.js/dashjs-widewine.ht
ml
https://github.com/streamroot/benchmarking-player/blob/master/samples/dash.js/dashjs-subtitles.ht
ml
https://github.com/streamroot/benchmarking-player/blob/master/samples/dash.js/dashjs-ads.html
https://github.com/streamroot/benchmarking-player/blob/master/samples/dash.js/dashjs-streamroot.
html
Online debug page:
http://dashif.org/reference/players/javascript/v2.3.0/samples/dash-if-reference-player/index.html
Dash.js metrics & events: http://cdn.dashjs.org/latest/jsdoc/module-DashMetrics.html
Dash.js ABR logic: https://github.com/Dash-Industry-Forum/dash.js/wiki/ABR-Logic
Streamroot Videojs integration: https://github.com/streamroot/videojs5-dashjs-p2p-source-handler
V. Examples: Dash.js

Other media engines
https://github.com/streamroot/benchmarking-player/blob/master/samples/shaka.html
https://github.com/streamroot/benchmarking-player/blob/master/samples/videojs.hls.html
V. Examples

What could go wrong?
- - Encoding
- - DRMs
- - HTTPS
V. The Path to Production!

I did a POC. Now what?
- - Do you need a Flash Fallback?
- - Moving the UX to HTML5
- - Build the media engine extendable architecture (providers)
- - (optional) choose a Fallback alternative
https://github.com/streamroot/videojs5-hlsjs-source-handler/blob/master/lib/videojs5-hlsjs-source-handler.js
https://github.com/videojs/video.js/blob/66922a818e588b8954989c439e1be790777966ae/docs/guides/tech.md
https://github.com/faisalman/ua-parser-js

Making a smooth transition.
- - HTML5 player rollout
- - Playback & QoS Metrics
- - AB Testing!

AB testing pipeline: General setup

Client AB testing methods:
1) Dynamic Config Injection
2) Different builds with a reverse proxy
AB testing pipeline: General setup

How much time does it take?
The build vs. buy tradeoff.
- Do I have the internal resources to develop,
integrate, customize and maintain?
- Are the features I need already available in
off-the-shelf and/or open-source solutions?
Consider time to market.

Questions?

Nikolay Rodionov, Co-Founder and CPO, nikolay@streamroot.io
Erica Beavers, Head of Partnerships, erica@streamroot.io
Get in touch!

SME 2017 - HTML5 workshop

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à SME 2017 - HTML5 workshop

Similaire à SME 2017 - HTML5 workshop (20)

Dernier

Dernier (20)

SME 2017 - HTML5 workshop