Package Details: vmaf-git 3.0.0rc.r1.g97e50eae-1

Git Clone URL: https://aur.archlinux.org/vmaf-git.git (read-only, click to copy)
Package Base: vmaf-git
Description: Perceptual video quality assessment algorithm based on multi-method fusion (git version)
Upstream URL: https://github.com/Netflix/vmaf/
Keywords: libvmaf netflix
Licenses: BSD
Conflicts: libvmaf-git, vmaf
Provides: libvmaf-git, vmaf
Replaces: libvmaf-git
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 7
Popularity: 0.000000
First Submitted: 2018-02-12 16:51 (UTC)
Last Updated: 2023-11-28 20:14 (UTC)

Required by (23)

Sources (1)

Latest Comments

1 2 3 Next › Last »

dbermond commented on 2023-11-28 20:15 (UTC)

@krutoileshii Package updated to match latest upstream changes.

krutoileshii commented on 2023-11-26 19:30 (UTC)

getting: install: cannot stat 'vmaf/libvmaf/build/tools/vmafossexec': No such file or directory

xiota commented on 2023-09-20 13:26 (UTC) (edited on 2023-11-27 02:34 (UTC) by xiota)

Please remove replaces directive, in accordance with AUR submission guidelines.

dbermond commented on 2022-02-18 00:41 (UTC)

@prg The package is currently building fine, and the tests are passing. vim is required at build time. No changes needed.

prg commented on 2022-02-17 19:44 (UTC)

vim should not be listed as a makedepend - its not required to build

in addition, the tests currently fail (with or without vim installed) so the check() function of this PKGBUILD should be commented out

oxalin commented on 2021-12-26 01:29 (UTC)

@kcave, you will need to recompile any app that depends on vmaf: devs now number the library (it came probable with an API change) and see if they compile correctly.

kcave commented on 2021-11-21 13:31 (UTC)

After I installed this in place of the out of date community vmaf package, at least one application (geeqie) stopped working because it couldn't find libvmaf.so.0.0

Presumably this is due to the resultant libvmaf being called libvmaf-git, judging by the PKGBLD

Due to the nature of this package, it cannot co-exist with the out of date community vmaf package (i.e. I have to uninstall community vmaf in order to install this one).

I'm just wondering what the solution to this may be. Unless I've got the wrong idea of course and this more up to date version of vmaf isn't a "drop-in" replacement for the out of date commmunity vmaf?

Regards.

misharash commented on 2021-11-14 18:41 (UTC)

This package does not satisfy the fresh requirement vmaf>=2.3.0 of lib32-vmaf as it is, while its version is actually higher. To fix this, one needs to specify provides:("vmaf=$pkgver" in PKGBUILD.

dbermond commented on 2021-07-29 22:54 (UTC)

@nathanielcwm The arch-meson script enables lto by default and the package is building fine for me.

nathanielcwm commented on 2021-07-29 12:02 (UTC)

Looks like it doesn't build with lto enabled btw?