Package Details: ffmpeg-amd-full-git 7.1.r114795.g0e4dfa4709-1

Git Clone URL: https://aur.archlinux.org/ffmpeg-amd-full-git.git (read-only, click to copy)
Package Base: ffmpeg-amd-full-git
Description: Complete solution to record, convert and stream audio and video (all possible features for AMD; git version)
Upstream URL: https://www.ffmpeg.org/
Keywords: audio codec convert encoder media svt video
Licenses: custom: 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: clap22
Maintainer: nathanielcwm
Last Packager: nathanielcwm
Votes: 12
Popularity: 0.000026
First Submitted: 2018-11-20 15:20 (UTC)
Last Updated: 2024-04-10 23:13 (UTC)

Required by (1830)

Sources (7)

Pinned Comments

saburouta commented on 2023-04-26 18:45 (UTC)

I adopted this package to keep it from falling off, but I haven't had the chance to update it yet.

I think only patches 40 and 60 still work. I'm not sure the other even need to be updated. I've been building with just 40 and 60.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 Next › Last »

JackuellnHdyde commented on 2019-10-23 11:36 (UTC)

@ReekyMarko:

For me using amdgpu-pro weren't a problem so far, since I just needed this version of ffmpeg to be run on a headless machine. Additionally I'm not interested in AMD AMF anymore, since the progress will probably take quite some time and I want some hardware encoder that actually works - now. It were an ... interesting experience, but I will stick with VAAPI if I can and if I'm able to either make use of cropping or remove black bars that VAAPI seems to add. (compared with x265)

If I'm trying AMF again I will shoot you a message if no one else asked for it. Greets

FunctionalHacker commented on 2019-10-23 08:19 (UTC)

@JackuellnHdyde Thanks for your investigation. If you notice before me that the support was added, drop a message here to let me know. I could make you a co-maintainer for this package too.

To be honest, I'm not that interested in AMF until I can use it with the open source drivers. SwayWM (Wayland) freezes consistently with amdgpu-pro and I also like to support open source as much as possible.

JackuellnHdyde commented on 2019-10-22 22:35 (UTC) (edited on 2019-10-22 22:46 (UTC) by JackuellnHdyde)

@ReekyMarko

You're right, after more testing I realized what you already found out yourself. I'm not very familiar with all this stuff and just reading into it currently and expected I just had to init the device like I would do with VAAPI and it took me some time to find out that I didn't used wrong cmd args. It seems the full implementation will happen next year or at least AMD will provide a better API. At least we now know how to add the support when time has come.

Edit: I found some more explanation about why it might or will not work for some of us anyway. You need at least VCE3.4 to make H264_AMF i.e. work, like described here: https://github.com/obsproject/obs-amd-encoder/wiki/Hardware-Support#Devices-5 There's also a reddit thread about this topic for those interested: https://www.reddit.com/r/Amd/comments/8eirp4/ffmpeg_40_released_includes_amf_hardware_encoding/

FunctionalHacker commented on 2019-10-22 19:33 (UTC)

@JackuellnHdyde I've now built ffmpeg with amf support, installed all drivers and the dependencies you mentioned. Trying to encode a video with a command like this:

ffmpeg -i video.avi -crf 18 -c:v h264_amf -c:a copy video.mkv

Results in the following error:

[h264_amf @ 0x564d188e5a00] AMF failed to initialise on the given Vulkan device: 1.
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!

Apparently only vulkan initialization is implemented from what I've read around online. I have vulkan-radeon and vulkan-amdgpu-pro installed. Do you have any workaround for this? I would rather not push the updated PKGBUILD until it's deemed working.

FunctionalHacker commented on 2019-10-15 10:36 (UTC)

@JackuellnHdyde thanks for the heads up. I will try to build it today or tomorrow and see how it goes. I've never used amdgpu-pro so it might get interesting. How can I test that AMF works? Does mpv support it?

JackuellnHdyde commented on 2019-10-15 10:32 (UTC)

@ReekyMarko: Hello, I wanted to ask if it is possible to add support for AMD AMF? I already altered the PKGBUILD and it seems to work with AUR dependencies "amf-amdgpu-pro" and "amf-headers-git". Afaik the amf driver is needed to be able to initialize the device and the amf headers are needed to be able to build ffmpeg with "-enable-amf" flag according to ffmpeg docs. (see: https://www.ffmpeg.org/general.html#AMD-AMF_002fVCE)

FunctionalHacker commented on 2019-10-04 10:52 (UTC)

You might want to remove --enable-omx-rpi. This is for the Raspberry Pi and I had to remove it to get it to build on my PC. Doubt it has much to do with AMD setups.

CaffeinatedTech commented on 2019-08-26 00:52 (UTC)

Build is failing.

In file included from libavcodec/omx.c:29:
libavcodec/omx.c: In function ‘omx_encode_frame’:
libavcodec/omx.c:807:44: error: ‘OMX_IndexConfigBrcmVideoRequestIFrame’ undeclared (first use in this function); did you mean ‘OMX_IndexConfigVideoFramerate’?
  807 |             err = OMX_SetConfig(s->handle, OMX_IndexConfigBrcmVideoRequestIFrame, &config);
      |                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

FunctionalHacker commented on 2019-05-29 08:20 (UTC) (edited on 2019-05-29 08:59 (UTC) by FunctionalHacker)

Anybody else have trouble with tensorflow? I'm getting this message when the ffmpeg build starts:

ERROR: libtensorflow not found

EDIT: I got it to build by adding this to configure:

--extra-cflags='-I/usr/include/tensorflow'

clap22 commented on 2019-04-22 18:27 (UTC)

@morosa You get that error when you do what exactly?

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 Next › Last »