1,433
edits
GstInterpipe - Simple Examples: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
GstInterpipe has many features that take place on runtime, so it is no possible to fully test it and demonstrate its capabilities using a quick gst-launch-1.0 prototype pipeline. In this case it will be necessary to develop a quick C or C++ application that integrates the GStreamer framework, but fortunately there is simpler and quicker alternative: [[Gstd-1.0|GStreamer Daemon (Gstd-1.0)]]. The perfect complement for the GstInterpipe is the [[Gstd-1.0|GStreamer Daemon (Gstd-1.0)]]. It gives the possibility to create a set of different independent pipelines, on which you can independently change their state or their element properties. | GstInterpipe has many features that take place on runtime, so it is no possible to fully test it and demonstrate its capabilities using a quick gst-launch-1.0 prototype pipeline. In this case it will be necessary to develop a quick C or C++ application that integrates the GStreamer framework, but fortunately there is simpler and quicker alternative: [[Gstd-1.0|GStreamer Daemon (Gstd-1.0)]]. The perfect complement for the GstInterpipe is the [[Gstd-1.0|GStreamer Daemon (Gstd-1.0)]]. It gives the possibility to create a set of different independent pipelines, on which you can independently change their state or their element properties. | ||
Based on the above explanation, the following samples were developed using the [[Gstd-1.0|GStreamer Daemon (Gstd-1.0)]]. | Based on the above explanation, the following samples were developed using the [[Gstd-1.0|GStreamer Daemon (Gstd-1.0)]]. To build and install gstd-1.0 you can follow this guide: [[Gstd-1.0 - Building GStreamer Daemon | Building GStreamer Daemon]]. | ||
__TOC__ | __TOC__ | ||