<div dir="ltr">The easiest and quickest way in GStreamer is to setup an RTSP server. It can use any video stream, but only one way. It can easily support multiple clients receiving the same (or different) video streams from the server. If you want something more, you *COULD* have both systems running as an RTSP server and both running as a client. However, the best way would be to use some other outside signaling protocol such as SIP. SIP does not require a server or a registrar and you can make pt-pt calls with SIP. You exchange SDPs in the invite/response, which can contain the sprops-parameters that contain the info you want. But SIP is entirely outside of GStreamer. There are several open source SIP implementations. If you do this without a SIP server that everyone registers with, you will have to provide some way for endpoints to know the destination (IP address) of the target. There are other out of band protocols also, such as H323. This will require a moderate amount of work.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 10, 2014 at 6:35 PM, Michael Tyson <span dir="ltr"><<a href="mailto:michael@tyson.id.au" target="_blank">michael@tyson.id.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">That’s great news! Thanks, Chuck.<br><div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<br></div>It’s pretty much one-sender-one-receiver, although I’d like to keep the option of one-sender-multiple-receivers open. It’s entirely local-network, with prearranged multicast address, port and protocol. <br><br>
</div><div>I’d imagine at launch priming the rx pipeline with the frame size/rate it expects to receive from the other end, which will hopefully facilitate showing some kind of display until the actual video arrives. Just to consider a simple case, where these are hard-coded, are you able to point me at the appropriate API bits to accomplish that?</div>
<div><br></div><div>Cheers!</div>
<br><div><div>On 11 Mar 2014, at 12:48 am, Chuck Crisler <<a href="mailto:ccrisler@mutualink.net" target="_blank">ccrisler@mutualink.net</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">Sure. You use out of band signaling, something like SIP or RTSP. It really depends on your application - what you are trying to do, single system to many? One to one? Endpoints registered to a server? How do you know the addresses and ports and protocols? The sender could include the sprop_parameters in that communication.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 10, 2014 at 5:49 AM, Michael Tyson <span dir="ltr"><<a href="mailto:michael@tyson.id.au" target="_blank">michael@tyson.id.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hello!<div><br></div><div>I’m putting together a realtime video monitoring application with a cairo overlay, in C.</div>
<div><br></div><div>Until the first RTP video packets arrive, there’s no visual - the pipeline’s got no video format information, so it’s waiting to receive the first frames.</div><div><br></div><div>I’d ideally like to display a blank screen, but primed with the expected screen resolution, ideally with something like a “waiting for video” caption. Is something like this at all possible with GStreamer?</div>
<div><br></div><div>Cheers,</div><div>Michael</div><div><br><div><div><div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div style="text-align:-webkit-auto;text-indent:0px;word-wrap:break-word"><div style="text-align:-webkit-auto;text-indent:0px;word-wrap:break-word"><br></div></div></div><br><br>
</div>
<br></div></div></div><br>_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>gstreamer-devel mailing list<br><a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a><br><a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
</blockquote></div><br></div><br>_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
<br></blockquote></div><br></div>