[gstreamer-bugs] [Bug 430804] [PATCH] navseek only seeks (sort-of) partially

[GStreamer (bugzilla.gnome.org) <bug...@bu...>]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=430804

  GStreamer | gst-plugins-good | Ver: 0.10.5




------- Comment #3 from Mark Nauwelaerts  2007-04-19 20:01 UTC -------
I am not quite sure if the above means to say that navseek will turn out OK by
itself, due to the (impending) changes in core.
In any event, to elaborate; I think it is particularly about the base_time
manipulation.  In the present (released) situation, the following happens:
let the pipeline play until (e.g.) position 30s, let then navseek perform a 10s
offset forward seek, then playing will continue at (about) 1m10s (= 40s + 30s
running_time), due to sync inspired dropping.  Similar and then even weirder
looking effects happen upon backward seek or subsequent seeks.  This is not a
"seek" one would expect, and in such a form not a comfortable potential debug
help.

With the "full" pipeline manipulation, navseek moves about as (normally)
desired
(definitely for the non-segment/loop seek, which happens in a separate thread
anyway).  So, will all of this (including base_time and related effects) then
happen automaticaly (somehow) ?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=430804.