change in OpenCL device numbering behaviour
Posted: Wed Dec 05, 2018 5:25 pm
It seems there has been a recent change in OpenCL device numbering behaviour in Windows and/or nvidia driver and/or ffmpeg.
Until recently, the ffmpeg command below used to consistently report NVIDIA CUDA device as number 1.0 and the other as 0.0 (on multiple computers).
Just recently, I noticed that the device numbers (on multiple computers) had swapped around and remained consistently that way across reboots.
I am not sure if that was caused by recent very large Win10x64 update, or a newer build of ffmpeg-with-opencl. Hence I am unsure if the change may affect your software or not.
The change caused me some grief in some hard-coded .bat files which assumed consistent device numbering over time.
Cheers.
Until recently, the ffmpeg command below used to consistently report NVIDIA CUDA device as number 1.0 and the other as 0.0 (on multiple computers).
Just recently, I noticed that the device numbers (on multiple computers) had swapped around and remained consistently that way across reboots.
I am not sure if that was caused by recent very large Win10x64 update, or a newer build of ffmpeg-with-opencl. Hence I am unsure if the change may affect your software or not.
Code: Select all
"ffmpeg.exe" -hide_banner -v verbose -init_hw_device opencl
[AVHWDeviceContext @ 0000025f0ef2a1c0] 0.0: NVIDIA CUDA / GeForce GTX 1050 Ti
[AVHWDeviceContext @ 0000025f0ef2a1c0] 1.0: Intel(R) OpenCL / Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
[AVHWDeviceContext @ 0000025f0ef2a1c0] More than one matching device found.
Device creation failed: -19.
Failed to set value 'opencl' for option 'init_hw_device': No such device
Error parsing global options: No such device
Cheers.