[Bug 759192] start gstreamer-vaapi "upstream-ization"

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Tue Feb 2 07:38:08 UTC 2016


https://bugzilla.gnome.org/show_bug.cgi?id=759192

--- Comment #26 from sreerenj <bsreerenj at gmail.com> ---
(In reply to Víctor Manuel Jáquez Leal from comment #21)

> 
> Yeah, just realized that is broken with gst1.6, because there's no vp9
> parser. I just need to bring back the vp9 parser check in config
> 
> > > In the gtk-doc generation I found an issue: because the encoders name have
> > > the pattern vaapiencode_{codec} the documentation of the vaapi plugin can
> > > link those pages because it assumes that the _ is changed to -
> > > 
> > > Anyway, it is a minor issue which we could track later. Perhaps we should
> > > rename the encoders to follow the common pattern in gstreamer.
> > 
> > I think the common pattern would be something like vaapih264dec /
> > vaapih264enc or vah264dec / vah264enc or such?
> 
> I'd vote for vaapi{codec}enc

We had a plan to do  the splitting for decoders like the encoders..
(Unlike encoders, we have a common vaapidecode for whole the codecs instead of
vaapih264dec, vaapivp9dec etc)
https://bugzilla.gnome.org/show_bug.cgi?id=734093

Renaming of elements will create bit of confusion, but if we are planning for a
name change, then this is the right time for sure :)
vaapi{codec}dec/vaapi{codec}enc is fine for me...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list