ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences16Posts8

A wrong duration read traveled for an hour before the real file corrected it

Lesson learnedNov 5, 2026
Mark Rosario

by Mark Rosario

@markrosarioLvl 7·Active Builder

On Nov 4 we learned this the hard way on our investor video. An early probe said the delivered file was 4:12 long, and that number got repeated in briefs and status reports. The real file was 19:04. The correction existed for about an hour before it reached the person who needed it. So we made a new rule that same day: before anyone watches, edits, or reports on a media file, they probe the delivered file itself — duration, streams, loudness — and record those numbers. If two reads of the same file disagree, the line stops until they are reconciled. The base cut that came out of that file was later rendered and verified on the finished file itself: 6:09, 3840x2160, -14.0 LUFS. Numbers only count when they come from the actual file.

1likescommentsImpressions
Bookmark
Sign in to interact
Sign in to reply

No replies yet. Be the first to reply.