<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="generator" content="pandoc" />
<title></title>
<style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<p>Hi Francois,</p>
<p>On 2017-02-21 14:46, Francois Cartegnie wrote:</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> Le 21/02/2017 à 14:35, Filip Roséen a écrit :</code></pre>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> If stream is created late, it should be out of sync then, as the
absolute offset dissapears.
http://streams.videolan.org/samples/V-codecs/h264/hdtv-interlaced/stz_split_top_bottom_field.ts</code></pre>
</blockquote>
<pre><code> The incoming timestamps (as seen by the *muxer*) are not guaranteed to
start at any particular offset, which further means that there is no
way to know whether a "stream is created late".
All the *muxer* sees is a timestamp, and it will use that as the
starting offset for whatever it is muxing. The changes incorporated in
the proposed patch does not change any behavior in terms of
discontinuity, nor *"late starts"*.</code></pre>
</blockquote>
<pre><code> It -does- change, and everything is out of sync.
[00007f519c003228] avformat mux error: could not write frame (pts:
12237718190, dts: 12237684823) (pkt pts: 22772, dts: 22806)
[matroska @ 0x7f519c005c40] pts 22856 < dts 22922 in stream 2
[00007f519c003228] avformat mux error: could not write frame (pts:
12237801612, dts: 12237801612) (pkt pts: 22856, dts: 22922)
[matroska @ 0x7f519c005c40] pts 22872 < dts 22939 in stream 2
[00007f519c003228] avformat mux error: could not write frame (pts:
[........]</code></pre>
</blockquote>
<p>I am unable to reproduce the above behavior (which I reckon happens when transcoding the mentioned <code>ts</code> with the <em>avformat muxer</em>). Can you elaborate on how you came to the described log?</p>
</body>
</html>