[gstreamer-bugs] [Bug 561224] Plugin resettime: Subtract a base time from the timestamps of passing buffers.

[GStreamer (bugzilla.gnome.org)]

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=561224

  GStreamer | gst-plugins-bad | Ver: HEAD CVS




------- Comment #3 from Arnout Vandecappelle  2008-11-24 09:08 UTC -------
(In reply to comment #2)
> The usual way for making a sink lock on to the current running_time is to set
> it to playing with a custom base_time.

I may be mistaken, but doesn't that only work for sources?  The use case is
something like:

Initial pipeline:

videotestsrc ! tee name=t ! queue ! matroskamux ! filesink location=...

After dynamic reconfig:

videotestsrc ! tee name=t ! queue ! matroskamux ! filesink location=... \
                        t ! queue ! matroskamux ! filesink location=...

Both files start at a different absolute time, but both should start at 0
running time.  So setting the source's base_time is not an option.

In this situation, you need something that changes timestamps in the middle of
the pipeline.  identity actually does that, but you have to supply it with the
new base_time - and for that you need to probe pad buffers to find out the
first buffer's timestamp.  Writing a new plugin was much simpler.  I could have
added it to identity, of course, but my feeling is that identity is already way
overloaded.

I must admit, this element probably fits more in gentrans (which already
contains most of identity's functionalities as separate elements).  If you
prefer I can add it there.


-- 
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=561224.