Influencing playbin2/decodebin2 auto-plugging

Tvrtko Ursulin tvrtko.ursulin at onelan.co.uk
Fri Aug 3 01:55:26 PDT 2012


On Thursday 02 August 2012 21:28:31 Stefan Sauer wrote:
> On 08/02/2012 07:36 PM, Tim-Philipp Müller wrote:
> > On Thu, 2012-08-02 at 19:03 +0200, Stefan Sauer wrote:
> >> On 08/02/2012 04:39 PM, Tvrtko Ursulin wrote:
> >>> Is there a way to dynamically influence auto-plugging in
> >>> playbin2/decodebin2, for example by upranking or deranking elements?
> >> 
> >> No. https://bugzilla.gnome.org/show_bug.cgi?id=649542
> > 
> > This is just convenience API, of course you can do such things
> > dynamically.
> > 
> > You can manually set element ranks at runtime in your application by
> > looking up the GstElementFactory/GstPluginFeature in the registry after
> > gst_init() and setting the plugin rank via
> > gst_plugin_feature_set_rank().
> > 
> > Then there are the "autoplug-{factories,sort,select}" signals on
> > decodebin2/uridecodebin, which you can use to tweak the autoplugging.
> > 
> > You can use those in playbin2 as well, but you need to "somehow" find
> > the uridecodebin element inside playbin2.
> > 
> > As for the vaapi stuff, I thought this should just work automagically
> > these days (with latest releases) if the video-sink set supports it
> > (like vaapi*sink or cluttersink). Perhaps it's only in git, don't
> > remember. I'm sure someone will correct me if needed :)
> 
> The question sounded like he want to adjust how much of the work is done
> on cpu/gpu.

Exactly, play n videos on the GPU, and when resources run out, play some more 
videos on the CPU.

Tvrtko


More information about the gstreamer-devel mailing list