kiendt91/video-mix-with-codex

This project is a workflow for editing music videos on a Windows machine, combining several pieces of software. The author uses Codex (an AI coding assistant), FFmpeg (a command-line tool for cutting and converting video), and HyperFrames (another command-line tool that turns an edit description into a rendered video). The repository is mostly a collection of PowerShell scripts and example files that glue these pieces together. The README explains the philosophy first. Instead of picking video timestamps at random, the author wants the editor to listen to the song, look at every clip of footage, decide what each shot is for, then render and check the result before delivering it. It supports two edit styles. A beat-cut music video where cuts land on the beats of the music, and a cinematic story music video where dialogue and character shots tell a small story over the song. The core process is described in six stages: prepare the media files, inspect each source clip for things like episode cards or hard subtitles, build contact sheets that show frames from each clip, plan the story or the song timing, mark which audio belongs to which moment, then generate, render, and run a quality check. An edit decision list, written in JSON, drives all of this. The scripts validate the list, build a HyperFrames project from it, render the final MP4, and run automated checks for black frames or accidental subtitles. To run the workflow you need Windows PowerShell, FFmpeg and FFprobe on your PATH, Node.js 22 or newer, and the HyperFrames command-line tool. There is also a local web interface called the Studio UI. Running npm run studio opens a browser page at a local address where you can paste paths to your music, source videos, and an output folder, then trigger each step in the pipeline from buttons rather than the command line. The Studio UI optionally talks to AI providers like OpenAI, Anthropic, Gemini, or xAI to draft, repair, or review the edit decision list. API keys are stored outside the repository in an APPDATA folder, and the actual rendering stays local with FFmpeg and HyperFrames. The README provides two quick-start sequences, one for each edit style, and a faster pipeline script for repeat jobs that caches normalized clips so re-renders skip unchanged shots.