On 14/02/2023 13:33, Takashi Yano via Cygwin-apps wrote:
On Mon, 13 Feb 2023 18:02:27 +0000
Jon Turney wrote:
On 06/02/2023 12:21, Takashi Yano via Cygwin-apps wrote:
On Sun, 5 Feb 2023 16:33:45 +0000
Jon Turney wrote:
On 05/02/2023 08:40, Takashi Yano via Cygwin-apps wrote:
[ITP]
[...]
AMF: for ffmpeg (new)
[...]
nv-codec-headers : for ffmpeg (new)
I have a question about how this (and AMF I guess) works.
Are these headers which implement the whole codec? or do they expect the
codec to be accessible via the driver somehow?
nv-codec-headers provides header files which dynamically
loads nvcuda.dll, nvcuvid.dll and nvEncodeAPI{,64}.dll.
Similary, AMF loads amfrt{64,32}.dll dinamically.
The codec itself is implemented in the dlls which is provided
by nVidia/AMD. mfx_dispatch also does the similar. It loads
some dlls dynamically privided by Intel.
I see.
It might be helpful to mention that (in general terms) in the
description for those packages.
I have added descriptions to cygport files each of AMF,
nv-codec-headers and mfx_dispatcher.
Generally, there are some ABI concerns with using interfaces like this,
e.g.:
[...]
Therefore, I do not think the problems i) and ii) apply.
Thanks very much for investigating and checking these details.
These are approved.
