Package Details: ffmpeg-full 7.0.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 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: 135
Popularity: 1.23
First Submitted: 2013-01-24 11:17 (UTC)
Last Updated: 2024-08-03 21:35 (UTC)

Dependencies (130)

Required by (1904)

Sources (10)

Pinned Comments

dbermond commented on 2024-06-24 15:59 (UTC)

@LordSIGSEGV avoid creating files not tracked by pacman in the system reserved directories, specially symlinks to shared libraries, as this have the potential to completely break your system. I have already notified the quirc maintainer in the aur web page of the package in April-2024. While this issue is not solved in quirc, I recommend to use quirc-git, which currently has a better packaging and does not suffer from this problem.

Latest Comments

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 55 Next › Last »

lonaowna commented on 2018-05-13 13:40 (UTC)

For anyone using this package just for NVENC: that's also available in the official package since ffmpeg 4.0-2.

ggrub commented on 2018-05-13 12:11 (UTC)

@dbermond intel-media-sdk-git (1.2a.r149.gfdd82d8-1), libmfx (1.23-1) How do i enable the iHD driver ?

dbermond commented on 2018-05-12 18:05 (UTC)

@misanthropist I don't think so. The changes are mostly on the programming (API) level. Upstream ffmpeg tends to be conservative in command line by preserving deprecated options in order to avoid end-user breakage. But anyway, I suggest you to test everything just to make sure.

misanthropist commented on 2018-05-12 17:48 (UTC)

I have some shell scripts that use ffmpeg, so to avoid problems: are there any changes to the commandline options?

dbermond commented on 2018-05-12 16:20 (UTC)

ffmpeg 4.0 is now on the official repositories, so we can safely push ffmpeg-full 4.0 here.

Enjoy.

dbermond commented on 2018-05-12 16:17 (UTC)

@ggrub Do you enabled the iHD driver? Are you using intel-media-sdk or intel-media-sdk-git? Do you have libmfx{,-git} installed?

ggrub commented on 2018-05-08 20:34 (UTC) (edited on 2018-05-08 20:35 (UTC) by ggrub)

are you're sure the h264_qsv is working?

ffmpeg -i test.ts" -c:v h264_qsv -global_quality 10 -look_ahead 0 out.mp4 (i7-6700k)

[h264_qsv @ 0x55c42d1516e0] No device available for encoder (device type qsv for codec h264_qsv).

[h264_qsv @ 0x55c42d1516e0] Selected ratecontrol mode is not supported by the QSV runtime. Choose a different mode.

FrederickZh commented on 2018-04-24 02:57 (UTC)

Thanks, dark-saber. It worked after recompiling libopenmpt-svn :)

dbermond commented on 2018-04-23 18:45 (UTC)

Important notes:

  • ffmpeg 4.0 was released by upstream. This version contains major changes: it switched API and increased library version numbers.

  • ffmpeg is a multimedia backend for many applications that resides on the official repositories. Since the 4.0 version is quite new and has a different API (and different library version numbers), it is possible that some applications are not yet ready to support it.

  • Currently, ffmpeg on the official repositories is still at version 3.4.2. It means the packages from the official repositories that depends on ffmpeg are still linking to library version numbers from 3.4.2 (for example, packages linking to libavcodec are still linking to libavcodec.so.57).

  • If we upgrade ffmepg-full to version 4.0 before ffmpeg is updated in the official repositories, all packages on official repositories that depend on ffmpeg will break complaining about missing libraries (for example, ffmpeg 4.0 introduces libavcodec.so.58, and packages linking to libavcodec.so.57 will stop to work - this will happen to packages like firefox, mpv and vlc, just to name a few).

  • That's why it's not a good idea to upgrade ffmpeg-full to version 4.0 before ffmpeg is updated in the official repositories, because it can break too much important things (depending on the packages that a user have installed). The Arch Linux developers have to be sure that all packages on the official repositories that depend on ffmpeg can successfully be built with the new 4.0 API. This can take time. Please be patient. After 4.0 is released on the official repositories we can safely upgrade it here.

  • If you want to use the new 4.0 API and features right now, I suggest you to use the package ffmpeg-full-git, but you'll be for your own for dealing with breakages that it may cause. At this moment, ffmpeg-full-git (git master branch) is quite the same as the stable 4.0 version, because 4.0 was just released.

dark-saber commented on 2018-04-23 11:41 (UTC)

FrederickZh:

I cannot reproduce this error neither on my working machine, nor on arch/mainline or arch/testing clean machines. Could you please make sure that libopenmpt-svn is recompiled and updated to the latest verison? Possible causes could also include other not updated/recompiled AUR packages or specific makepkg settings. Also, what's your environment (gcc -v, uname -a)?

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 55 Next › Last »