Results 1 to 7 of 7

Thread: Best HLS packetizer setting for given bandwidth

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Question Best HLS packetizer setting for given bandwidth

    Hello and good time of day.

    Can you give some tips how to determine the most suitable settings for given channel bandwidth to minimize stalled time?
    We using version 4.0.4

    Thanks in advance.

  2. #2


    Hello there.

    I am not sure exactly what you are asking here.

    You can use this guide to configure the HLS packetization:
    How to configure Apple HLS packetization (cupertinostreaming)

    To estimate how much memory is used to store the chunks for a single live stream, use the following formula:
    [total-memory-mb] = ([stream-bitrate-kbps]/([1024-kb-per-mb]*[8-bits-per-byte])) * [cupertinoChunkDurationTarget-seconds] * [cupertinoMaxChunkCount]

    For example, a 500 kbps stream consumes the following amount of memory, given the default settings from the guide:

    (500/(1024*8)) * 10 * 10 = 6 MB of memory

    To calculate the number of connections you can support, you can use this formula:

    number of users * stream bitrate + 20% IP overhead = total server bandwidth

    With a 1g nic (20% overhead accounted for) = 800mbs throughput, which is 800 1 mbs streams, or 1600 500kbs streams.

    You will have to test your actual server/network using the load test tool, or monitoring utilization in production. You must be properly tuned. And to achieve maximum levels you may have to tune your server and network in other ways outside Wowza.

    I hope this is helpful.

    Kind regards,


  3. #3


    Big thanks, i read this article and it was helpful, but i it not what i asking.

    I should detect what values of cupertinoChunkDurationTarget, cupertinoMaxChunkCount, cupertinoPlaylistChunkCount, cupertinoRepeaterChunkCount are the best for live channel when broadcasting to mobile devices, but have no idea how to check channel health with set of parameters not only by own eyes.

  4. #4


    HTTP streaming sends chunks to the client. The client needs 3 chunks cached before it starts playing.

    By default Wowza is set to send 3, 10 second chunks (cupertinoPlaylistChunkCount) in each packet sent to the client.

    Chunks must start on a key frame. So it is best to use a key frame interval that is factor of the cupertinoChunkDurationTarget setting.
    Try 2 second key frame frequency and cupertinoChunkDurationTarget "2000" (2 seconds)

    cupertinoMaxChunkCount is the total number of chunks that are maintained. So as the stream moves a bit further off of live, the player will start to request segments from further in the past. Having a larger list of chunks in reserve will insure this does not lead to a missing chunk error.

    Kind regards,


  5. #5


    Thanks, it helps keep stream live, but don't helps determine it's quality.

    Ok, i try to search not so strait method, may be javascript script that scan video current time and alert if video stalled for more then 2 seconds.

  6. #6


    I am sorry, but I am not clear on what you are asking.

    Can you please try to explain it again?

    Thank you.


Similar Threads

  1. HLS packetizer responses for invalid streams
    By johnsterling in forum Live Streaming and Encoder Discussion
    Replies: 6
    Last Post: 07-01-2014, 04:01 AM
  2. Cupertino packetizer - on chunk ready?
    By aegeli in forum Wowza Streaming Server Java API
    Replies: 2
    Last Post: 06-12-2014, 10:45 AM
  3. Setting up Wowza for HLS chunking and streaming
    By spence in forum General Forum
    Replies: 5
    Last Post: 10-24-2013, 12:07 PM
  4. Packetizer how to disabled?
    By dilonge in forum AddOn: Transcoder
    Replies: 7
    Last Post: 12-18-2012, 10:29 AM
  5. Packetizer events
    By slalompoint in forum Server-side Modules and Code Samples Discussion
    Replies: 4
    Last Post: 01-17-2012, 07:53 AM

Posting Permissions

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