Results 1 to 3 of 3

Thread: Muliti-bitrate playlist for HTTP Streaming vs HTTP Segmented stream

  1. #1

    Default Muliti-bitrate playlist for HTTP Streaming vs HTTP Segmented stream

    what is the difference between Muliti-bitrate playlist for HTTP Streaming vs HTTP Segmented stream?

  2. #2
    Join Date
    Sep 2011
    Posts
    1,933

    Default

    Hi
    Adaptive bitrate streaming allows a seamless change from a high bitrate to a lowers one should you not have the bandwidth to watch a stream without it stopping and starting due to buffering.
    The tutorial for streaming on demand content is below and shows an example of a multi-bitrate playlist using a .smil file
    http://www.wowza.com/forums/content....on-demand-file

    The http San Jose Streaming segmenter only work for live streams and controls are listed in the tutorial here,
    http://www.wowza.com/forums/content....s-(Flash-HTTP)

    Jason

  3. #3

    Default

    HTTP Segmented Streaming refers to the concept of downloading a file via HTTP/Progressive Download. In Progressive Download, the file is just downloaded like any other file, as fast as bandwidth will allow. Segmented Streaming breaks up the file into pieces. Each piece is then downloaded as fast as bandwidth will allow. You can see this in Windows Resource Monitor.

    This is in contrast to "Live Streaming" where the server streams data at the bitrate of the media/video.

    Muliti-bitrate playlist for HTTP Streaming, in the context of Wowza, usually refers to an .smil file that contains references to different streams or VOD media. The different media are encoded at different bitrates. The player opens the .smil and requests different bitrate files based on the current available bandwidth. For HTTP streaming the media will be "Segmented".

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •