Search Criteria
Package Details: lib32-vmaf 3.0.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/lib32-vmaf.git (read-only, click to copy) |
|---|---|
| Package Base: | lib32-vmaf |
| Description: | Perceptual video quality assessment algorithm based on multi-method fusion (32 bit) |
| Upstream URL: | https://github.com/Netflix/vmaf/ |
| Licenses: | BSD |
| Submitter: | oxalin |
| Maintainer: | oxalin |
| Last Packager: | oxalin |
| Votes: | 3 |
| Popularity: | 0.000000 |
| First Submitted: | 2020-05-12 13:00 (UTC) |
| Last Updated: | 2024-02-26 00:06 (UTC) |
Dependencies (6)
- lib32-gcc-libs (lib32-gccrs-libs-gitAUR, lib32-gcc-libs-gitAUR)
- lib32-libvmafAUR
- vmaf (vmaf-gitAUR, libvmaf-compatAUR)
- meson (meson-gitAUR, meson-rustAUR) (make)
- nasm (nasm-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR) (make)
Latest Comments
1 2 Next › Last »
kcave commented on 2021-11-21 23:14 (UTC)
@oxalin Looking at the provides for vmaf-git, it looks like it provides "vmaf" and "libvmaf-git" instead of "libvmaf".
I've dropped a comment into that AUR. Because IMO it should provide the expected libvmaf.so.0 instead of libvmaf-git.so.0, seeing as installing that AUR requires uninstalling the out of date vmaf package.
Unless I've totally misunderstood of course, but at the moment I have it in my head that if an AUR requires the de-installation of a corresponding system/community package, then it should provide the expected libraries it's replacing.
Then again, I'm still getting used to How Arch Works, after decades of getting tired of Debian ;)
oxalin commented on 2021-11-21 18:16 (UTC)
@kcave Could geeqie and other packages need to be rebuilt along vmaf 2.x series? Some links may be broken otherwise. This could be easily verified / tested though: download one of the PKGBUILD of a broken package and build it.
Just to test it, I may have a go at it later or in the next few days.
kcave commented on 2021-11-21 13:21 (UTC)
@oxalin Thanks for the prompt response.
After I installed vmaf-git a number of problems occurred - mainly that other applications like geeqie which looks for libvmaf couldn't find it anymore, so it looks like vmaf-git isn't a "drop-in" replacement for the community vmaf package, even though it claims to provide vmaf and libvmaf and doesn't co-exist with the community vmaf package. Blast.
And therefore trying to get lib32-vmaf to use vmaf-git is, right now, a non starter.
Regards.
oxalin commented on 2021-11-20 20:10 (UTC)
@kcave Yes, this would work. There is a little fix that needs to be applied to PKBUILD on vmaf-git's side, but other than that, nothing should prevent it from working.
kcave commented on 2021-11-20 15:33 (UTC) (edited on 2021-11-20 15:37 (UTC) by kcave)
@oxalin
Would it be possible to depend on and use the AUR vmaf-git package instead? After all, lib32-vmaf is an AUR package in itself.
Regards.
EDIT: I just realised the AUR vmaf-git is out of date-ish as well, at 2.0.0
FURTHER EDIT: No scratch that, it does indeed provide vmaf 2.3.0.blah currently.
oxalin commented on 2021-11-19 06:29 (UTC)
I had hoped that it would be easier and quicker to have an updated vmaf package, but it seems that, as many other packages, the last year has been hard on maintenance and some packages that should have been updated a long time ago are still lagging behind (as for vmaf).
There is no reason for not updating vmaf, while newer versions offer better performances and bug fixes. Opening a bug for problems related to maintenance is not considered to be the official way of doing it, so I'll need to go through forums and mailing lists. And I don't have the time for this quest right now (because it is truly a quest).
So I'll just revert the changes introduced by last commit and keep the updated version on hold.
DDoSolitary commented on 2021-11-14 10:54 (UTC)
The update makes the package virtually impossible to install
oxalin commented on 2021-11-14 03:10 (UTC)
The native package has been flagged as outdated for almost a year. If this causes problem, please mention it to the vmaf's maintainer so that the appropriate solution be applied.
MarsSeed commented on 2021-11-14 02:21 (UTC)
What's the use of updating this to the new version when not even Arch has updated the vmaf package that this one depends on?
DDoSolitary commented on 2020-11-16 07:44 (UTC) (edited on 2020-11-16 07:45 (UTC) by DDoSolitary)
The vcs_version.h error has been fixed in v1.5.3: https://github.com/Netflix/vmaf/issues/614
1 2 Next › Last »