FFmpeg devs call out AMD over “AI slop” patch

FFmpeg’s official X/Twitter social media account publicly poked AMD this week, saying FFmpeg developer was unhappy with “AI slop patches,” and pointed to a now-closed pull request on FFmpeg’s code server. The linked PR tried to add build support for AMD’s HIP SDK on Windows . In case you are not sure what HIP is, AMD HIP (Heterogeneous-computing Interface) SDK is a way to bring a subset of ROCm to Windows, with tooling and APIs for GPU compute using HIP.

In the review thread, FFmpeg devs pushed back on what looked like LLM-style details, both in the patch and in the commit message. They basically objected to end-user setup guidance being stuffed into a commit message, including instructions around software called pacman, instead of keeping the message focused on what changed and why.

AMD dev argued that the long-form guidance came from real build experience and older documentation, not random filler. The author later altered parts of the message after reviewers kept the discussion on commit standards.

The pull request still ended up closed on technical direction, not just presentation. FFmpeg has been investing in vendor-neutral GPU paths through Vulkan, including Vulkan-based decoding work that landed as a cross-platform, cross-vendor approach.

Perhaps FFmpeg comments were too harsh, given it was just a summarization of the work previously done. But the good news is that at least some devs are still reading and checking all commits. This also got me thinking: gamers could start a token fund for AMD, so that they could AI-slop FSR4 support for RDNA3.

Source: FFMpeg

Follow us on Google News Set as Preferred Source

Share