[gstreamer-bugs] [Bug 500447] EOS and EOF across a named pipe is .... difficult

[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=500447

  GStreamer | gstreamer (core) | Ver: HEAD CVS

Mark Nauwelaerts changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manauw at skynet.be




------- Comment #2 from Mark Nauwelaerts  2008-03-02 21:56 UTC -------
I could be overlooking something here (at this time of the day :) ),
but wouldn't the problem also be solved by running the 2 pipelines in separate
instances of gst-launch (rather than in 1 instance as seems to be the case
now).
After all, with 2 processes, if the first one reaches EOS, gst-launch should
exit, which will take down the first filesink, and close the fd.
So, cat gets an EOS, can finish its business, and the second filesrc should get
EOS, and shut down.  In summary, the following works for me:
mkfifo rpipe epipe
cat <rpipe >epipe &
gst-0.10 gst-launch filesrc location=myfile1 ! queue ! filesink location=rpipe
&
gst-0.10 gst-launch filesrc location=epipe ! queue ! filesink location=myfile2

Alternatively, the following element (or one like it) might be useful (part of
a transcoding oriented set):
http://gentrans.sourceforge.net/docs/head/gst-entrans-plugins/html/gst-entrans-plugins-procpipe.html
It is meant to make piping data through external processes easier to integrate
into a pipeline, and has been tested sucessfully (e.g. using mp2enc from
mjpegtools as a layer 1 encoder, if one would really want to ...).


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