On 27/12/2016 19:31, Anton Khirnov wrote:
> +     * When hardware acceleration with opaque output frames is used, the 
> actual
> +     * value of this option is disregarded and libavcodec behaves as if it 
> was
> +     * set to 0.

there should be a @warning markup around this.

The rest looks fine.
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to