typed-ffmpeg

Can you explain to me why, despite "full type safety, autocomplete and validation" being the focus of "typed-ffmpeg", it makes sense to be passing width and height (or the x and y co-ordinates) as strings here? ``` .drawbox(x="50", y="50", width="120", height="120", color="red", thickness="5") ``` (from https://github.com/livingbio/typed-ffmpeg?tab=readme-ov-file... )

Hi HN, I built typed-ffmpeg, a Python package that lets you build FFmpeg filter graphs with full type safety, autocomplete, and validation. It’s inspired by ffmpeg-python, but addresses some long-standing issues like lack of IDE support and fragile CLI strings. What’s New in v3.0: • Source filter support (e.g. color, testsrc, etc.) • Input stream selection (e.g. [0:a], [1:v]) • A new interactive playground where you can: • Build filter graphs visually • Generate both FFmpeg CLI and typed Python code • Paste existing FFmpeg commands and reverse-parse them into graphs Playground link: https://livingbio.github.io/typed-ffmpeg-playground/ (It’s open source and runs fully in-browser.) The internal core also supports converting CLI → graph → typed Python code. This is useful for building educational tools, FFmpeg IDEs, or visual editor