I learned DaVinci Resolve in two days because I wanted to edit the videos for my own product. I build InputLag, a Windows optimizer for gamers, and make videos about the settings behind it.
The useful discovery: Resolve has a Python scripting API. A script can create a timeline and place clips on tracks. I write those scripts together with an AI assistant, so a layered edit gets assembled from code, then open it in Resolve for the hands-on work.
Code builds the timeline
For my Valorant video about Network Buffering and Interrupt Moderation, the timeline is assembled in layers. The footage, graphics and audio can stay on separate tracks, so I can work on one part of the edit without flattening the whole thing into a single clip.
The GIF below is an insert from that video.
I still edit it by hand
Once the clips are on the timeline, I watch the sequence and make changes in Resolve. A cut can be in the planned position and still feel late. A graphic can be readable and still stay on screen too long.
The script handles assembly. I handle the decisions that need watching and listening. Having the layers available makes those revisions practical.
I'm also working on a big InputLag update: a new design, metrics and more tweaks. Making the videos myself has become another part of building the product.
