[FFmpeg-user] A query on using the OpenCL tonemap filter from derived OpenCL device contexts from VAAPI.
dmngaie at gmail.com
Tue Nov 6 15:06:54 EET 2018
I'll correct that and update the question, thanks.
On Tue, 6 Nov 2018 at 11:08, Paul B Mahol <onemda at gmail.com> wrote:
> On 11/6/18, Dennis Mungai <dmngaie at gmail.com> wrote:
> > Hello there,
> > From this patchwork:
> > It should be possible to utilize an OpenCL tonemap filter which does
> > HDR(HDR10/HLG) to SDR conversion with tone-mapping, as shown in the
> > below:
> > ffmpeg -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 INPUT -filter_hw_device ocl -filter_complex \
> > '[0:v]hwmap,tonemap_opencl=t=bt2020:tonemap=linear:format=p010[x1]; \
> > [x1]hwmap=derive_device=vaapi:reverse=1' -c:v hevc_vaapi -profile 2
> > However, doing this results in a failure, shown below:
> > Device creation failed: -38.
> > Failed to set value 'opencl=ocl at va' for option 'init_hw_device':
> > not implemented
> > Platform details:
> > I'm using the Intel Media driver built with the
> > cl_intel_va_api_media_sharing OpenCL extension enabled. The OpenCL
> > on the system is based on Neo:
> > fmpeg -hide_banner -v verbose -init_hw_device opencl
> > [AVHWDeviceContext @ 0x560d50e77140] 0.0: Intel(R) OpenCL HD Graphics /
> > Intel(R) Gen9 HD Graphics NEO
> > The Intel Media SDK is also installed, and can use both QSV and
> > VAAPI-based encoders in FFmpeg using the media-driver.
> > How can I fix that issue above?
> Issues posted with -hide_banner option are ignored.
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
More information about the ffmpeg-user