Custom Events and Flushing Pads.

Stirling Westrup swestrup at
Thu Jun 18 10:55:24 PDT 2015

On Mon, Jun 8, 2015 at 5:25 PM, Tim Müller <tim at> wrote:

> On Mon, 2015-06-08 at 16:27 -0400, Stirling Westrup wrote:
> > That's a shame. I would hope you would consider adding a
> > FLUSH_BYPASSING event bit that is set for FLUSH_START and FLUSH_STOP
> > and which could be used to create custom flush bypassing events.
> Maybe, it would be helpful to know more about your exact use case.

I have an application that has a dbus interface, and a dynamic pipeline
with a number of custom elements. At any time a user can send me a dbus
signal to change some global parameter of my video system (such as what
rotation angle to display video at).

My plan was to simply convert these dbus signals to events and have my
custom elements know which events were relevant to them, and to either make
immediate changes to how they were processing buffers, or (if the pipeline
wasn't currently active) to merely change their internal properties in
anticipation of the next start of play.

Because the pipeline is dynamic (and indeed, can be reconfigured via dbus),
I didn't want to have to keep and maintain a list of all of my custom
elements so as to know which to change properties on when global parameters
changed, but since I can't send events through a flushing pipeline, that is
exactly what I've had to do.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list