Discussion

FFmpeg Subtitle Tools

arthurjean: The Claude Code workflow here is interesting, having it write the encoder, then run review from five angles, then argue about architectural decisions. That's a more structured use of AI than just "generate code and accept." Curious how much of the 23 patches were Claude's first attempt vs. iterations where you had to course-correct.The fact that this bug sat open for 12 years and got fixed by one person with an AI assistant in a few weeks says something about the kind of work AI-assisted development unlocks, not greenfield apps, but gnarly legacy fixes nobody wanted to touch.

gyan: If you do open PRs at code.ffmpeg.org, remember to disclose and describe the AI contribution. You will also need to add FATE tests.

gus_massa: Where is the source code? https://github.com/connollydavid/FFmpeg/tree/pgs3-8.0.1 ?

slartibardfast0: https://github.com/connollydavid/FFmpeg/tree/pgs7-8.1is the most recent

slartibardfast0: oh yes, every commit is fully open about Claude Code + the model.honestly, it would've taken me about 2 years to do this otherwise.there are many FATE tests added and a lot more to add when the hardware verification bits i'm planning are done

KomoD: Open since 2014? No? It was opened in 2014 and closed as fixed in 2014.

slartibardfast0: mm, text to bitmap or vice-verse isn't there though is it?edit: plus the blu-ray subtitle encoder itself is new...