http://base-art.net/Articles/107/ <p>Long time no blog, eh? Anyway I was today hooking up <a class="reference" href="http://telepathy.freedesktop.org">Telepathy</a> Stream Tubes with <a class="reference" href="http://gstreamer.org">GStreamer</a> so that I could stream video over local-xmpp, go figure why... :)</p> <p>Everything was fine:</p> <ul> <li><p class="first">on one side, offer a stream tube in a multi-user room and setup a pipeline like this one:</p> <pre class="literal-block"> videotestsrc ! gdppay ! multifdsink </pre> </li> <li><p class="first">on client side, join the room and accept the tube, hooked into the following pipeline with a socket:</p> <pre class="literal-block"> fdsrc ! gdpdepay ! xvimagesink </pre> </li> <li><p class="first">when server is notified of new client, add its socket fd in multifdsink and start playback</p> </li> </ul> <p>But it wasn't working, multifdsink was removing the fd by itself from the list and client wasn't receiving data. I spent some time this afternoon trying to figure out why and thought I might share the solution, if it can serve to anyone using multifdsink in Python. Because I wasn't keeping references of the client socket instances in my code, they were garbage-collected by Python, so the fd was becoming invalid, hence the rejection by multifdsink.</p> <p>Keeping a list of the socket instances and cleaning it up when the sink emits the client-removed signal does the trick and I got my video streaming over local-xmpp working. Those Tubes are so much fun, thanks Collabora &amp; Telepathy folks for this nice stuff!</p> en The contents of this blog are available for non-commercial use only. Alinea http://pythonfr.org/alinea/ http://base-art.net/Comments/275/ http://base-art.net/Comments/275/ phil 2009-05-24T20:40:03Z http://base-art.net/Comments/274/ http://base-art.net/Comments/274/ wiflye81 2009-05-24T20:05:03Z