GNOME Bugzilla – Bug 601582
pad: Keep track of the configured segment and add API to get it
Last modified: 2011-05-09 10:08:53 UTC
The attached patch keeps track of the configure segment by looking at the NEWSEGMENT events and updates the last_stop for buffers if their offset/timestamp is valid and the segment format is BYTES, TIME or DEFAULT. Also the segment is reset on FLUSH_STOP and after activating the pad.
Created attachment 147491 [details] [review] pad: Keep track of the configured segment and add API to get it
Review of attachment 147491 [details] [review]: ::: gst/gstpad.c @@ +5420,3 @@ + * This function gets the currently configured #GstSegment + * from this pad. The returned pointer is valid as long as + * the pad exists. I guess you mean that the segment is copied, since it doesn't return a pointer.
(In reply to comment #2) > Review of attachment 147491 [details] [review]: > > ::: gst/gstpad.c > @@ +5420,3 @@ > + * This function gets the currently configured #GstSegment > + * from this pad. The returned pointer is valid as long as > + * the pad exists. > > I guess you mean that the segment is copied, since it doesn't return a pointer. Yes, right. The docs are from my first version that returned the segment ;) Thanks
Created attachment 147546 [details] [review] pad: Keep track of the configured segment and add API to get it Fixes bug #601582.
This is fixed different now in 0.11