[Gstreamer-bugs] [Bug 113180] Changed - Some GstBuffer comments
bugzilla-daemon at widget.gnome.org
bugzilla-daemon at widget.gnome.org
Wed May 21 09:11:19 PDT 2003
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=113180
Changed by in7y118 at public.uni-hamburg.de.
--- shadow/113180 Sun May 18 17:01:55 2003
+++ shadow/113180.tmp.19747 Wed May 21 12:11:19 2003
@@ -113,6 +113,20 @@
offset field is currently updated when creating a subbuffer but any
plugin can change it afterwards. Should we still update the offset
field or let the plugin update it?
------- Additional Comments From wim.taymans at chello.be 2003-05-18 17:01 -------
Ronald, yes, sorry, your code is right. I was confused :)
+
+------- Additional Comments From in7y118 at public.uni-hamburg.de 2003-05-21 12:11 -------
+The offset field needs to be initialized to an INVALID value when
+creating/copying a buffer.
+You may initialize it to the same value as the original buffer in the
+special case where a subbuffers starts at the beginning of its parent.
+
+And if we do a media specific offset field (I still like bytes more)
+we need to define what offset we use for every media format.
+That would require getting caps docs going.
+
+Another thing: Would it make sense to restrict events (seek, discont)
+and buffers to 3 formats (TIME, BYTE, media-specific aka UNITS) and
+allow getting other formats only by querying pads/elements?
More information about the Gstreamer-bugs
mailing list