Matroska Demux Issue

[Luis de Bethencourt]

If I understand the code correctly the main difference between the two
functions is that gst_matroska_demux_search_pos returns a fake index, and
gst_matroska_read_common_do_index_seek returns the index object from the
table.
The fake index generated by gst_matroska_demux_search_pos is a new object
with the information of the previous cluster time.



On 14 July 2014 01:12, Kevin Paul <kevinpaul1985 at hotmail.com> wrote:

> *Problem :* For a particular stream of duration 28 second, once I seek
> between 10th and 13th seconds, the video plays fast for a couple of seconds
> and the catches up with audio and plays normally. This doesn't happen if
> I seek anywhere else.
>
> *Analysis :* Cluster start positions are at 9.9 and 13.976 second. I
> frames are present at 9.9, 10.4 and 13.976 second. Cue points are present
> at every interval of 0.0333 seconds
>
> Once seeked between 10th and 13th second, the search for index is done
> using function "gst_matroska_read_common_do_index_seek" and it returns cue
> point closest to the seek location. But I frame is not present to start
> the video playback. But if I use function "gst_matroska_demux_search_pos",
> it finds correct position to start playback and seek works normally.
>
> Can someone please help me to understand the difference between these to
> functions to search for index. Is it fine to use
> "gst_matroska_demux_search_pos" for finding index instead of
> "gst_matroska_read_common_do_index_seek"?
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140714/24cba11e/attachment.html>