On August 20, 2025 10:47:03 PM PDT, Lynne via ffmpeg-devel
wrote:
> +Hardware accelerated decoding: Vulkan VP9, VAAPI VVC, OpenHarmony
> H264/5
> +Hardware accelerated encoding: Vulkan AV1, OpenHarmony H264/5
> +Filters: colordetect, pad_cuda, scale_d3d11, Whisper, and others
maybe
On August 19, 2025 1:45:01 AM PDT, ffmpeg--- via ffmpeg-devel
wrote:
> We have have already completed implementation of this protocol into FFMPEG 7
> and I enclose patches to add this to the current FFmpeg origin/master.
>
>
> If the .eml patches dont make it through the email, here are lin
PR #20289 opened by Jacob Lifshay (programmerjake)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20289
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20289.patch
Add myself to codeowners. I didn't add myself to maintainers because I'm not
planning on being all that active, but I can at
On August 19, 2025 2:27:12 PM PDT, Michael Niedermayer via ffmpeg-devel
wrote:
> Hi all
>
> what name should we give 8.0 ?
IDK if it's a very good suggestion, but Hachi? It's both the Japanese number 8,
as well as a common nickname. There's a famously loyal dog with that name:
https://en.w
On September 18, 2025 2:15:22 AM PDT, Nicolas George via ffmpeg-devel
wrote:
> If this web monster does not let you push code in your private fork
> without asking to include it upstream, it is one more reason not to use
> that thing.
It does let you push to your private fork without updating
On Thu, Sep 18, 2025 at 12:03 AM Nicolas George via ffmpeg-devel
wrote:
>
> Timo Rothenpieler via ffmpeg-devel (HE12025-09-18):
> > The problem is they can be very frequent. And not only force pushes.
> > So the current implementation is a compromise between visibility and
> > spam-level.
>
> They
