On Fri, Oct 21, 2016 at 4:55 AM, Ronald S. Bultje <rsbul...@gmail.com> wrote: > Hi, > > On Thu, Oct 20, 2016 at 11:14 PM, James Zern <jzern-at-google....@ffmpeg.org >> wrote: > >> On Thu, Oct 20, 2016 at 8:31 AM, Kagami Hiiragi <kag...@genshiken.org> >> wrote: >> > vp9_cx_iface actually allows values in range [0..2]. >> > This fixes ticket #5894. >> > >> > Signed-off-by: Kagami Hiiragi <kag...@genshiken.org> >> > --- >> > libavcodec/libvpxenc.c | 7 ++++++- >> > 1 file changed, 6 insertions(+), 1 deletion(-) >> > >> >> This is all right in the sense that the library exposes the option. In >> practice the feature was never fully developed and will cause failures >> in certain hardware decoders. > > > Maybe these hardware should be blacklisted. >
I don't necessarily disagree, but I think issues with multiple altrefs and/or the frequency of individual ones is somewhat pervasive. So blacklisting might mean vp9 wasn't an option on some platforms. This is part of the reason behind all this [1]. [1] http://www.webmproject.org/vp9/levels/ _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
