PR #21042 opened by russelltg
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21042
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21042.patch
When a frame is exported to DRM, it may be written to to read to in an
asyncronous fashion. Make sure, on unmap of a Vulkan frame that was mapped
PR #21041 opened by derrod
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21041
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21041.patch
The range of `cpu-used` has been increased to `[0, 12]` a while ago, see aom
help text for example:
https://aomedia.googlesource.com/aom/+/refs/hea
PR #21040 opened by Zhao Zhili (quink)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21040
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21040.patch
For example:
./ffmpeg -hwaccel videotoolbox \
-i input.mp4 -c:a copy \
-vf scdet=threshold=10 \
-c:v h264_videot
PR #21038 opened by Niklas Haas (haasn)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21038
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21038.patch
The current logic assumes `s->reset_sar` always resets the SAR, but this
is only true if `force_oar` is actually true as well, meaning t