Package Details: ffmpeg-full-git 7.2.r119073.g2657e1679e-1

Git Clone URL: https://aur.archlinux.org/ffmpeg-full-git.git (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: 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, ffmpeg-full, ffmpeg-git, libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 21
Popularity: 0.007908
First Submitted: 2015-12-27 19:22 (UTC)
Last Updated: 2025-03-30 03:37 (UTC)

Required by (1943)

Sources (7)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 Next › Last »

MichaelChou commented on 2018-02-09 04:49 (UTC)

@dbermond

For the following somehow related problems: 1. ffmpeg(-full)-git and ffmpeg(-full) can not co-exist. 2. Packages depend on ffmpeg libs need to recompile every time the so version number changes. And that's a lot of them. 3. A few software are not compatible with the ffmpeg(-full)-git.

I have a suggestion: create a ffmpeg git package just like the official ffmpeg2.8 (https://www.archlinux.org/packages/extra/x86_64/ffmpeg2.8/).

I wonder what's your opinion about this? - Should this package change to that structure? - Or should we make another package to do that? And if this is the way to go, I can find some time to maintain that. What package name do you suggest this package to have?

dbermond commented on 2018-02-03 23:56 (UTC)

@ahjolinna Thank you for pointing this and for the interest in ffmpeg-full-git. Switched zimg-git dependency back to zimg.

ahjolinna commented on 2018-02-03 16:54 (UTC)

zimg 2.7.3 is now in repos, git version shouldn't be needed anymore (at least for now :D)

dbermond commented on 2017-12-06 17:56 (UTC)

@ahjolinna That's true. I'm using zimg-git too for the last days. I was hoping that zimg version 2.6.3 would solve this issue, but currently it really needs zimg git master. I have temporarily switched zimg dependency to zimg-git. Thank you for the interest.

ahjolinna commented on 2017-12-05 16:17 (UTC)

I needed to install zimg-git for this to compile, didn't compile with "stable" 2.6.2 (nor 2.6.3 )

dbermond commented on 2017-11-01 19:40 (UTC) (edited on 2017-11-01 19:52 (UTC) by dbermond)

@Nothing4You This is normal and expected. That's because ffmpeg git master has switched API in preparation for the next 3.5 release. For this, they increased the so-version-number of the libraries. Since repository packages are compiled against ffmpeg 3.4, they will fail to locate the older target libraries that have lower so-version-numbers. Some possible options are: 1) Recompile all your software that depends on ffmpeg. But many of these software will fail to compile with the newer ffmpeg git master, since this is fairly new code. An example is Firefox. At least, it did not compiled for me on the last time that ffmpeg switched API. I didn't even tried recompile Firefox this time (it takes a lot of time). An example that currently works is vlc, but you will need to use vlc-git from aur. 2) Use another software. For example, I'm using chromium, which does not depend on ffmpeg. 3) If you cannot live without Firefox or any other favorite software, currently you need to use ffmpeg 3.4 (from the official repositories or ffmpeg-full if you wish), or ask upstream to support ffmpeg git master.

Nothing4You commented on 2017-11-01 13:00 (UTC)

Latest git doesn't seem to be compatible with firefox anymore. Repo ffmpeg works fine. When running firefox with latest git from this package it isn't able to directly play video and audio anymore. It'll just prompt me to download them. Youtube html5 playback doesn't work, their html5 test page says my browser doesn't support h264. Do you happen to know whether that's some kind of known issue and whether it's something on mozillas side or ffmpegs side that will have to get adjusted?

dbermond commented on 2017-10-24 19:36 (UTC)

@Nothing4You Everything is up-to-date with upstream now. Thank you for the interest and report. Regarding the flite1 package issue, I have temporarily removed libflite in order to give some time to the flite1 maintainer to deal with it, although he has not yet answered.

Nothing4You commented on 2017-10-23 21:30 (UTC)

See https://github.com/FFmpeg/FFmpeg/commit/a2a7b02fbd9d96ff12280cfa03bbce6b8c797932

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 Next › Last »