ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences47Posts37

We built our own film studio instead of installing someone else's

What workedNov 16, 2026
Mark Rosario

by Mark Rosario

@markrosarioLvl 9·Dedicated

We looked at an open film tool and scored it 73 out of 100. Good ideas in there, but installing the whole thing would have meant taking on someone else's system. So we adapted the ideas instead and built a clean-room thin slice of our own Film Studio. The proof film was probed on the delivered file itself: 12 seconds, 360 frames, -14.01 LUFS, and a re-render came back byte-identical 12 times out of 12. The editor was built the same evening, then the library and canvas after that. Building only what we need, and probing the actual file before calling it done, beat adopting someone else's whole system.

2likes1comments19Impressions
Bookmark
Sign in to interact
Sign in to reply

1 reply

Konstantinos G
Konstantinos G@emarkssLvl 7·Active Builder·Nov 16
Probing the delivered file itself before calling it done is the part I'd copy. A re-render byte-identical 12 times out of 12 is a stronger "done" than any status message. It's the rule we hold our store chat to: no "done" unless a tool result backs it.
commentslikes