[Gstreamer-bugs] [Bug 114208] Changed - filesink now ignores NEW_MEDIA

bugzilla-daemon at widget.gnome.org bugzilla-daemon at widget.gnome.org
Sun Jun 1 11:22:14 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=114208

Changed by rbultje at ronald.bitfreak.net.

--- shadow/114208	Sun Jun  1 13:52:35 2003
+++ shadow/114208.tmp.13989	Sun Jun  1 14:22:14 2003
@@ -20,6 +20,24 @@
 
 For example, i have a pipeline to extract frames from a film using pngenc.
  pngenc generates NEW_MEDIA events between each buffer because each png
 should be in a separate file.
 
 So what is the solution?
+
+------- Additional Comments From rbultje at ronald.bitfreak.net  2003-06-01 14:22 -------
+OK, general idea: NEW_MEDIA was a bad idea. EOS should be enough.
+
+So, when going to PLAYING, filesink openes a file. On EOS, it closes
+it. What should be done is that the application listens to EOS, then
+sets a new (next) filename to filesink and sets the pipeline back to
+PLAYING.
+
+This is basically what NEW_MEDIA was intended to do, except that the
+code was horribly wrong, had memleaks all over the place and was badly
+limited. This proposal works much better.
+
+What's needed is simply that the client app listens to EOS and sets a
+new location and resets the pipeline to PLAYING on EOS (and other
+elements need to use EOS instead of NEW_MEDIA). In PAUSED when a new
+filename is set, filesink must then immediately open it. See attached
+patch.





More information about the Gstreamer-bugs mailing list