Results 1 to 5 of 5

Thread: HDS/HLS and Stream Switching Interruption

  1. #1

    Default HDS/HLS and Stream Switching Interruption

    I successfully implemented a stream switching module using this as a baseline example:

    I noticed that when switching between multiple live and od sources, RTMP(T) handles this switch well during playback. However, when viewing using HDS/HLS, the player just suddenly stops at the moment I make the server-side switch. Is this a known issue? If so, is there a resolution?


  2. #2


    Hello there.

    Do the various streams that are being switched between contain the same FPS and key frame frequency across the set? Also, are the frame size, video and audio codecs the same for all the streams? Are they all H.264 video and AAC or MP3 audio?
    If the codecs are not the same switching will be problematic.

    Another problem could be that HTTP streaming sends chunks to the client. The client needs 3 chunks cached before it starts playing.

    Does the HDS/HLS stream ever start to play after the switch? If so you could try modifying the default packetization settings.

    By default Wowza is set to send 3, 10 second chunks in each packet sent to the client. You can modify this behavior by editing the Application.xml file.
    This guide explains how to control how the Cupertino (iOS device) segmenter segments an incoming live stream:
    How to configure Apple HTTP Live Streaming packetization (cupertinostreaming)
    How to configure Adobe HDS packetization (sanjosestreaming)

    I hope this is helpful in troubleshooting your issue.

    Kind regards,


  3. #3


    The streams vary in keyframe frequency, fps, size, but they are all H264/AAC or MP3. I'll give the packetization settings a try and get back to you with results. Thanks.

  4. #4


    It appears the player stops after a 404 Not Found error on one of the segments during a server-side switch:

    http://<root>/media_b105217.abst/Seg1-Frag171 Failed to load resource: the server responded with a status of 404 (Not Found)
    http://<root>/playlist_b105217.abst Failed to load resource: the server responded with a status of 404 (Not Found)

    The player never plays, but if I press the play button, it resumes playback. I set the chunkDurationTarget to 1s instead of 10s and that did not help. Why does the player stop when a chunk cannot be retrieved over HDS/HLS, but RTMP and RTMPT handles this just fine?

  5. #5


    I am pretty sure this is due to different encodings per stream. Your best bet is to re-encode these streams with the same fps, GOP (key frame frequency), audio/video and frame size.

    You can do this with FFmpeg:
    How to encode video on demand content

    Kind regards,


Similar Threads

  1. nDVR and stream interruption
    By Priority1 in forum AddOn: Wowza nDVR
    Replies: 3
    Last Post: 01-07-2016, 10:57 AM
  2. Problem Switching HLS Streams
    By bighenry in forum Wowza Transcoder
    Replies: 9
    Last Post: 02-28-2014, 10:21 AM
  3. HLS livestream multistream switching problem
    By romild0 in forum Live Streaming and Encoder Discussion
    Replies: 8
    Last Post: 10-16-2013, 02:10 AM
  4. HLS/HDS load testing tool
    By xzerth in forum Performance Tuning Discussion
    Replies: 11
    Last Post: 01-08-2013, 07:08 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