On 03/06/15 19:39, James Almer wrote: > 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.
Some of it is available already in 1.3.0, I guess I can restrict by version instead of restricting by features exposed. lu _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
