[gstreamer-bugs] [Bug 493831] [tcpserversink] errors out if first buffer has no caps
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Wed Nov 14 05:58:03 PST 2007
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=493831
GStreamer | gst-plugins-base | Ver: 0.10.14
Tim-Philipp Müller changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |t.i.m at zen.co.uk
Status|UNCONFIRMED |NEEDINFO
Summary|Bug in tcpserversink |[tcpserversink] errors out
| |if first buffer has no caps
------- Comment #1 from Tim-Philipp Müller 2007-11-14 13:58 UTC -------
This seems to be by design: tcpserversink will error out if the first buffer
doesn't have caps set on it (this is so tcpserversink can send stream headers
and the like to newly-connected clients). I'm not sure if this is really
necessary though, possibly it could just treat no_caps the same as
caps-without-streamheaders, as long as the protocol is not GDP.
In any case, for now you need to do something like this:
gst-launch-0.10 filesrc location=foo.txt ! typefind ! tcpserversink
(which may not work if the file is too small or not in ASCII or UTF-8
encoding), or:
gst-launch-0.10 filesrc location=foo.txt ! text/plain ! tcpserversink
or something similar.
--
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=493831.
More information about the Gstreamer-bugs
mailing list