Package Details: ffmpeg-full 4.2.2-1

Git Clone URL: https://aur.archlinux.org/ffmpeg-full.git (read-only, click to copy)
Package Base: ffmpeg-full
Description: Complete solution to record, convert and stream audio and video (all possible features including nvenc, qsv and libfdk-aac)
Upstream URL: https://www.ffmpeg.org/
Keywords: audio codec convert cuda cuvid decklink encoder fdk-aac fdkaac ffmpeg hwaccel intel-svt libnpp media nvenc qsv quicksync svt vaapi video
Licenses: custom: nonfree and unredistributable
Conflicts: ffmpeg
Provides: ffmpeg, libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavresample.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Submitter: rpolzer
Maintainer: dbermond
Last Packager: dbermond
Votes: 78
Popularity: 0.030203
First Submitted: 2013-01-24 11:17
Last Updated: 2020-01-03 23:12

Dependencies (102)

Required by (970)

Sources (7)

Latest Comments

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

dbermond commented on 2020-01-07 01:19

@Danieldakataca This error should not appear at all. Please see my previous messages from 2019-06-11 for explanation.

xzntest commented on 2020-01-07 01:05

@Danieldakataca

Log out then log back in after installing cuda, or source etc/profile.d/cuda.sh manually

Danieldakataca commented on 2019-12-16 06:33

==> Iniciando build()... -> Running ffmpeg configure script... ERROR: failed checking for nvcc.

If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file "ffbuild/config.log" produced by configure as this will help solve the problem. ==> ERROR: Se produjo un fallo en build(). Cancelando...

smoneck commented on 2019-11-22 12:37

Same as Verequies here with vmaf 1.3.15:

-> Running ffmpeg configure script... ERROR: libvmaf >= 1.3.9 not found using pkg-config.

Confirming it compiles successfully without --enable-libvmaf.

dbermond commented on 2019-11-16 13:54

@FraYoshi You need to rebuild ffmpeg-full every time that one of its dependencies get a soname bump. In this case, dav1d got a soname bump when upgrading it from 0.4.0 to 0.5.0.

FraYoshi commented on 2019-11-16 12:40

ffmpeg-full breaks chromium (/usr/lib/chromium/chromium: error while loading shared libraries: libdav1d.so.2: cannot open shared object file: No such file or directory) and NetFlix (Error Code: F7355) for me...

Solved replacing with ffmpeg standard

dbermond commented on 2019-08-22 17:31

@ganthore

1) hm is not a dependency for ffmpeg-full, so it's not needed here. vmaf and blackmagic-decklink-sdk are already in makedepends.

pocketsphinx currently builds fine for me. If you have any concerns about pocketsphinx please direct it to its package maintainer.

2) nvcc path is not missing, this was already answered. Please see the 2 comments from 2019-06-11. In short: nvcc path is handled by makepkg because it automatically sources the profile file when pulling and installing cuda.

ffmpeg-full is building fine in a chroot with devtools so it builds fine in a fresh Arch install.

ganthore commented on 2019-08-22 15:48

There are two problems that need to be corrected with the PKGBUILD.

1) Missing or broken deps

On a fresh install of arch, the PKGBUILD building phase will fail due to the following packages not being set as dependencies:

hm (required for kvazaar to build) vmaf blackmagic-decklink-sdk

Also note that the pocketsphinx PKGBUILD is broken, so it may be better to use the pocketsphinx-git package as a workaround.

2) nvcc is missing

The build process will fail because you're assuming people have /opt/cuda/bin in their system or root shell path. An easy workaround is to export this into the PATH during the build phase: "export PATH=$PATH:/opt/cuda/bin"

craeckie commented on 2019-08-13 10:29

strange, I had intel-svt-hevc installed at 1.4.0-1. Still, after rebuilding and installing it, I was able to build ffmpeg.

dbermond commented on 2019-08-12 19:15

@craeckie Package is building fine. Please make sure that you have an updated intel-svt-hevc (currently at 1.4.0-1).