I'm Quentin. I've just published my longterm project - excited to share! m0saic is a video compiler. Typescript programs define an explicit spatial layout via a string DSL (m0), and configure what goes into each independent rect over a shared timeline. This media intent IR gets lowered to a series of ffmpeg invocations, which produce the intended media artifact deterministically.
I got interested in this originally when I was younger and made Call of Duty montages on YouTube. I made compilations and whatnot and found it tedious to do some of the "structural" work I suppose (like making a 2x2 layout, other effects). I had saved project files to help me make similar style content over time, but found myself wanting more control. Around then sometime I stumbled into ffmpeg and got into media production and automation as a hobby.
I later designed a string DSL for layout, answering roughly how could I represent any arbitrary set of rectangles in an arbitrary canvas in one blob? This led to the m0 DSL. If interested, below link has some of my original derivation records https://m0saic.io/go/hn-substack Or if you just want to see a quick visual example, here is a somewhat complex example (a github commit graph geometry) that shows the idea: https://m0saic.io/go/hn-layout-year
Anyways, that layout language is the base, and I've built a template based media program on top. There's a CLI, Web Editor, and Desktop Editor. No external dependencies other than ffmpeg and resvg for the CLI. Templates are specific media programs that define input props and produce the IR the compiler can turn into pixels.
I've been exploring different verticals for usecases (more on site). I believe headless automation and CI do well with this workflow. Templates are low-cost once written, and can encode specific media operations into essentially a deterministic func from props to pixels. I have not set out to create an agentic video editing platform, though the compiler framing of this project I've found to play really well with LLMs. I've been able to have reproducible, debuggable and structured working sessions as opposed to a one shot result. Read more here: https://m0saic.io/agent
Some of what I think makes this different: - Layout is a small string algebra and it is closed under composition. There is only integer arithmetic, so the same string resolves to the same rects on any machine and any language that implements the grammar. - This compact "blob" form is suitable for travel across contexts, and can inherently be interpreted the same across them. - Templates improve through composition - once good primitives exist, higher level templates can compose them into more complex results. - Can be installed headless on a Linux worker, or a rich visual editing experience exists for developer/end user in the desktop Electron app. Underlying render functionality of templates remains the same, different audience.
The product has open source components - I've open sourced everything except for the compiler itself and the web/desktop app. Website has links to npm and GitHub.
Thank you for reading - I'd love feedback and thoughts!