[FFmpeg-devel] [PATCH 00/15] OpenCL infrastructure, filters

Mark Thompson sw at jkqxz.net
Wed Nov 15 16:34:09 EET 2017

On 14/11/17 22:30, Carl Eugen Hoyos wrote:
> 2017-11-14 20:47 GMT+01:00 Mark Thompson <sw at jkqxz.net>:
>> Silly example using everything (for i965 VAAPI + Beignet):
>> ./ffmpeg_g -y -init_hw_device vaapi=va:/dev/dri/renderD128
>> -init_hw_device opencl=ocl at va -hwaccel vaapi
>> -hwaccel_device va -hwaccel_output_format vaapi -i in.mp4
>> -f image2 -r 1 -i overlays/%d.png -an -filter_hw_device ocl
>> -filter_complex '[1:v]format=yuva420p,hwupload[x2];
>> [0:v]scale_vaapi=1280:720:yuv420p,hwmap[x1];
>> [x1][x2]overlay_opencl=0:0,
>> program_opencl=test.cl
> Is this the equivalent of the vhook functionality?

I suppose it has some similarities.  Is that a problem?

The point of it is to allow the user to run simple pixel shaders on the GPU side without having to integrate them into ffmpeg.  Compare, for example, the user shaders feature in mpv.


- Mark

More information about the ffmpeg-devel mailing list