C++ GStreamer SDK as input/outpu

Sebastian Dröge sebastian at centricular.com
Thu Jun 26 00:04:55 PDT 2014

On Mi, 2014-06-25 at 08:43 -0700, MrDaniel wrote:
> So we have appsrc and appsink.
> Could you possibly elaborate?
> After some googling, i have found this example of capturing with appsink.
> http://webcache.googleusercontent.com/search?q=cache:http://stackoverflow.com/questions/10403588/adding-opencv-processing-to-gstreamer-application
> I am still confused, the documentation says that appsrc and appsink both
> have a push and pull mode.  Is there any way to clarify how to use these?

You can push buffers into appsrc whenever you want, or wait for the
need-data and enough-data signals to let it "pull". That's from an
application point of view though, and the "pull" is not really pull mode
in a GStreamer way. From a GStreamer point of view appsrc will handle
pull vs. push mode transparently and you don't have to worry about that.

For appsink, you can either just pull data all the time which then
blocks... or wait for the new-sample event to happen and only then pull.
But internally from a GStreamer point of view appsink is always in push

Sebastian Dröge, Centricular Ltd - http://www.centricular.com
Expertise, Straight from the Source
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140626/abc3f93b/attachment.sig>

More information about the gstreamer-devel mailing list