A real-world Kimi K3 test: rebuilding a 36-second launch film as editable code
 |
Benchmarks tell me very little about whether a model can stay useful through a visual production loop, so I tested Kimi K3 on a 36-second reference-led launch film. This was not a one-prompt video generation. K3 used ffmpeg to inspect the source, extracted frames, detected edit points, and helped reconstruct the sequence as editable code-driven clips. GSAP carried the temporal system, generated images became material textures, and Three.js produced the particle simulations. The first pass was structurally useful but visually incomplete. The final result came from repeated matched-frame review: retiming clips, correcting framing and scale, replacing flat materials, and tuning particle density without discarding the underlying code. My main takeaway is that K3 was more convincing as a revision partner than as a one-shot generator. It retained enough project context to keep the sequence coherent, while human direction still defined visual hierarchy and when each shot was finished. When you evaluate a new frontier model, do you learn more from the first output or from how it behaves after the fifth revision? submitted by /u/Tight-Switch819 |
