вс, 26 февр. 2023 г., 23:48 Andrea paz <gamberucci.andrea@gmail.com>:

One final consideration:
system ffmpeg has "--enable-opencl" active by default, while our
ffmpeg does not have it and cannot even activate it. Did we take this
option off?

I feared so, but my termux rebuild showed opencl as only available hw device for internal ffmpeg:

~/cinelerra/cinelerra-5.1 $ thirdparty/ffmpeg-5.1/ffmpeg -init_hw_device list

Supported hardware device types:

opencl

after I modified my build script.

~/cinelerra/cinelerra-5.1 $ git diff blds/termux.bld

diff --git a/cinelerra-5.1/blds/termux.bld b/cinelerra-5.1/blds/termux.bld

index afa14a74..7cbcdf2a 100755

--- a/cinelerra-5.1/blds/termux.bld

+++ b/cinelerra-5.1/blds/termux.bld

@@ -1,6 +1,6 @@

#!/bin/bash

# Produced, tested, and used by Andrew-R on an Android tablet

-export FFMPEG_EXTRA_CFG="--disable-debug --disable-doc --disable-ffprobe --enable-libdav1d"

-export EXTRA_LIBS="-ldav1d"

+export FFMPEG_EXTRA_CFG="--disable-debug --enable-opencl --disable-doc --disable-ffprobe --enable-libdav1d"

+export EXTRA_LIBS="-ldav1d -lOpenCL"

./configure --without-lv2 --without-vdpau --without-vaapi --without-ladspa-build \

--without-nv --with-single-user --with-clang --without-gl --disable-dav1d

So, for some reason your ffmpeg build as done by cingg does not pick up those opencl variables?

Thank you Andrew, you are doing a great job!