Page 2 of 2 FirstFirst 12
Results 11 to 11 of 11

Thread: Wowza Media Server 3.5.0 duration/start Bug on HLS

  1. #11
    Join Date
    Mar 2010


    Quote Originally Posted by charlie View Post
    We now add a 10 second offset to the transport stream chunk timecodes (pts and dts values) per Apple's recommendation. Without this the Apple stream validator would throw warning messages. This is also how the Apple segementer works.
    Could you please point where I can read this Apple's recommendation? Is the offset exactly 10 seconds, or it is the same as the chunk duration (which could be changed by cupertinoChunkDurationTarget setting)?

    The reason I'm asking is that some HLS player libraries (such as vitamio) apparently display the playing timestamp shifted by 10 seconds, and this happens apparently because of this.

    Another possible reason for such behavior is that wowza sends chunks numbered from 1 ( #EXT-X-MEDIA-SEQUENCE:1) instead of from 0 ( #EXT-X-MEDIA-SEQUENCE:0), and you've said that there's no way to change this in wowza ( But if you look at an example from Apple (, their playlists use #EXT-X-MEDIA-SEQUENCE:0 (
    Last edited by vlad312; 02-15-2013 at 02:38 PM.

Page 2 of 2 FirstFirst 12

Similar Threads

  1. Streaming from Adobe flash media encoder to wowza media server to encode in HLS
    By adityam in forum Live Streaming and Encoder Discussion
    Replies: 3
    Last Post: 09-17-2013, 08:25 AM
  2. WOWZA BUG! not sending full video duration
    By WebDev4Life in forum Video On Demand Streaming Discussion
    Replies: 1
    Last Post: 07-20-2013, 06:36 PM
  3. Replies: 1
    Last Post: 02-25-2013, 11:05 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