2,225
edits
GstInterpipe: Difference between revisions
m
no edit summary
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
= Introduction = | = Introduction = | ||
== Overview == | |||
GstInterpipe is a Gstreamer plug-in that allows communication between two independent pipelines. The plug-in consists of two elements: | GstInterpipe is a Gstreamer plug-in that allows communication between two independent pipelines. The plug-in consists of two elements: | ||
* interpipesink | * interpipesink | ||
| Line 12: | Line 13: | ||
Various sink pipelines may listen to it by: | Various sink pipelines may listen to it by: | ||
<pre style="background:#d6e4f1"> | <pre style="background:#d6e4f1"> | ||
interpipesrc | interpipesrc listen-to=video_src ! xvimagesink | ||
interpipesrc | interpipesrc listen-to-video_src num-buffers=1 ! jpegenc ! filesink location=snapshot.jpeg | ||
</pre> | </pre> | ||
The state of each pipeline is independent, each one can manage events by their own and | The state of each pipeline is independent, each one can manage events by their own and can be attached or detached at any moment. | ||
The concept behind the Interpipes Project is to simplify the construction of GStreamer applications, which often has the complexity of requiring dynamic pipelines. It transforms the construction process from low level pad probe manipulation to the higher level setting an element's parameter value. Application developers don't get mired down in stalled pipelines because one branch of a complex pipeline changed state. | The concept behind the Interpipes Project is to simplify the construction of GStreamer applications, which often has the complexity of requiring dynamic pipelines. It transforms the construction process from low level pad probe manipulation to the higher level setting an element's parameter value. Application developers don't get mired down in stalled pipelines because one branch of a complex pipeline changed state. | ||
| Line 32: | Line 31: | ||
This way the stream flow in a complex pipeline is reduced to simply set the correct listeners in the interpipe elements taking away the complexity of re-configuring pads or some other complex and error-prone logic. | This way the stream flow in a complex pipeline is reduced to simply set the correct listeners in the interpipe elements taking away the complexity of re-configuring pads or some other complex and error-prone logic. | ||
== Features and Limitations == | |||
The GstInterpipe project exposes the following characteristics: | |||
* Inspired by intervideosrc/intervideosink | |||
* Uses appsrc and appsink as a base | |||
* Generic data handling | |||
* Multiple dynamic interpipesink - interpipesrc connections | |||
* Replace tee and selector elements allowing dynamic pipeline flow control with GStreamer Daemon | |||
Features: | |||
The | The current release exposes the following limitations and known bugs: | ||
;Specialized clocks | |||
:At the time being, pipelines negotiate their clock independently. If a pipeline uses a special clock (i.e.: GstAudioSinkClock), the associated pipes (being independent) may negotiate different clocks, typically GstSystemClock. This could be a big problem if, for example, synchronization between streams is required. It is currently responsibility of the application to set the special clock in all the involved pipes by calling [https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/GstPipeline.html#gst-pipeline-set-clock gst_pipeline_set_clock]. | |||
= Getting the Software = | = Getting the Software = | ||