Started as “PhotoMind for videos” and grew into a local-first AI rough-cut assistant. Point it at a folder of clips: every shot is described and scored on your Mac, the whole library becomes searchable by meaning, and a typed idea becomes an editable cut — beat-synced and ready for DaVinci Resolve.
Recorded on a real library of 507 clips and 1,863 shots; the footage shown is from trips in northern Pakistan.
A four-minute walkthrough made for testers: first scan, searching in plain words, cutting by hand and to the beat, the AI Director, interview reels with B-roll, and opening the result in DaVinci Resolve.
A single trip can leave hundreds of clips behind — drone, action-cam, phone. Finding the right ten seconds means scrubbing through every file, so most of it never gets edited. File names say nothing, and no folder structure survives contact with a real shoot.
Manzar breaks every video into shots and describes each one with an on-device vision model — what's in frame, tags, shot type, steadiness and exposure, a suggested use and a hook idea — with exact timecodes. Every clip is scored for Reels and long-form. The library becomes searchable by meaning, with “more like this” on any shot. The AI Director turns a typed brief into an ordered cut, explaining why each clip is there; it hands Claude only the text descriptions and timecodes, never the video. Add a music track and the cut is trimmed to the beat; one click exports a non-destructive DaVinci Resolve project.
| Backend | Python — Click CLI + FastAPI, SQLite (WAL, FTS5) |
| On-device AI | mlx-vlm (Qwen2-VL), open_clip, librosa |
| Cloud step | Claude API, text only, for the AI Director |
| Media | ffmpeg / ffprobe with VideoToolbox hardware decoding, exiftool |
| Frontend | Vite + React |
Actively developed and in use on a real library of over 500 clips — well past its original three-phase roadmap.
If your archive is growing faster than anyone can watch it, there's a way to make it searchable — and keep it private.