You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've built Intel's VSR from the reisr4nas branch of ffmpeg cartwheel, and can likewise confirm that it works as expected; at least in GPU modes where OpenCL is available.
However, the same cannot be said of the out-of-the-box ASM modes with software-based encoding via libx264 and libx265, as documented on the wiki.
These trivial examples simply fail/exit with no output(s) on the console:
Now, if an OpenCL hardware context is provided as with the trivial example below for libx264, and asm=opencl is set, the filter runs/executes as expected:
Hi @Brainiarc7 if you want to use Opencl acceleration and encode with software -based libx264 or libx265, can use the following command line: ffmpeg -i "bbb.mp4" -vf "raisr=filterfolder=/filters_2x/filters_highres:asm=opencl" -pix_fmt yuv420p -c:v libx264/libx265 encoder_parameters_xxx -f mp4 ./output.mp4
If using lix264 can work but x265 cannot work with the same or similar codec parameters, you can first check if it can do transcode only(mean removing raisr filter) with libx265. Please check libx265 environment if the transcoding only with libx265 can't work.
Please check OpenCL environment install opencl if the transcoding only with libx265 work well.
With (1), yes, libx265 works as expected.
And with (2), OpenCL is readily available for both Intel and NVIDIA in the environment, verified with clinfo.
Hello there,
I've built Intel's VSR from the reisr4nas branch of ffmpeg cartwheel, and can likewise confirm that it works as expected; at least in GPU modes where OpenCL is available.
However, the same cannot be said of the out-of-the-box ASM modes with software-based encoding via
libx264
andlibx265
, as documented on the wiki.These trivial examples simply fail/exit with no output(s) on the console:
With `libx264:
With `libx265:
Now, if an OpenCL hardware context is provided as with the trivial example below for
libx264
, andasm=opencl
is set, the filter runs/executes as expected:However, attempting the same with
libx265
fails with the error:Regardless of the OpenCL device type/context created.
In brief: The filter is virtually unusable with the software-based
libx264
andlibx265
encoders, as-is, out of the box.The text was updated successfully, but these errors were encountered: