Package Details: ffmpeg-full 6.1.1-6

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 libfdk-aac)
Upstream URL: https://www.ffmpeg.org/
Keywords: audio codec convert cuda cuvid decklink encoder fdk-aac fdkaac hwaccel libnpp media nvenc svt video
Licenses: LicenseRef-nonfree-and-unredistributable
Conflicts: ffmpeg
Provides: ffmpeg, libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Submitter: rpolzer
Maintainer: dbermond
Last Packager: dbermond
Votes: 134
Popularity: 0.89
First Submitted: 2013-01-24 11:17 (UTC)
Last Updated: 2024-05-02 21:46 (UTC)

Required by (1823)

Sources (15)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 53 Next › Last »

boesi commented on 2024-02-24 15:40 (UTC) (edited on 2024-02-24 15:42 (UTC) by boesi)

@frankenstein20 I installed these libraries in an older version

  • glslang 13.1.1-3
  • libplacebo 6.338.1-1
  • shaderc 2023.7-2

But now I have an unsupported Arch installation :-(

The problem is, that glslang 14 removed the HLSL and OGLCompiler, but ffmpeg depends on them. Maybe you could use the glslang-git and shaderc-git packages, which are the still the old versions.

frankenstein20 commented on 2024-02-24 14:38 (UTC)

does anyone know how to solve "ERROR: spirv_compiler not found"?

LudwigJ commented on 2024-01-28 14:04 (UTC)

@dbermond I did rebuild, but apparently I pressed N when asked to clean the tree... Oh well... I rebuilt with a clean tree, and problem solved, thanks.

dbermond commented on 2024-01-28 00:14 (UTC)

@LudwigJ You missed the libvpx 1.14.0 rebuild. Rebuild the package against libvpx 1.14.0. Please remember that it's user responsibility to keep track of all installed AUR packages and do the needed tasks in each one of them, like doing the needed rebuilds in time.

LudwigJ commented on 2024-01-27 23:01 (UTC)

The package builds fine, but after installing it, many programs fail to run throwing this error:

error while loading shared libraries: libvpx.so.8: cannot open shared object file: No such file or directory

I don't understand what's happening, my system is up-to-date, I have libvpx 1.14.0-1 installed (providing libvpx.so.9) and if I remove ffmpeg-full and reinstall ffmpeg, everything runs fine again. But as soon as I install ffmpeg-full, I get the same error again.

Bluebomber182 commented on 2024-01-08 00:51 (UTC)

Just a heads up if you try to install ffmpeg full, you'll get a terminate called after throwing an instance of 'std::bad_alloc' error message if you try to import torchaudio. You'll need to patch lensfun-git before compiling ffmpeg full. Here's a link for the patch. https://github.com/lensfun/lensfun/issues/2129#issuecomment-1836858140

dbermond commented on 2023-11-18 23:28 (UTC)

@boesi Yes, there was a need for using ffnvcodec-headers-git for providing av1_nvenc. But the reason for installing is not relevant in this case. What is important is that you should keep track of all your AUR packages, specially the VCS ones (-git, -hg, -svn, etc), as they usually does not get regular version bumps. VCS packages should be regularly updated by the user, as the package maintainer is not required to do version bumps in these type of packages. When you install an AUR package (whatever the reason for installing it), you are completely responsible for it. If you installed it without noticing due to the use of an AUR helper, chances increases for you to have problems. Using makepkg is the right method, is a manual process, and the only supported one. When you delegate all AUR tasks to a helper and simply ignore that you have regular tasks to do with every single installed AUR package, you have a higher chance to encounter a problem sooner or later. If you are already using the makepkg method, that's good, and you just cannot forget about your AUR packages, none of them. I cannot speak if other users are having the same issue as you. What I can say is that the users that are acting like the Arch Wiki recommends (by doing the needed tasks on their AUR packages) should not have such issue.

boesi commented on 2023-11-18 21:49 (UTC)

@dbermond Well, I certainly didn't install it on purpose. But in the commit logs of ffmpeg-full you can see that in version 6.0-1 the make dependency for ffnvcodec-headers was changed to ffnvcodec-headers-git and in version 6.0-2 it was changed back to ffnvcodec-headers. On this occasion I must have missed to remove the make dependencies as I usually do. Do I understand correctly that everyone who has done the same is now having this problem?

Please note that I am not blaming anyone. I just want to learn how to keep my system healthy.

dbermond commented on 2023-11-18 16:11 (UTC)

@Milor123 The package is building fine. The nvcc issue has been discussed several times in ffmpeg-full-git. See there the comments from previous couple of years. By your log, it looks like you are using an AUR helper, and this is not supported, use makepkg.

dbermond commented on 2023-11-18 16:06 (UTC)

@boesi If you have installed ffnvcodec-headers-git for some reason, it's up to you to keep track of it and either update it regularly or switch to the stable version when not needing the -git one anymore. There is no special solution for finding outdated AUR packages. You need to keep track of all your packages that are not handled by pacman and act accordingly to each one of them. Please see: https://wiki.archlinux.org/title/Arch_User_Repository#Updating_packages .