Using HTTP streaming

To use HTTP streaming for a media file, you must supply metadata describing how the media is packaged. You provide this metadata to OSMF in the form of a Flash Media Manifest file (file extension: F4M). Once you create an F4M file, you pass its URL to DefaultMediaFactory, which automatically handles loading the stream.

An F4M manifest file is an XML document containing metadata related to a single piece of media. The manifest file can contain references to more than one instance of the media, such as for multiple bit rates. However, the manifest does not encapsulate more than one distinct piece of media and does not function as a playlist.

Manifest information can include the location of the media, DRM authentication information, media bootstrap information, multi-bitrate information (MBR), and more. For a complete description of the F4M format, see the Flash Media Manifest File Format Specification.

For details on the larger HTTP streaming workflow, including methods of creating F4M manifests for live and recorded content, see the HTTP streaming overview in the document Using Adobe HTTP Dynamic Streaming.

For further information on using HTTP streaming features in your OSMF player, see Optimizing delivery with Dynamic (MBR) Streaming for HTTP and RTMP streams, Delivering DVR features in HTTP and RTMP live streams, and Supporting alternate audio tracks in HTTP Streaming videos.