HTTP Dynamic Streaming (HDS) enables both on-demand and live adaptive bitrate video transmittal of MP4 media over typical HTTP connections. HDS is an open-format solution that allows online media publishers to leverage existing network and cache facilities to deliver media to the Adobe Flash Platform with high efficiency. As with the other types of adaptive bitrate streaming, HDS can dynamically adjust movie playback quality to match the available speed of wired or wireless networks.
NOTE: If you prefer, you can use the API to rapidly create Adobe HDS streaming files from your source content.
To configure a single video file Add Media for Adobe HTTP Dynamic Streaming, do the following:
- Upload a single piece of media with our Add Media feature. The source video file may reside on Amazon S3, Rackspace CloudFiles, FTP sites, or your local drive / network.
- In the second step of the setup, you will need to setup one or more Output Formats. Choose Adaptive Streaming Formats from the first dropdown menu.
- Next, choose the Adobe HDS All Devices encoding preset from the second dropdown menu.
- Continue with the remainder of the setup.
To configure a watch folder for Adobe HTTP Dynamic Streaming, do the following:
- Follow the instructions in the Watch Folder article.
- In Step 3 (the 3rd segment) of the watch folder setup procedure, where you choose the Output Format, choose Adaptive Streaming Formats from the first drop-down menu.
- Next, choose the Adobe HDS All Devices preset from the second dropdown menu.
- Continue with the remainder of the watch folder setup.
HDS Output from Encoding.com can be used on any Flash Media Server or as an extension to any web server running Apache HTTP Server version 2.2 that is running the Adobe HTTP Origin Module. Click this link to read more from Adobe on the HTTP Origin Module. Adobe HDS enjoys support from many popular third-party Flash players, such as Flowplayer. For more information on Adobe HTTP Streaming technology, visit the Adobe product page.
NOTE: To use Adobe’s HDS, the source media must be in MP4, FV4, or FLV compatible formats. Please transcode your video into one of these formats before using the HDS preset.
SPECIAL NOTE: Because the HDS output creates multiple files from a single source file, you have the option to tar the output (set <output> to tar = yes). If you chose to tar your HDS output, then the file extension of your output video should be set to .tar. Then, in the <destination> field of your request you would specify (for example):
In this case, all of outputs will combine into a single tar ball file-which you may unpack later. Otherwise, set <output> to tar = yes to send all the files unpacked to the directory specified in your destination path.
CRITICAL NOTE: The extension of your output video name(s) should be.f4m. For example, in the <destination> field of your request you would specify the following:
In this example, all of the HDS compatible files will be sent to the root directory /hds, so we reco
The HDS process will create the following outputs and send them to your specific destination:
.f4f segments – The API engine will output one or more F4F files. Each file contains a segment of content from the source file, and each segment contains one or more fragments of content. Any compatible media player can use a URL to address each fragment. Our default multi-bitrate segments are 300k, 600k, and 1200k, but you may customize these (see the parameter table). Always specify bitrates from lowest to highest so that the manifest file will be created accurately. Assuming source file name was myhdsvideo, you would receive the following .f4f files:
.f4m Flash Media Manifest file – Contains information about codec resolution and the availability of multi-bitrate files. Assuming the source file name was myhdsvideo, you would receive the following .f4m files:
.f4x Index files – these files contains the location of specific fragments within a content stream. Assuming the source file name was myhdsvideo, you would receive the following .f4x files: