Skip to archive
Abhay Rohit
Back to archiveSelected study / 05

Reel OS

Find the story in the footage.

My role

Builder and editorial owner of a personal media-production system.

Project status

Private local workflow · editor interface prototype.

Concept poster for Reel OS. A burgundy film ribbon curls through a dark scene beside a blue reel wheel and translucent frames. The headline reads “From footage to finished.” It identifies a working local media workflow. The film objects are metaphorical artwork, not an editor screenshot or tool-produced footage.
Original conceptual campaign artwork · October 2026. A visual metaphor for this study; project evidence follows below.
01 / Context

The idea behind the work.

Reel OS turns the edit into something inspectable. Original footage is indexed, selected moments carry exact timecodes, and the editorial plan stays connected to the rendered master. The system produces editable timelines, proof sheets and technical QA so a later session can understand how the cut was made. A supervised phone-to-Mac route uses private Drive for source intake and review delivery. The important product choice is the separation of states: a technically sound render can still need a human verdict, and a published post’s performance must be measured in its own window. That gives the creative process durable records without pretending that a codec check proves a good film.

02 / Engineering & design

What I chose.
And why.

A good short-form edit depends on decisions about source identity, exact moments, pacing, typography and sound. Repeated chat-only editing loses those decisions and makes it difficult to explain or reproduce a result.

  1. Keep original footage, source inventories and timestamped moment evidence connected to schema-validated edit plans.

  2. Generate editable OTIO/EDL timelines and deterministic FFmpeg masters with plan-bound preflight and QA.

  3. Keep technical delivery, normal-speed human review and platform performance as separate records.

03 / Supporting media

Closer to the source.

Dates and capture context are preserved with the media.

A historical Reel OS contact sheet showing nine timecoded frames from Abhay’s local boxing draft with sparse on-screen text. It is review output, not an editor UI or human publication approval.
Supporting image: historical local boxing review contact sheet; capture date unspecified.Nine timecoded views of a local boxing review draft. The sheet supports visual review of selected frames; it does not establish normal-speed pacing, sound, a final delivery date or publication approval.
04 / Evidence

What the work shows.

The repository documents a resumable pipeline, shared typography, checksum-bound QA and supervised private Drive intake/delivery. A dated eight-source cycle verified upload, cloud playback and checksum-identical return. The historical contact sheet shows an actual local rendered draft. No automatic analytics connection or performance lift is claimed.

05 / Boundaries

Where I keep the distinction.

Technical QA checks the media file; it cannot decide whether the edit tells the right story. Human review stays part of every delivery. The BMW reel predates this workflow and is not presented as a Reel OS result. The editor interface shown on the homepage is a prototype.

Contact Me

Abhay Rohit — portfolio index