[Bug 613351] gst_element_seek() should have async counterpart

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=613351
  GStreamer | gstreamer (core) | git

Sebastian Dröge (slomo) <slomo> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #6 from Sebastian Dröge (slomo) <slomo at circular-chaos.org> 2013-07-18 09:06:34 UTC ---
(In reply to comment #5)
> Do we still have elements that do the actual blocking seek in the seeking
> thread (instead of the streaming thread) ?

Yes, most demuxers and also baseparse.

> In order to validate a specific seek has completed, we should have a way to
> report (via a message and its seqnum) the seek completed by using the same
> seqnum as the seek event.

The segment event after a seek is supposed to have the same seqnum as the seek
event.

> If a certain seek is going to take a long time, shouldn't buffering messages be
> posted ?

PROGRESS messages probably, there's no buffering happening.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.