HTTP Dynamic Streaming enables high-quality (H.264 or VP6), network-efficient HTTP streaming for media delivery that is tightly integrated with Adobe® Access software for robust content protection in the Adobe Flash® Player 10.1 or later and Adobe AIR® 2 or later runtimes. This open format solution allows online publishers to leverage existing network and cache infrastructures to efficiently deliver media content to the Adobe Flash Platform. Adobe Media Server software will continue to be a great option for streaming, multiway communication, as well as advanced interactive experiences such as quick start times and quick seeking. Like Adobe Media Server, HTTP Dynamic Streaming supports quality of service (QoS) monitoring, adaptive bitrate streaming, and DVR functionality. The HTTP Dynamic Streaming workflow includes content preparation tools, fragmented MP4 files that are HTTP cache‐friendly, a playback framework (Open Source Media Framework, or OSMF), and options for protected streaming powered by Adobe Access, continuing to make the Flash Platform the choice for reliable delivery of protected, high-quality playback experiences.
HTTP Dynamic Streaming utilizes the same HTTP server technology used to delivery progressive downloaded video. The new technology is different because it adds:
To deliver a streaming experience over HTTP, media assets need to go through a fragmentation process that can also apply content protection (called fragmenting), and a special module installed in the HTTP server is required. The player can be built using OSMF, just like progressive download.
HTTP Dynamic Streaming builds on the success of streaming delivery through Adobe Media Server. This new technology matches the quality of service, rendering quality, buffer controls, and other important aspects of media delivery required to deliver a great experience to the end user. Adobe Media Server provides a high-performance, turnkey delivery server that can protect and deliver any content with a very simple publishing workflow, with support for multibitrate delivery. HTTP allows the publisher and delivery network to customize and optimize the publishing workflow to maximize capacity and reach, using standard network and caching infrastructures.
HTTP Dynamic Streaming requires Flash Player 10.1 or later or Adobe AIR 2 or later. For fastest deployment, Adobe recommends using OSMF, which is currently supported on Flash Player 10.1 (future support for AIR is planned).
No — unless they're in a location outside the reach of Adobe Media Server, or behind a firewall that doesn't allow RTMP delivery, then they should receive a significantly improved experience. Multibitrate switching will respond just as it does with Dynamic Streaming on Adobe Media Server triggered by expected frame rate and/or bandwidth changes (good or bad).
If developers use OSMF today to develop their media players, then there should be limited impact; however, if developers are creating media players without OSMF, there will be a significant impact — as most of the stream logic occurs in ActionScript® at the client. Adobe recommends all developers consider OSMF for developing media players.
Existing Adobe Media Server/RTMP workflows are fully supported. For content protection, an Adobe Access license will be required to encrypt the live streams. Customers can use third-party live encoders to prepare for HTTP delivery, or contact Adobe for additional options.
A new file format is required (F4F). This new file format is based on the standards-based MP4 fragment format. Reencoding is required only for adaptive bit rate experiences where keyframes are not aligned. Recorded content delivered with HTTP Dynamic Streaming will need to go through a new packaging and protection process.
HTTP Dynamic Streaming is designed for online publishers that deliver to large audiences requiring high capacity and scalability to meet traffic peaks or those customers with high-quality video leveraging the benefits and reach of the Adobe Flash Platform.
HTTP Dynamic Streaming expands the capacity available to media publishers because content delivery networks (CDNs) can leverage more of their network to bring the content closer to the end user, which will help reduce disruptions due to network performance. HTTP delivery also enables content to be cached outside the CDN, helping to reduce delivery costs.
Adobe provides a full-featured HTTP delivery solution with the greatest reach of any media delivery platform.
The best way to implement HTTP Dynamic Streaming within a media player is to use OSMF. OSMF has made it simple to provide a seamless user experience, including parsing manifest files, handling URL requests, integrating Adobe Access protection, utilizing multibitrate delivery, implementing DVR, monitoring quality of service (QoS) metrics, and so on. OSMF has been developed by Adobe and leading experts in the community.
Media playback is started by requesting and parsing a manifest file (F4M). The manifest file contains four main parts:
OSMF will use the information from the manifest file to generate the URLs and begin filling a buffer using new APIs inside Flash Player 10.1. OSMF will also fetch any required DRM keys and use them for playback, also using new APIs in Flash Player 10.1.
During playback, OSMF is responsible for managing fragment requests, monitoring QoS, and switching bitrates if needed.
HTTP streaming can be achieved using standard Apache server software and caching infrastructures. To make this easy to implement, Adobe provides an HTTP module for 32-bit Apache web server (Windows® or Linux®) that can be used for HTTP Dynamic Streaming.
Yes, you can deliver video up to 1080p to the Adobe Flash Platform. HD video can be delivered with bitrates from 700kbps up to and beyond 6Mbps. Like other Flash Player supported delivery methods, HTTP Dynamic Streaming supports H.264 video and VP6 codecs required for the highest quality video on the platform.