Hi,
> -enabled libvmaf && require_pkg_config libvmaf "libvmaf >= 1.5.2"
> libvmaf.h compute_vmaf
> +enabled libvmaf && require_pkg_config libvmaf "libvmaf >= 2.0.0"
> libvmaf.h vmaf_init
General question: Is it acceptable to drop support for libvmaf 1.x? I
saw that Fedora 33
Thanks, moving this to the users mailing list. However, I did actually
manage to narrow this down. It seems that the ffmpeg configure does not
follow CC and CXX environment variables and seems to insist on GCC.
On Wed, Jun 30, 2021 at 11:49 AM Nicolas George wrote:
> Šimon Tóth (12021-06-30):
>
Šimon Tóth (12021-06-30):
> clang: error: no such file or directory: 'DEBUG_PREFIX_MAP_PWD=.'
>
> Any pointers would be greatly appreciated.
The bug seems in the environment you give to the configure script:
ASFLAGS='... -DDEBUG DEBUG_PREFIX_MAP_PWD=. -isysroot...'
For further help, please ask
On Sat, 2021-05-15 at 17:53 +0200, Bas Nieuwenhuizen wrote:
> This way we can pass explicit modifiers in. Sometimes the
> modifier matters for the number of memory planes that
> libva accepts, in particular when dealing with
> driver-compressed textures. Furthermore the driver might
> not actually
On 16.04.2021 10:58, Tobias Rapp wrote:
Adds schema validation for ffprobe XML output so that updating the
ffprobe.xsd file upon changes to ffprobe is not forgotten. This was
suggested by Marton Balint in:
http://ffmpeg.org/pipermail/ffmpeg-devel/2021-March/278428.html
The schema FATE test is on
