On 03/06/15 11:29 AM, Luca Barbato wrote: > On 31/05/15 17:01, Luca Barbato wrote: >> On 27/05/15 22:25, James Almer wrote: >>> Yes, that plus a considerable amount of ifdeffery in the code. It >>> will be ugly, but i also think it's worth keeping compatibility with >>> at least 1.3.0 >>> >> >> 1.3.0 explodes on 422p that at least in theory should support. (I'm >> testing all the possible encodings right now). >> > > 1.3.0 seems that had been released when not ready, do we really want to > support it? > > lu
It works with 420p content (vp8 and vp9). Support for 422p, 440p, 444p and high bit-depth was officially added with 1.4.0. 1.3.0 should reject the latter stuff, but for some reason it doesn't and it encodes garbage. With some ifdeffery and static init magic both the decoder and encoder can be limited to 420p for vpx 1.3.0. But then again, I guess vpx 1.3.0 is old enough by now that support for it can be safely dropped. _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
