Studio-grade DRM packaging: Package content for a single DRM workflow that targets the desktop, connected TVs, tablets, and smartphones, including iOS and Android devices, when you include Adobe Access 4.

On-demand packaging for HTTP: Deliver video using HTTP for Adobe Flash Player compatible and iOS devices without preparing the assets ahead of time. On-demand packaging makes publishing easier by requiring one set of video files to deliver to multiple devices with or without Flash Player installed.

Protected HTTP streaming for iOS: Deliver high-quality live and on-demand video to devices and HTML5-enabled browsers that support the HTTP Live Streaming (HLS) video format with the same media and live streams as those for Flash Player. Full adaptive bitrate can be used without disruption.

Protected HTTP streaming for Flash Player: Protect your content streamed to the desktop and devices using HTTP with reduced complexity thanks to real-time encryption, cacheable key delivery, and player binding.

Adobe Access DRM support: Dynamically segment and encrypt content with the Adobe Access DRM policy for HLS on iOS. Apply sophisticated business rules and policies to support premium video experiences for live, linear, and on-demand video.

Adobe Media Server provides several protection schemes for content ranging from encrypted Real Time Messaging Protocol (RTMPE) and SWF verification to Protected HTTP Dynamic Streaming (PHDS) through either HDS or HLS. These methods are an adequate form of protection for the majority of premium content available today. Adobe Access is a studio-grade DRM solution that provides the most hardened forms of protection, including the enforcement of business rules like rental periods and license revocation. Using them together, you can package and protect premium content for the broadest possible device landscape, even in native apps on the iOS platform through the inclusion of the Adobe Access for iOS library in your Objective-C projects.

The primary difference between Adobe Media Server 5 Professional and Flash Media Interactive Server 4.5 is the ability to package and protect your premium content for the broadest possible device landscape, even in native apps on the iOS platform through the inclusion of the Adobe Access for iOS library in your Objective-C projects.

Adobe Media Server 5 Professional will appeal to broadcasters and media distribution companies with large video libraries that need to be published across a diverse device landscape, as well as media distribution companies and broadcasters that require strong DRM protection for licensed content. Media Server 5 also supports the FCC's requirements for closed captions and extends the protection options for native iOS apps.

Streaming from within your network infrastructure is potentially more cost effective. You can control access and delivery channels, plus manage the load on your network with the origin/edge configuration of Adobe Media Server. You can also deploy deep authentication and interactive solutions that content delivery networks (CDNs) do not support. In addition, you can support more advanced media delivery options including multicast and multicast fusion using encrypted RTMFP.

Adobe product compatibility — Get broad desktop support through Flash Player, coupled with very rapid adoption when new versions are released.

On-demand HTTP Dynamic Streaming — You can package F4F files in real time from existing MP4 or FLV video files, simplifying the workflow for HTTP delivery and eliminating the need for prepackaging content for Flash Player.

Stronger protection — You can protect adaptive bitrate video on demand and live streams at the same time to Flash Player-compatible and iOS devices. Add even more digital rights management (DRM) protection with Adobe Access, with consistent support across desktops, devices, and select connected TVs.

More secure multicast, including multicast fusion — You can support higher quality video in your enterprise without impacting your network, now with enhancements such as stream replication, server-side recording, and rebroadcast.

A more robust experience— With applications like Adobe Connect™ and partners like Akamai constantly driving the technology, Adobe Media Server has real-world deployments that are robust and difficult to duplicate.

No. Adobe Media Server can be configured as a remote origin server for HTTP delivery. If you don't want to run your own origin, Adobe is working closely with CDN partners to enable HTTP and RTMP services. Contact individual partners to learn more about their plans.

On-demand packaging in Adobe Media Server can support the packaging of hundreds of files at the same time. Once a file has been packaged, it will remain in the HTTP cache for the next person. When used with HTTP caching technologies (such as Varnish or SQUID) and CDNs, scalability increases dramatically. If you are streaming only a few files to a large audience, the demand on Adobe Media Server is low. If you are streaming a large number of different files to an audience, the impact on the server increases. For iOS streaming, there is no additional impact on the server capacity. For streaming with encryption, there is an impact on the number of concurrent files that can be packaged.

Yes, Adobe Media Server supports RTMP edge caching configurations. The origin and edge architecture provides the caching services required for large and distributed installations. You can also use both of these editions to split live streams to multiple locations to improve load balancing.

RTMFP applications are now more easily scalable with the new introduction forwarding features that allow multiple servers to be used to manage your P2P group.

You can find extensive online documentation and support files for Adobe Media Server on the resources page, along with a wealth of tutorials and sample code in the Adobe Media Server Developer Center. If you require a higher level of product support, you can enroll in one of Adobe's support programs.

Adobe maintains a directory of Adobe Media Server solution providers. Their services range from encoding and publishing to advertising, delivery, and consulting. You can also find helpful experts on Adobe Forums for Adobe Media Server and related discussion lists. Or check the list of resources at the bottom of this page.

Yes. High-definition video can be delivered via Flash Player using either the VP6 or the H.264 codec. H.264 can deliver great quality at lower bitrates. HD delivery is supported in both live and on-demand over all protocols. HD video delivery is best used with dynamic streaming (RTMP or HTTP). HD video is streamed with either a 480p or 720p frame size with bitrates as high as 2–3Mbps.

Adobe Media Server supports dynamic streaming with media encoded in multiple bitrates. Dynamic streaming lets you switch smoothly between these video files to help ensure a high-quality experience for the video consumer. Dynamic streaming can be used with RTMP or HTTP to Flash Player, or HLS delivery to Apple iOS.

Adobe Media Server supports IP multicast streaming and recording for live video to Flash Player 10.1 or later. Multicast is a highly optimized method to deliver high-quality video to a very large audience with virtually no impact on the server as demand increases.

Adobe Media Server can generate a multicast broadcast from any live RTMP stream or a linear stream from a server-side playlist. Flash Player 10.1 and later clients do not need a server connection to receive the stream. Multicast is very useful for large-scale broadcasts within enterprise networks.

Video players developed with Open Source Media Framework (OSMF) will have full support for IP multicast.

Source-specific multicast (SSM) lets you generate and consume both SSM and any-source multicast (ASM), enabling stream replication, server-side recording, or rebroadcast over separate multicast channels or RTMFP groups. SSM support reduces the demand on the network resources while also improving the security of the streams.

Streaming video through Adobe Media Server can support more concurrent high-quality streams per server than progressive download because streaming serves only the portion of the video that's requested. This can potentially save you substantial bandwidth charges — which could more than offset the cost of Adobe Media Server licensing. Adobe Media Server can also determine the most efficient stream to deliver to a client — either before streaming even starts with native bandwidth detection or during playback using RTMP Dynamic Streaming.

The different versions or pieces of content are synchronized (the video timelines must match)

Audio or other data in each content stream is synchronized with the video data in that stream

To provide users with the smoothest experience, when you encode the content, follow these recommendations:

Ensure that the video keyframe interval (keyframe frequency) and frame rate are consistent across the different versions of content. A shorter keyframe interval lets the server switch streams more quickly, which means the client can have a smaller playback buffer.

Use a consistent audio bitrate.

Use a consistent audio sample rate as much as possible. For low-end encodings, you can save bandwidth by using mono audio rather than stereo.

Adobe Media Server offers full support for all streaming and communication protocols including application-level multicast using peer-assisted networking and Protected HTTP Dynamic Streaming. It also supports protected adaptive bitrate streaming to Apple iOS using the HLS format.

RTMP streaming establishes an encrypted session between the Flash Player client and Adobe Media Server to deliver video and real-time communications. RTMP requires a server connection for every stream being delivered. RTMP scaling is achieved by chaining multiple servers together to cache video content. RTMP is compatible with applications developed using Flash Player or AIR.

HTTP streaming does not maintain a persistent connection. Video is delivered by a series of HTTP requests from the player that is controlled by manifest files. Video is broken up into a series of smaller files (called segments or fragments) that are cached in the network to reach large scale. Protection is applied when files are packaged into the smaller fragments or segments.

Adobe Media Server supports two HTTP file formats: HLS for iOS devices and HDS for Flash Player compatible devices. HTTP streaming is optimized for mobile delivery because of its caching features.

HLS is a file container format optimized for Apple devices. The container supports H.264/AAC-encoded video/audio and is based on MPEG-2 transport stream (TS). All video delivered to iOS (including AIR for IOS) must use this format.

HDS is a file container format optimized for applications that run in Flash Player. The container also supports H.264/AAC-encoded video/audio and is based on MPEG-4 TS. HDS is not supported on AIR for iOS.

Adobe provides one of the leading online digital media delivery platforms with full support for standards-based H.264. Flash Player supports all encoding profiles of H.264; the codec is also built into the hardware of many mobile devices and can provide optimal viewing experiences without draining the battery.

You can leverage the same video and audio assets across multiple devices including iOS and those compatible with Flash Player, which helps reduce your storage and content management. Flash Player 9 and later supports the playback of formats derived from the MPEG-4 container such as F4V, MP4, M4A, MOV, MP4V, 3GP, and 3G2 if they contain H.264 video and/or HE-AAC audio. iOS and the HLS format support MPEG-2 TS with H.264/AAC codecs.

There is no software limit set on the number of simultaneous RTMP streams you can serve on Adobe Media Server, but your configuration, server hardware, and infrastructure may cause limitations in capacity.

By default, Adobe Media Server installs an embedded HTTP server. This allows you to deploy SWF and HTML files from the same computer on which it is installed. You can also deploy JPEG, GIF, and many other file types. The HTTP server can also be used to deliver video and audio content via HTTP if RTMP fails. The Apache server has been preconfigured as an origin server for HTTP Dynamic Streaming, allowing you to deliver video on demand or live adaptive bitrate video using the embedded server.

RTMP enables multidirectional communication from Flash Player to Adobe Media Server. This protocol allows the client to control the stream delivery quality and security. RTMP has different modes that include two real-time encryption modes: SSL (RTMPS) and RTMPE. It also allows multiway interactive applications to send data back and forth. RTSP is an insecure, one-way protocol. With RTSP, alternate solutions and workflows are needed to protect your content (such as digital rights management). In addition, multidirectional communication is not possible with RTSP. For multicast delivery, RTMFP is fully encrypted transport over UDP and will operate in the same network configurations as RTSP.

You can deliver multicast to multiple offices that are not connected with a multicast-enabled WAN link. This can be done using the multipoint publishing feature, enabling Adobe Media Server to subscribe to an RTMP stream from the ingest server and rebroadcast in the local area network (LAN). For networks with a multicast-enabled WAN connection, no additional servers are required.

Adobe Media Server can negotiate port blocking, either by “tunneling” streams via RTMPT or by automatically defaulting to HTTP delivery if streaming is not permitted by the client's connection. The result is a smooth viewing experience for all clients. For peer-assisted networking, RTMFP has the ability to traverse most firewalls and network address translations (NATs).

Yes, Adobe Media Server enables delivery of adaptive bitrate streams at the same time to iOS. You can stream to the Safari browser using an HTML5 player or an Objective C ("native") application. You can also use Adobe AIR for iOS to develop a rich video experience on iOS. HLS streams delivered to iOS devices can be protected with AES128 encryption. Both live and on-demand streaming to iOS can use the integrated HTTP origin.

Yes, you can stream video from Adobe Media Server to AIR for iOS with full hardware acceleration support for optimal battery life. Video must be streamed using Apple's HLS format to use the hardware acceleration feature.

There are many ways to integrate advertising with your video content. If you have a custom player, you can use ActionScript to intersperse ads in any way you like. You can even integrate with an ad server to use its tracking and management features. Easily integrate with third-party ad networks and APIs by utilizing the OSMF plug-in architecture.

Real-time ad insertions or synchronized data cues can also be added to custom video players using the customizable HTTP packaging APIs in Adobe Media Server, enhancing the delivery and monetization of video to Flash Player compatible and iOS devices.

For a list of Adobe partners that can offer assistance in video development and content delivery, visit the partner page.

The best way to deliver live video is by broadcasting through Flash Media Live Encoder, free software that allows you to stream and archive video from almost any source, ranging from webcams to high-end capture cards. It supports VP6 or H.264 codecs and connects to Adobe Media Server, which then broadcasts your stream to connected clients. Alternatively, you can broadcast directly from Flash Player, which is ideal for videoconferencing. Flash Player 11 now supports higher quality video with H.264 encode. Download Flash Media Live Encoder for Mac OS and Windows®.

Streaming media using RTMP or RTMFP, including multicast, helps protect your content because media is not cached by the client. Streaming media using HTTP progressive, HTTP Dynamic Streaming, or HTTP Live Streaming (HLS) can be cached and requires additional protection measures.

Stream encryption is enabled with RTMPE and RTMFP protocols.

HTTP Dynamic Streaming can also be encrypted in real time using either Adobe Access or Protected HTTP Dynamic Streaming with a simple configuration.

SWF file verification (with RTMP) helps ensure that the video player accessing your video is actually your video player and not a modified or spoofed version of it. SWF file verification is also supported with content protected by Adobe Access.

HLS streaming to iOS devices can use protected HLS streaming and key delivery over SSL. For more information, see the white paper.

Implementing RTMPE is easy — you only need to specify it in your connection string (for example, rtmpe://myFMSserver.com/vod). You can also choose SSL, which requires a certificate. RTMPE does not require a certificate.

To implement SWF file verification for RTMP connections, place a copy of the SWF or Adobe AIR file on Adobe Media Server. Easy configuration options, including support inside the C++ plug-ins, help you integrate with your network environment.

To implement SWF file verification for Protected HTTP Dynamic Streaming , use the SWFHasher tool installed with Adobe Media Server and place the SWF hash into the same directory as your video files. For more information, see the white paper.

Yes, you can use domain whitelists/blacklists to further protect your content from unauthorized access. Multicast streams do not require server connections, so more advanced access controls will be required in the network or at the client.

Using Adobe Media Server with server-side ActionScript, you can verify that the client is authorized to play the video through a variety of metrics, including referrer, domain, IP address, or even Flash Player version. ActionScript can be used to manage requests made to Adobe Media Server. You can protect SWF files from being reused or modified when using RTMP and help prevent unauthorized connections with SWF file verification.

C++ can also be used to manage authorization by creating custom plug-ins for Adobe Media Server. Plug-ins can be used to closely integrate into your network. You can also leverage databases or user management services such as LDAP using plug-ins. With Adobe Media Server, you can create C++ access plug-ins (such as the Authentication plug-in for Adobe Media Live Encoder).

Media packaged with Adobe Access protection can also be streamed with Adobe Media Server.

Yes. Using AIR for IOS, you can develop video chat and voice chat applications that interact with Flash Player or AIR clients running on other devices or desktops. You can use RTMP or RTMFP protocols for communication, and you can use the built-in camera on iOS devices.

Yes, Adobe Media Server can be used to enable rich video chat applications with Flash Player 10.1 on devices that support camera and microphone. You can build apps to enable communication with desktop players or integrated communication solutions. Video chat is enabled with the multidirectional RTMP or the new peer-assisted networking protocol, RTMFP.

If you program for Adobe Flash Professional or Adobe Flash Builder® software and know ActionScript 1.0, 2.0, or 3.0, getting started with Adobe Media Server is easy. You'll use some additional communication classes utilized in both client-side and server-side code in your interactive applications. Explore an extensive list of helpful articles and documentation on the resources page.

For even more inspiration and useful code examples, try the Flash Media Interactive Server Feature Explorer, a cross-platform desktop application built on Adobe AIR. This application hosts more than 30 examples of streaming and multiway communication solutions, including basic server connection examples, complex video streaming, and authentication routines. You can also learn to build video messaging and VoIP solutions.

Adobe Media Server applications can be developed just like any other rich media content, using either Flash Builder or Flash Professional CS6, with the final application being deployed as a SWF file. Server-side code can be written in any text editor or using Flash Builder or Flash Professional.

Adobe provides numerous tools and resources to help ensure your streaming and interactive applications are robust. The Adobe Media Server administration console lets you monitor your server and is also a server-side debugger. A rich administration API lets you build your own custom unit test applications. The interactive debugger in Flash Professional also helps. In addition, Adobe maintains an up-to-date Knowledgebase on Adobe.com.

Data push, a unique and powerful feature of Adobe Media Server, is enabled using remote shared objects. Remote shared objects can contain complex data that is shared among connected clients. Whenever the data is changed, all connected clients are notified of the change event and the data is automatically updated. This allows you to create rich real-time applications with features such as stock updates, live chat, shared whiteboards, and more. For RTMFP applications, you can use directed routing and posting functions of the peer-to-peer group to send data messages, and enable robust scaling with new distributed peer groups.

Yes, Flash Media Interactive Server 3.5 or later supports recording of streams using the H.264 codec, directly on the server. Archive high-quality live streams so you can quickly deploy the content on demand after your live event is over, and use the free F4V flattener utility to prepare your file for video editing using Adobe Premiere Pro CS6. New multicast enhancements in Adobe Media Server enable server-side recording of multicast streams.