copy-larp
A pipeline that takes a reference reel and a folder of my own footage and returns a finished, postable edit.
Working on my Mac. Used on three projects so far: one hike reel and two match reels.
67 editing rules, each written from a note I gave on a real cut
- Where
- Personal project
- Role
- Design and build
- Built with
- Python, ffmpeg, Whisper, Apple Vision, Gemini for a second QC view
What I made
It started as hand-written build scripts for one reel: a hike in thrifted suits, edited five times in one day in September. I turned those scripts into an engine with five steps.
The core of it is the rules file. Every time I reject a cut, my reaction goes into the project notes in my own words, then becomes a dated rule the next edit reads first.
- refshots, pacing, text, song and look of the reference
- intakecatalogs the footage and transcribes every clip
- musictempo, beats, sections and bar-aligned cut points
- renderstabilised, graded, captions behind the subject
- qcloudness, frames at every cut, a second model's watch
What came out of it
The hike reel
Five versions in a day, from a 15-second clip to a 46-second cut with the song spliced across two verses. The rebuilt engine was later checked frame by frame against versions 4 and 5.
Match reels
The same engine cuts highlight reels for my team from an auto-tracking camera's recording of a full game, with a review page where I keep or drop each moment first.
Where it's going
The complete version gets a new reel to a postable cut in one or two rounds, because the rules file already carries every note from the reels before it.
- NowFive rounds a reelThe hike reel took five versions in one day.
- Rules in the engineMechanical notes are enforced by the engine or the QC step.
- One or two roundsA new reel reaches a postable cut in one or two.