[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zeromq-dev
Subject:    Re: [zeromq-dev] Video streaming (?)
From:       Steven McCoy <steven.mccoy () miru ! hk>
Date:       2011-06-24 20:13:25
Message-ID: BANLkTikJDW1HNXGQfy+juBSaF4YV-W_j9g () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 24 June 2011 15:51, Gary Strangman <gary.strangman@gmail.com> wrote:

> Hi again,
>
> I have a(nother) use-case where video data (up to full 1080p) data will be
> acquired by one computer, and needs to be (1) distributed in more-or-less
> real time to one or more clients computers (perhaps using pub/sub?), as well
> as (2) being simultaneously archived in a database. I've read various things
> about how to handle streaming video using 0MQ, and they've ranged the gamut
> ... from 0MQ being a "stunningly poor choice":
> http://news.ycombinator.com/item?id=1660695
>

As it presumably is live data you are going to have a frame-by-frame stream
of data, and you have a choice how to encapsulate it on the wire.  First
choices are obviously RTSP over TCP or UDP depending on fan-out
requirements, and HTTP for easy streaming.

Looking for more exotic transports depends upon your requirements and
integration with metadata or other business logic.  For example you could
hook a video source up with GStreamer and a PGM sink/source*, or adding a
little more payload and working with FEC and congestion control end up with
something like PoolVideoSwitch:

http://www.ks.uni-freiburg.de/projekte/pvs/

* PGM GStreamer sink/source
http://openpgm.googlecode.com/files/gstpgm-2.0.4.tar.bz2

-- 
Steve-o

[Attachment #5 (text/html)]

<div class="gmail_quote">On 24 June 2011 15:51, Gary Strangman <span dir="ltr">&lt;<a \
href="mailto:gary.strangman@gmail.com">gary.strangman@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">

Hi again,<div><br></div><div>I have a(nother) use-case where video data (up to full \
1080p) data will be acquired by one computer, and needs to be (1) distributed in \
more-or-less real time to one or more clients computers (perhaps using pub/sub?), as \
well as (2) being simultaneously archived in a database. I&#39;ve read various things \
about how to handle streaming video using 0MQ, and they&#39;ve ranged the gamut ... \
from 0MQ being a &quot;stunningly poor choice&quot;:</div>


<div><a href="http://news.ycombinator.com/item?id=1660695" \
target="_blank">http://news.ycombinator.com/item?id=1660695</a></div></blockquote><div><br></div><div>As \
it presumably is live data you are going to have a frame-by-frame stream of data, and \
you have a choice how to encapsulate it on the wire.  First choices are obviously \
RTSP over TCP or UDP depending on fan-out requirements, and HTTP for easy \
streaming.</div>

<div><br></div><div>Looking for more exotic transports depends upon your requirements \
and integration with metadata or other business logic.  For example you could hook a \
video source up with GStreamer and a PGM sink/source*, or adding a little more \
payload and working with FEC and congestion control end up with something like \
PoolVideoSwitch:</div>

<div><br></div><div><a \
href="http://www.ks.uni-freiburg.de/projekte/pvs/">http://www.ks.uni-freiburg.de/projekte/pvs/</a></div><div><br></div><div>* \
PGM GStreamer sink/source</div><div><a \
href="http://openpgm.googlecode.com/files/gstpgm-2.0.4.tar.bz2">http://openpgm.googlecode.com/files/gstpgm-2.0.4.tar.bz2</a></div>


<div><br></div><div>-- </div><div>Steve-o</div></div>



_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev


[prev in list] [next in list] [prev in thread] [next in thread]