Package Details: ffmpeg-full-git 4.4.r98424.g73757577cb-1

Git Clone URL: (read-only, click to copy)
Package Base: ffmpeg-full-git
Description: Complete solution to record, convert and stream audio and video (all possible features including libfdk-aac; git version)
Upstream URL:
Keywords: audio codec convert cuda cuvid decklink encoder fdk-aac fdkaac hwaccel libnpp media nvenc svt video
Licenses: custom: nonfree and unredistributable
Conflicts: ffmpeg
Provides: ffmpeg, ffmpeg-full, ffmpeg-git,,,,,,,,,
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 15
Popularity: 1.48
First Submitted: 2015-12-27 19:22
Last Updated: 2020-07-06 19:18

Dependencies (109)

Required by (1000)

Sources (6)

Latest Comments

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

ggrub commented on 2019-05-21 08:13

! LaTeX Error: File `newunicodechar.sty' not found.

dbermond commented on 2019-04-02 23:40

@Fog This is already fixed.

Fog commented on 2019-04-02 21:33

I've encountered that issue too and just removed that option from pkgbuild.

dbermond commented on 2019-03-23 18:19

@filthyAUR Fixed in the latest package update.

kescherAUR commented on 2019-03-20 20:17

==> Starting build()...
  -> Running ffmpeg configure script...
Unknown option "--enable-libndi_newtek".
See ./configure --help for available options.
==> ERROR: A failure occurred in build().
Error making: ffmpeg-full-git

Caused by: libndi_newtek was removed. PKGBUILD should remove that argument to ./configure.

dbermond commented on 2019-03-20 00:55

@TomCatT Thank for using this package. Enjoy. :)

TomCatT commented on 2019-03-14 14:33

This works like a champ AND I can use it to stay on top of the latest update. I should have used Arch Linux years ago. Thanks.

dbermond commented on 2019-02-22 01:48

@filthyAUR I have temporarily disabled cuda-sdk since upstream is taking longer than expected to fix it.

kescherAUR commented on 2019-02-19 17:18

Alright, guess I'll just disable cuda-sdk as I don't need it on my machine anyway.

dbermond commented on 2019-02-18 00:41

@filthyAUR This is a known upstream issue. You can follow the problem in the upstream bug tracker at ticket #7742.