On 13/03/17 17:02, Luca Barbato wrote: > On 13/03/2017 17:59, Mark Thompson wrote: >> On 13/03/17 16:50, Mark Thompson wrote: >>> --- + version bump > >> Maybe the default value would be better as a detectable one like -1 >> or INT_MIN? Then the filters which currently have a higher default >> could used their original values in that case, and users wouldn't >> need to add this option in some cases which currently work. > > How it would combine with the decoder setting?
It wants to do the same thing. I haven't touched the qsv decoder here because it needs the hw_device_ctx support to be meaningful (9/25 in the more-device-stuff series), but now that I think about it it will have the same issue. VAAPI has less compatibility interest because it doesn't currently overallocate frames, though you can still run into problems when decoding a stream with many reference frames and then encoding the resulting frames directly with a lot of delay. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
