Package Details: ffmpeg-git 4.4.r101737.g896395bbcf-1

Git Clone URL: (read-only, click to copy)
Package Base: ffmpeg-git
Description: Complete solution to record, convert and stream audio and video (git version)
Upstream URL:
Keywords: audio codec convert encoder ffmpeg media vaapi video
Licenses: GPL3
Conflicts: ffmpeg
Provides: ffmpeg,,,,,,,,
Submitter: DrZaius
Maintainer: dbermond
Last Packager: dbermond
Votes: 66
Popularity: 0.60
First Submitted: 2011-01-17 22:00
Last Updated: 2021-03-26 19:27

Dependencies (64)

Required by (1000)

Sources (2)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

dbermond commented on 2021-05-26 16:46

@rien333 This is normal and expected. ffmpeg usually switches API and changes the soname versions at every x.0 and x.5 release. The current stable release is 4.4, and the git master branch now has the code for an upcoming 4.5 version, which in turn has increased the soname version. There is no action to be taken by this package or by any other package that depends on ffmpeg. You are for your own when using the git master branch (or when using any other AUR package). You, as the user, must choose either to use the stable ffmpeg version and continue to use software that are compiled for it, or use the latest git master branch with a soname bump and break everything that depends on ffmpeg. When using the git master branch you could try to recompile every package that links against ffmpeg, but this would require a lot of work, and not all packages would compile against it, because, as I already said, the code on git master usually has an API switch and it takes time for every other software to support it. For more details you can see my posts from 2017-Nov-01 and 2018-Fev-09 on package ffmpeg-full-git when this happened for the last time during the switch to the ffmpeg 4.0 release.

rien333 commented on 2021-05-26 12:56

I haven't been able to use this package for weeks now, because multiple packages (chromaprint, dolphin, vapoursynth) depend on libavcodec, libavutil, etc versions older than ffmpeg-git provides. Is this actually true in the first place? Can anything be done, and who needs to take action (e.g. this package or the other packages)?

aviallon commented on 2020-06-14 19:46

@dbermond I understand your point of view, but ffmpeg-full-git just adds way too much dependencies, and builds a ton of things for specific hardware... whereas rav1e is an infinitely useful feature of the master ffmpeg branch... I don't even want to try encoding to AV1 without rav1e...

EDIT: I made ffmpeg-rav1e-git, with rav1e pre-enabled.

dbermond commented on 2020-06-14 14:54

@zanny rav1e is still not used by repository ffmpeg. Since this package is the VCS (-git) variant of repository ffmpeg, it also does not have rav1e support for now. When repository ffmpeg adds it, I'll add it here too.

If you want rav1e support on ffmpeg git master you can use ffmpeg-full-git.

zanny commented on 2020-06-14 05:08

Could also add rav1e (rav1e / --enable-librav1e) now. Built it myself and it works fine.

dbermond commented on 2020-02-29 17:56

@toggleton dav1d was missing. Thanks for pointing this. Package updated with the addition of dav1d.

toggleton commented on 2020-02-23 12:00

Can you add depends=( 'dav1d' --enable-libdav1d \ dav1d is a lot faster in decoding than libaom(still needed for av1 encoding) and is even the default decoder in ffmpeg

digitalone commented on 2020-01-13 18:12

Cannot install and build with yay after x264 upstream update.

severach commented on 2019-08-10 01:37

Provides requires version numbers to function properly. This line will add all versions at once. provides=("${provides[@]/%/=${pkgver%%.r*}}")

dbermond commented on 2019-07-24 20:47

@Schlaefer It looks like that ffmpeg-qsv is currently linking against the wrong file, as it's using libmfx in depends. Its maintainer is already aware of the problem.

This package builds in the correct way. That's because it works for you and ffmpeg-qsv does not.

As you need ffmpeg with multiple additional features, I suggest you to use ffmpeg-full instead of manually editing the PKGBUILD here.