RSB GStreamer Integration: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732014-09-03T16:24:00ZOpen Source Collaboration Platform
Redmine Tasks #1981 (In Progress): Port to GStreamer 1.xhttps://code.cor-lab.de/issues/19812014-09-03T16:24:00ZC. Leichsenringcmertes@cit-ec.uni-bielefeld.de
<p>I created a new branch <code>gstreamer-1.0</code> where the port from gstreamer 0.10 to gstreamer 1.x can take place.</p>
<p>There are porting guidelines at <a class="external" href="http://cgit.freedesktop.org/gstreamer/gstreamer/tree/docs/random/porting-to-1.0.txt">http://cgit.freedesktop.org/gstreamer/gstreamer/tree/docs/random/porting-to-1.0.txt</a></p>
<p>I'm closing the ticket I had previously created at <a class="external" href="https://projects.cit-ec.uni-bielefeld.de/issues/3861">https://projects.cit-ec.uni-bielefeld.de/issues/3861</a></p> Tasks #922 (New): Create a manualhttps://code.cor-lab.de/issues/9222012-03-02T20:06:32ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.deTasks #507 (New): Expose RSB configuration options as GObject properties?https://code.cor-lab.de/issues/5072011-08-15T22:43:04ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>Some mechanism to configure RSB transports (especially Spread) using gstreamer machinery will probably be required.</p> Tasks #501 (New): Think about current lifecyclehttps://code.cor-lab.de/issues/5012011-08-13T04:46:07ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
Currently, the following lifecycle is used:
<ul>
<li><code>NULL -> READY </code>: listener creation</li>
<li><code>READY -> PAUSE </code>: handler registration, event queuing</li>
<li><code>READY -> NULL </code>: listener destruction</li>
</ul>