Adobe HTTP Streaming

Adobe HTTP Streaming

www.dsp-ip.comFast Forward Your Development

Agenda

• Background

• Adobe HTTP Streaming

▫ Overview

▫ Components

▫ Files

• Comparison to competing technologies:


• Comparison to competing technologies:

▫ Microsoft “Smooth Streaming” (Silverlight)

▫ Apple “Live HTTP Streaming”

Background

• Video viewing in flash is enabled in several forms:▫ Streaming, Live or VoD

▫ Progressive Download

▫ Pseudo - Streaming


• Each method has its own advantages and disadvantages.

Progressive Download

• Simple• Utilizing existing protocols & servers (HTTP)

• Media file is prepared: metadata up front

• Playback - after metadata is received

• Cache-ability - supported


• Cache-ability - supported

• Seek-ability – very limited support

• Poor user experience - seek, multi-rate

• Waste of bandwidth when not watched fully

• Low cost

Pseudo Streaming• Media is sent as a regular file like Progressive DW

• Server must understand how the media is

structured

• Playback: after metadata is received

• Existing protocols

▫ Non standard server


▫ Non standard server

▫ Non standard client component

• Cache-ability – Limited !

• Seek-ability – supported

• User experience – better than PD, support seek.

• Waste of bandwidth when not watched full

Streaming

• Seek-ability – supported

• Server side – proprietary technology (FMS)

• Cache-ability – requires special servers for streaming

• User experience – very good

• Cost – high


• Cost – high

HTTP Streaming Intro

• HTTP Streaming offers the advantages of:▫ Progressive download in terms of � Cost

� Standard Server

� Scalability

� Standard client components (OSMF)


� Standard client components (OSMF)

▫ Streaming in terms of � User experience

� Seek-ability of streaming

Overview

Adobe HTTP Dynamic Streaming is a solution that allows you to stream live and on-demand content over HTTP to Adobe Flash Player. When content streams over HTTP, clients can seek quickly to any


HTTP, clients can seek quickly to any location.

HTTP Dynamic Streaming supports adaptive streaming, DVR functionality, and Adobe Flash Access protection (DRM).

COMPONENTS

•Content Ingest

•Server


•Server

•Client

Main components

• Preparation

▫ File Packager

▫ Live Packager for HTTP Dynamic Streaming

• Server

▫ Apache module (HTTP Origin Module)

▫ Flash Access


▫ Flash Access

• Client

▫ Player with OSMF classes

▫ Flash Player version 10.1+

▫ Air 2.0+

Adobe Solution main components


Ingest- File Packager• A command-line tool

• Used for converting offline content to formats required for Adobe HTTP streaming

• Translates on-demand media files into fragments and writes the fragments to F4F files.


Ingest - Live Packager

• The Live Packager for HTTP Dynamic Streaming is part of Adobe Flash Media Server.

• The server ingests a live stream over RTMP and translates it into F4F files in real-time. The built-in Apache HTTP Server uses the HTTP Origin Module to deliver the live content over HTTP.


Module to deliver the live content over HTTP.

Server - Apache module (HTTP Origin)

• Extension to Apache HTTP Server version 2.2.

• Enables processes of Adobe Files:

▫ F4F, F4M,F4X

▫ .bootstrap and

▫ .drmmeta

• Flash Media Interactive Server 3.8 includes


• Flash Media Interactive Server 3.8 includes Apache HTTP Server.

Server - Flash Access

• DRM Server

• Flash Access delivers protected media to Flash Player

• For content protection, both File Packager and Flash Media Server are required to package and


Flash Media Server are required to package and encrypt the content

Client - OSMF classes

• The OSMF Player uses the ActionScript 3.0 NetStream.appendBytes() API to deliver bytes to Flash Player. To use this API to create an HTTP Dynamic Streaming player, use the OSMF Player as a reference implementation. However, OSMF is a robust framework designed to deliver high-


is a robust framework designed to deliver high-quality video. Adobe strongly recommends using OSMF to build HTTP Dynamic Streaming players.

ADOBE HTTP STREAMING FILES

F4F, F4M,F4X

.bootstrap and


.bootstrap and

.drmmeta

Files

• The files required for HTTP streaming are:▫ F4F - MPEG4 media format. Holds the media

▫ F4M – Media description file(codec, resolution)

▫ F4X - Fragments location file

▫ .bootstrap – bootstrap information for each segment


segment

▫ .drmmeta – DRM encryption information

F4F File

• Standard MP4 format with open file specification

• Each file contains a segment of the source file.

• Each segment contains one or more fragments of content.

• The file formats stores any flash supported codec except Speex (voice codec).


except Speex (voice codec).

• A player can use a URL to address each fragment.

HTTP Streaming file types

• *.F4X File▫ Flash Index file.

▫ Contains the location of specific fragments within a stream.

• *.F4M File▫ Flash Media Manifest file.


▫ Flash Media Manifest file.

▫ Contains information about the media codecs, resolution, and the availability of multi-bitratefiles.

HTTP Streaming file types

• .bootstrap

▫ Bootstrap file.

▫ Contains the bootstrap information for each segment of the file

• .drmmeta

▫ DRM Header file.


▫ DRM Header file.

▫ Contains additional header information about the encryption.

DSP-IP Contact information

Download slides at: Download slides at: www.dspwww.dsp--ip.comip.com

Course materials & lecture requestCourse materials & lecture request

Adi YakovAdi YakovTraining ManagerTraining Manager

adi@[email protected]

+972+972--99--86519338651933


Projects development services:Projects development services:

+972+972--99--86519338651933

wwwwww..dspdsp--ipip..comcomMailMail :: info@[email protected]:: ++972972--99--88509568850956,,FaxFax :: ++972972--5050-- 89629108962910

Alona AshkenaziAlona Ashkenazi

Development Development ServicesServices

alona@[email protected]

+972+972--99--88509568850956

Education

Adobe HTTP Streaming