AW: Timestamping problem

[Thornton, Keith]

I have discovered that what I thought was the problem is in fact not the problem.
I am recording a 30 second video. Our application logic analyses the frames and decides that a certain region is interesting for our customers.
I play it back by sending seek to the pipeline 
E.G.
ret = gst_element_seek(m_pPipeline, 1.0, GST_FORMAT_TIME, static_cast<GstSeekFlags>(GST_SEEK_FLAG_KEY_UNIT | GST_SEEK_FLAG_FLUSH), GST_SEEK_TYPE_SET, m_from, GST_SEEK_TYPE_SET, m_till);
where m_from could be something like 6422000000 and m_till could be 16442000000.
I can repeat this for one and the same video several times
The pipeline is in PLAYING but sometimes the return code is 0 and sometimes the return code is 1 
Which means sometimes it plays the whole 30 seconds and sometimes the required 10 seconds. 
This is the problem which I am trying to solve.

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] Im Auftrag von Nicolas Dufresne
Gesendet: Donnerstag, 17. Dezember 2015 21:48
An: Discussion of the development of and with GStreamer
Betreff: Re: Timestamping problem

Le jeudi 17 décembre 2015 à 10:30 +0000, Thornton, Keith a écrit :
> Hi
> I have a pipeline in which my encoder (using Intel INDE on Windows 7
> x64) encodes an H264 Stream and passes the encoded frames to qtmux.
> My encoder sets the pts and dts timestamps as I would expect.
> When playing the resulting video qtmux adds a value of 39:01:18 to the 
> PTS. While this doesn’t affect the playback, it makes seeking 
> impossible.
> Presumably my encoder is not setting some initial value correctly.
> Can anyone explain what this mysterious addition is.
> I am using the current Git Master on Windows7 Regards

What do you set in the segment ?

Nicolas