A team of University of Waterloo engineering students (Justin Wu, Lucas Jin, Owen Li, Thomas Lenh) has released Vit, a free, open-source tool that brings Git-style version control (GitHub, if you’re more familiar with it) to video editing. Instead of passing project files back and forth on hard drives or waiting for one editor to finish before the next can start, Vit lets editors, colourists, and sound designers work on the same timeline in parallel using branches, then merge their changes together at the end, just like software developers do with code.

we just built git for video editing. pic.twitter.com/ldSvzDkATE

— Lucas Jin (@lucashjin) March 25, 2026

What Vit Actually Does

Vit works by serialising your DaVinci Resolve timeline into lightweight JSON metadata files. It does not version your raw footage or media. Instead, it tracks the creative decisions: clip placements, colour grades, audio levels, effects, transitions, and markers. Git handles all the versioning under the hood, and your team shares changes through a standard GitHub repository, so there is no new infrastructure or accounts required.

The clever part is how Vit splits the timeline data across domain-specific files. Each role on a production team owns a different file, which means Git can merge them without conflicts in most cases.

Domain File Breakdown

Because different people edit different files, parallel work rarely creates merge conflicts. When cross-domain issues do arise, such as one branch deleting a clip while another colour-grades it, Vit includes an AI-powered semantic merge system that analyses the conflict and proposes a resolution.

The Problem Vit Solves

Professional video production has long been a sequential process. The editor finishes a cut, hands it off to the colourist, who finishes and hands it off to the sound designer. Everyone waits their turn. As Vit creator put it on X, “video editing is very sequential” and new AI video editing tools do not solve this because they do not integrate with pre-existing software.

Software developers solved this exact workflow bottleneck decades ago with Git and GitHub. Video editors, until now, had no equivalent. The only comparable tools on the market have been enterprise-grade solutions costing thousands per month, as one Product Hunt commenter noted. Vit is free, open-source under the MIT licence, and built entirely on top of Git and GitHub, so teams can start using it with tools they likely already have.

Read More: Nintendo Issues DMCA Notices To Switch Emulators On GitHub In Latest Crackdown

Read More: Nintendo Tells Robbed Pokemon Card Store To Change Name As The Trainer Court

How To Set Up Vit: Step-By-Step Tutorial

Vit requires Python 3.8 or later, Git, and optionally DaVinci Resolve for the in-editor integration. Here is how to get everything running from scratch.

Installing Vit

On macOS or Linux, a one-line install handles everything:

curl -fsSL https://raw.githubusercontent.com/LucasHJin/vit/main/install.sh | bash

Alternatively, you can install manually by cloning the GitHub repo and running pip install. If you want the optional Qt-based GUI panel inside Resolve, install with the qt extra using pip install ".[qt]". After installation, run vit install-resolve to symlink the plugin scripts into DaVinci Resolve.

Starting A New Project (Lead Editor)

Before anything else, create an empty GitHub repository with no README or licence file. This repo is how your team shares timeline changes. Your footage needs to be shared separately through whatever method your team already uses, whether that is a shared drive, Dropbox, or a local server. Vit only tracks edit decisions, not raw video.

In your terminal, initialise the project and connect it to your GitHub remote:

vit init my-project

cd my-project

vit collab setup

When prompted, paste your empty repo URL. Then open DaVinci Resolve, load your project and timeline, and open the Vit Panel from Workspace, then Scripts, then Vit Panel. Hit Save Version to create the first snapshot. Vit serialises the timeline to JSON and commits it. Send the clone URL that your terminal prints to your collaborators.

Joining An Existing Project (Collaborators)

Collaborators clone the project from GitHub using the URL provided by the lead editor:

vit clone https://github.com/yourname/your-repo.git

cd your-repo

vit checkout main

Open Resolve, run the Vit Panel, choose Switch Branch, select your footage folder, and relink any offline clips. Then create your own branch with vit branch your-name. From this point forward, everything happens inside the panel.

The Daily Workflow

Once the project is set up, the day-to-day workflow happens entirely within the DaVinci Resolve panel. Pull to fetch the latest changes from the team. Switch Branch to restore the timeline to your branch. Edit in Resolve as you normally would. When you are ready, hit Save Version to serialise and commit your changes, then Push to share your work with the team.

Merging Work Together

When it is time to combine everyone’s work, the lead editor pulls all the latest commits, switches to the main branch, and uses the Merge function in the panel to select which branch to bring in. The panel shows a diff summary and, if a Gemini API key is configured, uses AI to recommend a merge strategy. For complex cross-domain conflicts, Vit offers a full AI-assisted resolution flow through the CLI using vit merge <branch>.

AI-Powered Features Under The Hood

Vit uses the Gemini API to handle tasks that go beyond what plain Git can manage. The standout feature is semantic merge resolution. When a merge creates cross-domain conflicts, the AI analyses the base, ours, and theirs states across all domain files and produces structured per-domain decisions with confidence levels. For ambiguous merges where the AI is not confident, it presents options to the user before committing anything.

Beyond merging, Vit can auto-generate descriptive commit messages from the timeline diff using video editing terminology, produce natural-language summaries of recent commit history for the team, and auto-categorise commits as audio, video, or colour changes. All AI features are optional and degrade gracefully. Vit works fully without a Gemini API key; you just lose the smart merge and suggestion capabilities.

Early Reception And What Comes Next

The project has already gained significant traction since launching. Lucas Jin’s announcement on X has pulled in over two million views, and the tool has attracted 171 followers on Product Hunt. Owen Li described the team’s motivation simply: professional video production is broken because editors, colourists, and sound designers work sequentially, and software developers solved this thirty years ago with Git while video editors had nothing.

The team is not currently accepting external pull requests, but the project is MIT-licensed and available on GitHub for anyone to fork and build on independently. For production teams looking to move away from sequential editing workflows, Vit offers a genuinely practical solution that slots directly into DaVinci Resolve without requiring expensive subscriptions or new infrastructure beyond a free GitHub account.

The post Vit is GitHub for Video Editors, and It Finally Makes Collaborative Video Editing Work appeared first on Shane the Gamer.

Nintendo has issued a fresh wave of DMCA takedown notices targeting Nintendo Switch emulators hosted on GitHub, continuing its long-running crackdown on Switch emulation.

Multiple projects, including Eden, Citron, Kenji-NX, MelonNX, Skyline, Sudachi, Suyu and others, have reportedly received notices via GitHub’s Trust & Safety team. While some repositories remain visible at the time of writing, developers were given a short deadline to respond before facing potential disablement.

The move follows earlier legal action against major Switch emulators and signals that Nintendo’s enforcement campaign is far from over.

Multiple Switch Emulator Repositories Hit With DMCA Notices

As first highlighted by PC Gamer and shared across Reddit, a number of Nintendo Switch emulator repositories on GitHub were notified that they had been targeted under the Digital Millennium Copyright Act.

GitHub’s message reportedly stated it is “never our desire or goal to take down open-source projects”, but explained that it must act when presented with valid DMCA claims. Developers were given one business day to respond before repositories risk being disabled.

Among the affected projects are forks and successors to earlier Switch emulators. Some, like Skyline and Sudachi, are no longer actively developed, yet were still included in the sweep.

According to reports, even projects that are inactive or forks of previous emulators did not escape attention, suggesting this was a broad action rather than a targeted strike at a single team.

Eden Developer Says “Nothing Major” But Releases Moving Off GitHub

An Eden developer known as maufeat addressed the situation on the project’s Discord server, confirming their release repository received a notice.

“It is true, but nothing major,” maufeat wrote. “Our release repo got the notice so you will probably have to download future releases and nightlies directly from us.”

They added that many affected projects are forks and said it was “just a matter of time” before GitHub-hosted versions were targeted. The developer also explained that this is precisely why some emulator teams avoid hosting their source code on GitHub in the first place.

Self-hosted repositories, including official project websites for Eden and Citron, appear to remain online for now.

Community Reaction: “They Can Never Kill Emulation”

The news quickly spread across Reddit and emulator Discord communities, where frustration was clear.

One widely shared comment read, “If they kill one, 10 more will pop up. Kill 10, 100 more will pop up. They can never kill emulation.” Another user advised, “It’s never a bad time to back up your favourite emulators.”

While those reactions reflect community sentiment, the legal reality is more complicated. Emulation itself is not automatically illegal under US case law. However, when it intersects with bypassing technological protection measures or facilitating piracy, companies like Nintendo have aggressively pursued action.

In previous filings, Nintendo argued that certain emulators enabled widespread piracy, including early downloads of The Legend of Zelda: Tears of the Kingdom prior to its official release.

This Follows Major Legal Action Against Yuzu And Ryujinx

This latest round of DMCA notices comes after a turbulent period for Switch emulation in 2024.

Nintendo sued the creators of Yuzu, one of the first major Nintendo Switch emulators. The case ended in a reported US$2.4 million settlement. Shortly after, Ryujinx was discontinued after its creators were reportedly offered an agreement to stop working on the project.

Discord servers for related emulator projects such as Suyu and Sudachi were also taken offline during that period.

In response, new forks like Citron and Eden emerged. The current GitHub notices suggest Nintendo is now addressing those successors directly.

Nintendo’s Broader Position On Emulation And Piracy

Nintendo has consistently taken a strict stance on emulation and piracy, particularly when it involves current-generation hardware like the Nintendo Switch.

The company has previously revised its account agreements and privacy policies to tighten rules around emulation and unauthorised use. It has also banned users from online services for using flash cartridges capable of storing pirated game files.

A key part of Nintendo’s legal argument in past cases has centred on technological protection measures, including encryption keys used to decrypt Switch games. Even if those keys are not bundled directly with emulator code, Nintendo has argued that circumvention tools enable infringement.

While the removal of repositories from GitHub does not erase emulator development entirely, it can make projects harder to discover and distribute.

For now, it appears the battle between Nintendo and Switch emulation developers is entering yet another phase. Whether this wave of DMCA notices significantly slows development or simply pushes projects further underground remains to be seen.

The post Nintendo Issues DMCA Notices To Switch Emulators On GitHub In Latest Crackdown appeared first on Shane the Gamer.