<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12"> <TITLE>MP4 timing issue implementing a dash demux</TITLE> </HEAD> <BODY>  Hi, Following Sebastian advice, we have implemented an MPEG DASH demux based on the HLS demux code. Basically, the demux fetches the MP4 data fragments and pass them downstream. Whenever a new bitrate is selected, a new output pad is created and decodebin2 creates the appropriate decoding chain. In each new chain, decodebin2 instantiates in particular a new isomp4 demux, to which the DASH demux forwards an MP4 header (the initialization header), followed by as many MP4 data fragments. The DASH demux also sends a new segment event to specify the playback offset for that chain. The issue we have is that the isomp4 demux ignores the new segment event and starts timestamping output buffers at 0. This is harmless on some configurations where the video sink outputs frames in decoding order ignoring the timestamps, but on more restrictive configurations, it blocks playback until the new chain catches up with the playback time at which the previous one stopped (and as a nasty side effect, it rapidly drains our download queue, causing playback jerkiness). I am not sure how to handle this: should we force the new chain to seek up to the playback position it is supposed to start ? Should the offset rather be encoded in the MP4 enveloppe ? If so, would it even be parsed by the current isomp4 demux ? Thanks in advance for any explainations (I may have got it all wrong) and/or tips … David Corvoysier Orange Labs </BODY> </HTML>