Proxy Factory
Auto-generate proxies the moment footage lands
Choppy playback, laggy scrubbing, and unusable timelines — even on strong machines — often comes down to editing long-GOP or heavy codecs at high resolution without proxies. This recipe generates proxies automatically whenever new camera originals appear, so every project starts edit-ready instead of debug-ready.
INGREDIENTS
PROMPT
Create a skill called "Proxy Factory". Configure: - originals_path - proxies_path - proxy_resolution (default 1920x1080) - proxy_codec (prores_proxy | dnxhr_lb | h264_proxy) - max_parallel_jobs - manifest_path When new media appears, generate proxies, save a manifest mapping originals→proxies, and send me a one-screen set of attach instructions for my editor (Premiere Pro / DaVinci Resolve / Final Cut Pro).
How It Works
This skill watches your camera originals folder, generates proxies with a consistent
naming convention, mirrors the folder structure, and writes a manifest mapping originals
to proxies. You get a notification with editor-specific instructions for attaching proxies.
What You Get
- Automatic proxy generation triggered by new media or on demand
- Consistent naming convention (e.g., `A001_C001_0101AB_PROXY_1080p.mov`)
- Mirrored folder structure in your proxies directory
- Proxy manifest (CSV/JSON) mapping every original to its proxy
- Editor-specific attach instructions for Premiere Pro, DaVinci Resolve, and Final Cut Pro
Setup Steps
- Point to your camera originals folder and choose a proxies destination
- Set resolution (default 1920x1080) and codec (ProRes Proxy, DNxHR LB, or H.264)
- Configure max parallel jobs based on your machine
- Run as a watch folder, hourly scan, or on-demand command
Tips
- ProRes Proxy gives the smoothest NLE playback; H.264 saves the most space
- Keep the manifest updated — it makes relinking and archiving predictable
- Set max parallel jobs to 2 on laptops to avoid thermal throttling
- Pair with VFR Gatekeeper to transcode VFR footage before proxy generation