vit | Devpost

~vit
~vit commit
~vit visualize
~vit merge

📦 Product Summary

Vit is a version control system for DaVinci Resolve, built on Git. It lets video teams collaborate in parallel the same way developers do with code.

Instead of versioning large video files, Vit serializes timeline decisions into domain-split JSON files: clip placements, color grades, audio levels, and markers. Each role owns a different file, so Git merges happen without conflicts. A full PySide6 panel inside Resolve gives teams save, branch, switch, merge, push, and pull, all without leaving the editor.

When conflicts do occur, a post-merge validator catches orphaned references and calls Gemini to propose a semantic resolution before anything is committed. A natural language chat agent in the same panel lets collaborators type commands in plain English, with Gemini handling intent parsing, parameter extraction, and confirmation before executing.

The full history of every creative decision is preserved, auditable, and reversible. Teams share projects through a standard GitHub repository with no new accounts, no new infrastructure, and no learning curve.

🎉 Inspiration

Professional video production is collaborative by nature, but the tools are not. Editors, colorists, and sound designers work sequentially; one person finishes and hands off to the next. Software developers solved this inefficient workflow 30 years ago with Git: branches, merges, and version history. Video editors have none of it.

Vit changes that. We built Git for video editing.

🤯 What it does

Vit versions the edit decisions, not the video files.

A timeline is just structured data: clip placements, color grades, audio levels, and markers as structured JSON, then version those changes with Git.

This allows video teams to collaborate using branches, merges, and version history, just like developers do with code.

💭 How it works

Example workflow:

Editor opens Resolve, builds a rough cut, and clicks Save Version in the Vit panel
Colorist opens the same project, creates a color-grade branch, grades the footage, and saves their version
Sound designer creates a sound-design branch, adds music and SFX, and saves their version
Editor clicks Merge Branch twice, combining all three workstreams in seconds

It works because each role edits a different file:

Editor → cuts.json
Colorist → color.json
Sound designer → audio.json

Git merges these files automatically without conflicts.

AI conflict resolution

When a real conflict occurs — for example, an editor deletes a clip that a colorist already graded — Vit’s post-merge validator catches the orphaned reference and calls the Gemini AI model.

Gemini: