[gstreamer-bugs] [Bug 499771] New: using a fifo as filesink doesn't seem to work

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

  GStreamer | don't know | Ver: HEAD CVS
           Summary: using a fifo as filesink doesn't seem to work
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: don't know
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: bouvigne at mp3-tech.org
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Using:
gst-launch  filesrc location="./testfile" ! filesink location="./testfifo"

with ./testfifo being a fifo is failing due to a tentative of seeking
on./testfifo.

Since #343312 was closed, filesink is reporting tentative of seeking on non
seekable outputs. In the current case, it properly reports the error.

However, it seems that this still doesn't work. From reading
gst_file_sink_event within gstfilesink.c, I noticed that in case of
GST_EVENT_NEWSEGMENT, the filesink element would issue a seek.

In my case, the problematic seek request tries to seek at offset 0 (from debug
output of gst-inspect).

I think that it might be because a GST_EVENT_NEWSEGMENT is initially issued,
and filesink then tries to seek, even if it's requested to seek at the current
(initial) position.


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