Player integration requirements
AMD is designed for use with standard media players, such as an Open Source Media Framework (OSMF) player, JWPlayer, Flowplayer, HLS.js, and DASH.js. For the most part, modifications to the player are not necessary to deliver content through AMD.
There are a few requirements you should be aware of.
Do you need token authentication in your player?
If you use token authentication to secure the links to your content, you may need to modify your player to support the token exchange that takes place between our Edge servers and your player. These changes vary depending on the format of the content you're serving. The requirements are the same for both live and on demand delivery.
|DASH (via DASH.js)||
If you are using DASH.js for playback of Dynamic Adaptive Streaming for HTTP (DASH) content, you’ll need to make some modifications to DASH.js to include support for token authentication.
We offer a DASH support player
You can access a player supported for use with DASH and AMD at: http://players.akamai.com/dash/.
You don't need to modify a player to support token authentication for Apple HTTP Live Streaming (HLS) format media.
To support token authorization for HTTP Dynamic Streaming (HDS) content, you’ll need to incorporate some changes to the native OSMF player. These changes will account for transfer of the token as a query string parameter in requests from the player.
Contact your Account Representative for additional details.
Are you using prepackaged streams?
This applies if you're delivering your streams from prepackaged files, as opposed to
presegmented files. For example, if your content is comprised of contiguous
fragmented MP4 files, and not individual MP4 chunks, you’ll need to append the
parameter to the playback URL: