FFmpeg 9.0

Post by jobigoud » Tue, Aug 04, 2026, 2:10 PM UTC

thinkingtoilet wrote: post #57

cm2187 wrote: post #50

Earlier quoted context omitted.

Though there is one part I didn’t understand in that interview. They were complaining of being overwhelmed by AI submitted bug reports (fair), including for obscure codecs that must have been used by a couple of users at most. And therefore implying that securing those codecs is low priority/important. I don’t understand that. To me the severity has nothing to do with how popular is a code path, but whether that code…

It's all about time in the day, my friend. Do you want to secure a feature used by 100% of your users or 0.01% of your users? Which has a better ROI?

Post by gyan » Tue, Aug 04, 2026, 2:15 PM UTC

blacklion wrote: post #59

It is interesting, that changes from 8.0 to 8.1 is more substantial than from 8.1 to 9.0. I don't say it to mean "they did less work," no, what his interesting to me is choice of major version bump instead of minor one.

Post by luckydata » Tue, Aug 04, 2026, 2:23 PM UTC

jobigoud wrote: post #61

thinkingtoilet wrote: post #57

Earlier quoted context omitted.

It's all about time in the day, my friend. Do you want to secure a feature used by 100% of your users or 0.01% of your users? Which has a better ROI?

It's used by most users, that's what they are saying, it doesn't matter that the file format is obscure. If you make a video player based on ffmpeg you take input videos. The attacker can share a specially crafted video with the victim. Same kind of attack as sharing word documents.

Post by [deleted] » Tue, Aug 04, 2026, 2:32 PM UTC

jobigoud wrote: post #64

timonoko wrote: post #32

Only slightly broken already. Dont remember the details, but Gemini could not this to work just by reading the manual. https://github.com/timonoko/Skipperi

What do you mean you don't remember, your repo is from 8 months ago, this release is from 18 hours ago. And how does "Gemini couldn't get it to work" translate to "it's broken"? It sounds like your vibe-coding session didn't work first try and you haven't tried to understand what the problem was. You could also look at other repos in github to see what they do to do the same task.

Post by znpy » Tue, Aug 04, 2026, 2:41 PM UTC

brookst wrote: post #27

dspillett wrote: post #23

Earlier quoted context omitted.

> Although i was under the impression that they usually preferred hand optimized assembly. Using LLMs/agents to do gap analysis and fill boilerplate doesn't rule out also reviewing the output and hand-optimising. That is how the tools should be used (if you aren't being a luddite like me and not using them at all) rather than click-and-hope vibe-coding.

And as a ffmpeg user with some old/weird hardware, I would much prefer click-and-hope support to no support at all. Ideally they’d have the resources for a real live human to hand-code assembly for every codec for every platform, but that’s probably not realistic. I’ll take what I can get and dust off my assembly skills if a click-and-hope implementation is close but not quite enough.