[FFmpeg-devel] [OPENCL] a idea to get a better performance of the OPENCL video filter

Timothy Gu timothygu99 at gmail.com
Wed Jun 26 18:16:11 CEST 2013

On Jun 26, 2013 1:52 AM, "weixuan wang" <batmanwwx at gmail.com> wrote:
> Would it be an alternative to only have one
> opencl filter that supports unsharp, deshake
> and all future features?
> yes, it will be an alternative to the all of the filters which supports

I guess you didn't understand Carl's question. He was asking whether having
only ONE "opencl" filter for everything is reasonable. Something like this:
-vf 'opencl=unsharp:otheropt'.

> Or will all filters really be implemented very
> similar to the existing filters (with identical
> options) so that it makes perfectly sense to
> have them in one source file together with the
> existing filters and as the same filter for
> the users?
> yes, it will be  implemented very similar to the existing filters, but
> the filters which supports the OPENCL need this function to improve their
> performance.

Same here. Carl probably means having separated filters.


More information about the ffmpeg-devel mailing list