Like #220327, this fixes the following errors:
ERROR: cuda requested, but not all dependencies are satisfied: ffnvcodec
ERROR: cuvid requested, but not all dependencies are satisfied: ffnvcodec
ERROR: nvenc requested, but not all dependencies are satisfied: ffnvcodec
This fixes the following errors:
ERROR: cuda requested, but not all dependencies are satisfied: ffnvcodec
ERROR: cuvid requested, but not all dependencies are satisfied: ffnvcodec
ERROR: nvenc requested, but not all dependencies are satisfied: ffnvcodec
When cross-compiling, the build platform compiler ends up in the runtime
closure because it is included in the configure flags that get embedded in the
binaries. To fix this, add the compiler to the remove-references-to invocation.
ffmpeg was having issues while trying to use the nvenc encodings due to
not finding libcuda.so.1
this was because addOpenGLRunpath was pointing to $out/lib instead of
using the placeholder path of the lib output
Co-authored-by: Mats <mats@mats.sh>
A ton of cleanup and refactoring went into this. Too much to list.
Co-authored-by: Anderson Torres <torres.anderson.85@protonmail.com>
Co-authored-by: Martin Weinelt <mweinelt@users.noreply.github.com>
ffmpeg 5.1 introduced ipfs:// and ipns:// streaming support as part of
libavformat. This new implementation falls back to fetching from an
untrusted 3rd party internet service in the (likely) case where a user
doesn't have a local IPFS gateway running on their computer. This puts
an unaudited 3rd party provider in a position where they can log and
alter any IPFS content being streamed by the ffmpeg library. No user
consent is collected at any point by the library.
ffmpeg developers are currently discussing [1] how to better implement
this feature. In the meantime, cherry-pick the proposed patch to disable
the default gateway until a better alternative is released.
[1] https://ffmpeg.org/pipermail/ffmpeg-devel/2022-August/299924.html
