HTTP Dynamic Streaming: Getting Started


Published on

HTTP Dynamic Streaming enables leveraging of existing caching infrastructures - for example, content delivery networks, ISPs, office caching, home networking - and provides tools for integrating content preparation into existing encoding workflows.” That is great, but what does it mean for me?

To answer this question we’ll cover the following:

What is HDS?
How do I get started with HDS?
When should I use HDS?
How can I integrate HDS into my content creation workflow?

Recorded Presentation:

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Intro\n\nBlog series ( &\n
  • RTMP\n– Delivering content over RTMP is called “streaming”.\n– Media is delivered to the client continuously over a socket connection.\n– The client can seek to any point in the media stream regardless of what has been downloaded.\n\nHTTP\n– Delivering Content over HTTP is called “Progressive Download”.\n– The content must transfer to the client machine from beginning to end.\n– The client cannot seek until the location has downloaded. \n- No special server is needed.\n
  • HTTP Dynamic Streaming combines HTTP (progressive download) and RTMP (streaming) to provide the HTTP streaming feature set. Flash Media Server is not required for on-demand content.\n• Clients can access and begin playing content “instantly”.\n• Clients can “seek” to points in content that have not yet downloaded.\n
  • • On-demand content\n• On-demand multi-bitrate content -> “adaptive streaming” and “dynamic streaming”\n• Live content\n• Live multi-bitrate content\n• Live content with DVR functionality\n• Live multi-bitrate content with DVR functionality\n• Flash Access is also available for each of these use cases\n
  • - f4fpackager\n- F4M File\n- F4F Files\n- HTTP Origin Module\n- OSMF Player\n
  • Command line utility from Adobe\nWindows and linux only\n\n
  • - XML formatted file that contains information about a Flash media asset.- \n- This is the file that is loaded as the media content \n- It is up to the player to inspect play back the media content\n- Bootstrap info for segments & fragments\n- MBR\n- Flash Access \n- This can include:\n- Media location\n- Media type\n- Media bootstrap\n- Multi-bitrate (MBR) availability\n- Codecs\n- Resolutions\n- Digital Rights Management (DRM) authentication\n- DVR information\n- moov atom, metadata block and XMP metadata block\n\nMore detailed information\n\n\n
  • - Container file for segments and fragments\n- Based off of the F4V file format spec\n- ***Package the sample.f4v and review the output\n\n
  • - The data flow for the origin module\n1. Request F4M from player\n2. The player inspects the F4M \na. Bootstrap data to determine what segment/fragment to request for playback\nb. MBR \nc. Flash Access to authenticate\n3. The player request the segment and fragment from the server\n4. The origin module pulls the correct segment/fragment pair using data from the .f4x file and delivers it as a response to the request.\n5. The Player assembles the fragments for playback\n
  • - Flash Media Playback & Strobe Media Playback\n* Play back a stream using FMP\n- Custom Player using OSMF\n- package \n* Review the sample player for playback \n
  • \n
  • - No access to Apache 2.2 - which the origin module requires\n- F4FExtractor\n* Show the sample of extracting the files, uploading to S3 and playing back the fragments\n- Works for any other HTTP server \n
  • Intro\n\nBlog series ( &\n
  • HTTP Dynamic Streaming: Getting Started

    1. 1. HTTP Dynamic StreamingGetting started with HDS
    2. 2. RTMP vs. HTTP
    3. 3. HTTP Dynamic Streaming
    4. 4. When do I use HDS?
    5. 5. The Pieces & Parts
    6. 6. The f4fpackager
    7. 7. Flash Media Manifest Files (F4M)
    8. 8. F4V Fragment Files (F4F)
    9. 9. The HTTP Origin Module
    10. 10. The Player - OSMF
    11. 11. HDS & Live Content
    12. 12. Delivering HDS from Amazon S3
    13. 13. Questions?@jccrosbyjohn@realeyes.com