tcp with uridecodebin / playbin ?

[stic]

Hi,

is there a way to use tcp source uri (tcp://...) with uridecodebin or playbin elements ?

Thanks.
_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Sebastian Dröge-3]

On Do, 2014-04-17 at 17:58 +0200, [hidden email] wrote:
> Hi,
>
> is there a way to use tcp source uri (tcp://...) with uridecodebin or playbin elements ?

There are two TCP sources (tcpclientsrc and tcpserversrc), but both
don't implement an URI handler.

You could implement a custom subclass of GstBin that implements the
GstURIHandler interface and implements the TCP protocol you want to use,
but having a generic "TCP" URI handler does not make much sense IMHO.

--
Sebastian Dröge, Centricular Ltd - http://www.centricular.com
Expertise, Straight from the Source

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[amitchawla]

Hi Sebastian,

"having a generic "TCP" URI handler does not make much sense IMHO"

Could you please explain why it doesn't make sense?

Actually I was looking at playbin to wait for a movie stream at a TCP port.... so tcpserversrc seemed to the answer. Do I have any other way to implement that ?

Thanks for your thoughts.

Amit

[Jan Alexander Steffens]

On Apr 19, 2014 19:08, "Sebastian Dröge" <[hidden email]> wrote:
>
> On Do, 2014-04-17 at 17:58 +0200, [hidden email] wrote:
> > Hi,
> >
> > is there a way to use tcp source uri (tcp://...) with uridecodebin or playbin elements ?
>
> There are two TCP sources (tcpclientsrc and tcpserversrc), but both
> don't implement an URI handler.
>
> You could implement a custom subclass of GstBin that implements the
> GstURIHandler interface and implements the TCP protocol you want to use,
> but having a generic "TCP" URI handler does not make much sense IMHO.

I'll have to object here---TCP URI handling is something ffmpeg and its players have that I've been missing in GStreamer.

E.g. I often use mpv to test pulling a MPEGTS stream over TCP.

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nicolas Dufresne-4]

Le lundi 09 mai 2016 à 14:13 +0200, Jan Alexander Steffens a écrit :
> I'll have to object here---TCP URI handling is something ffmpeg and
> its players have that I've been missing in GStreamer.
> E.g. I often use mpv to test pulling a MPEGTS stream over TCP.

I think tcp:// is miss-leading, and only exist in FFMPEG to stay
backward compatible. If you want mpegts over tcp, you could use
tcp+mpegts://, this at least would be a fully specified scheme. Just
TCP is ambiguous. It endup giving you a non-live source (no timestamp
information), that cannot be seeked. As there is no packetization, it's
also hard to manage it has live. Solution are welcome, but it's not
that simple.

Nicolas
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Sebastian Dröge-3]

On Mo, 2016-05-09 at 02:24 -0700, amitchawla wrote:
> Hi Sebastian,
>
> "having a generic "TCP" URI handler does not make much sense IMHO"
>
> Could you please explain why it doesn't make sense?
>
> Actually I was looking at playbin to wait for a movie stream at a TCP
> port.... so tcpserversrc seemed to the answer. Do I have any other
> way to implement that ?

You already answer that partially yourself. Should it be tcpserversrc
or tcpclientsrc that is used with an tcp:// URI?

The other parts are answered by Nicolas' mail already, in general "TCP"
is not a well defined media streaming protocol. For some subset of
streams this can be made to work though.

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com


_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel