[FFmpeg-devel] [PATCH 00/15] OpenCL infrastructure, filters
hydra3333 at gmail.com
hydra3333 at gmail.com
Sun Nov 26 18:14:38 EET 2017
Most systems have a "clinfo" program which will list all the queryable
properties of the available devices.
>From docs:
-init_hw_device type[=name][:device[,key=value...]]
Initialise a new hardware device of type type called name, using the
given device parameters. If no name is specified it will receive a default
name of the form "type%d".
-filter_hw_device name
Pass the hardware device called name to all filters in any filter graph.
So, either give it a name explicitly or deduce what the name will be:
-init_hw_device opencl=arbitrary_name:1.0 -filter_hw_device arbitrary_name
or
-init_hw_device opencl:1.0 -filter_hw_device opencl0
(There is some thought of adding an option -opencl_device working
like -vaapi_device to avoid the two steps for simple upload. The most
useful cases all use device derivation/mapping to keep things on the GPU
side, though, so I'm not entirely sure whether it's actually wanted.)
- Mark
----------------------------------------------
OK and Thank you, Mark.
One last question if I may,
> Most systems have a "clinfo" program which will list all the queryable
> properties of the available devices.
In both of these cases
-init_hw_device opencl=arbitrary_name:1.0
-init_hw_device opencl:1.0
the device is seen to be "1.0" ... how does one determine that device "id"
in Windows 10 in order to use it ?
(I have a another PC with intel graphics plus a 1050Ti and need to specify
the 1050Ti)
I tried to use a clinfo command in DOS under Win10 ... but no go.
Display Adaptor properties didn't show anything obvious to an end-user.
GPU Caps Viewer didn't show anything useful.
ffmpeg -init_hw_device list showed
Supported hardware device types:
cuda
dxva2
qsv
d3d11va
opencl
Thank you.
More information about the ffmpeg-devel
mailing list