Code:
Take for example a software package that is distributed at no cost and to which the developer wants to add support for a video format which requires a patent licence. If there is a licence which requires a tiny per-copy fee, the software project will not be able to avail of the licence. The licence may be called "(F)RAND", but the modalities discriminate against a whole category of intangible goods such as free software[11] and freeware.[12]
This form of discrimination can be similarly caused by common licence terms such as only applying to complete implementations of the licensed standard, limiting use to particular fields, or restricting redistribution. The Free Software Foundation suggests the term "uniform fee only" (UFO) to reflect that such "(F)RAND" licenses are inherently discriminatory.
https://en.wikipedia.org/wiki/Reason...bution_schemes
Code:
AMD added support for H264 only video encoding on Linux through AMD Video Coding Engine (GPU encoding) with the AMDGPU PRO proprietary packages, and ffmpeg added support for AMF video encoding, so in order to encode using the h264_amf video encoder, amf-amdgpu-pro (AUR) is required.
From the AMD open source driver, released May 21st, 2025
Code:
AMF will no longer be included in the release. AMF users are advised to transition to VA-API / Mesa Multimedia. Some examples of ffmpeg use cases with VA-API / Mesa Multimedia are shown below:
Hardware Decode:
ffmpeg -hwaccel vaapi
Hardware Encode:
ffmpeg -vaapi_device /dev/dri/renderD128 -i in.mp4 -vf hwupload,scale_vaapi=format=nv12 -c:v h264_vaapi out.mp4
Hardware Transcode:
ffmpeg -vaapi_device /dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi -i in.mp4 -c:v hevc_vaapi out.mp4
AMF is the ffmpeg library layer that would be used for the video acceleration, decode, encode, ecc..
Sorry again, and closing
Mick Taylor
!