Skip to main content

Snapper 🐟

snapper-logo pre-commit.ci status Code style: black

Note

Currently only Resolve 18 is supported. Resolve 17 and older require Python 3.6, which is now EOL. Some dependencies have started dropping support for it. If you use Resolve 17, checkout the 'resolve-17' branch. You can fork that branch and any incompatible dependencies if you're feeling brave. Although new features will not be ported, pull requests are welcome. The Resolve 17 branch has not been tested with older versions of Resolve.

Purpose

Sometimes you want to try out some risky idea, create a couple of variations of something to compare, or even just have some timeline backups within easy reach when your project take some big steps. Snapper helps automate that. It's all too easy to throw 'best practice' out the window when you're on a tight turn-around. Snapper is really just a quick and easy utility to help you version your timelines. Snapshots sound cool, but really they're just timelines with a simple version number appended:

My timeline V1, My timeline V2, My timeline V3, etc.

Usage

Simply run snapper new to create a new snapshot of the active timeline. You can run this command with a shell-script, batch-file, StreamDeck, desktop shortcut, whatever you like.

When you create a new snapshot, Snapper duplicates your active timeline, renames it as the newest version, and puts it in a subfolder called '@Snapshots' next to your working timeline. If you keep all of your timelines in one place they'll all share the same subfolder, but if you like to keep unrelated timelines in separate folders, they'll each get their own '@Snapshots' subfolder. This helps prevent one person locking all the timelines if they park on the subfolder in collaborative mode.

If you still like seeing all your timeline versions in one place, you can enable the timelines smart bin in Resolve's settings - best of both worlds.

What it doesn't do

Creating snapshots was always a point of friction for me and others I work with. That's why I made Snapper. That being said there are things I specifically don't want it to do. I want them to stay points of friction:

Deleting snapshots - That's dangerous territory, and better left as a manual process. Just keep them - unless you work with huge timelines, they don't really bloat your projects

Reverting snapshots - More often than not you'll want to do a partial revert, and there's no way of knowing how much you'd like to revert. It makes more sense to use the very granular tools Resolve provides you to pick and choose what you want to. Plus, if we're to avoid deleting all versions upstream of a revert, we leave behind a messy, jump-around history.

Installation

First make sure you have:

  • Python 3.10 - install with pyenv and pipx if you want to keep things tidy
  • DaVinci Resolve Studio, with scripting set up (read Resolve's scripting README)

Then run:

pipx install git+https://github.com/in03/snapper

 ___ ___ ___ ___ ___ ___ ___
|_ -|   | .'| . | . | -_|  _|
|___|_|_|__,|  _|  _|___|_|
            |_| |_|

Create and manage DaVinci Resolve timeline revisions 🐟

Usage: snapper [OPTIONS] COMMAND [ARGS]...

  Do yourself a favour and create frequent timeline snapshots. Don't leave
  messy little experiments at the end of your timelines. Keep it tidy. Keep it
  clean.

  Just type: "snapper new"

Options:
  --verbose / --no-verbose        Log debug messages  [default: no-verbose]
  --install-completion [bash|zsh|fish|powershell|pwsh]
                                  Install completion for the specified shell.
  --show-completion [bash|zsh|fish|powershell|pwsh]
                                  Show completion for the specified shell, to
                                  copy it or customize the installation.
  --help                          Show this message and exit.

Commands:
  new  Create a new timeline snapshot

How can I contribute?

Clone the repo, install dependencies, call from poetry shell:

git clone https://github.com/in03/snapper
cd snapper
python3 -m pip install poetry
python3 -m poetry shell
poetry install
snapper --help

If you're unfamiliar with using Poetry for dependency management and packaging, give it a look.

Metadata

Release files for dr-snapper 0.3.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dr-snapper 0.3.5
File Size Uploaded
dr_snapper-0.3.5.tar.gz 7.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dr-snapper 0.3.5
File Interpreter ABI Platform
dr_snapper-0.3.5-py3-none-any.whl Python 3 none any Details

Total release size: 15.6 kB

Release files / dr_snapper-0.3.5.tar.gz

Download URL dr_snapper-0.3.5.tar.gz
Size 7.4 kB
Tags Source
SHA-256 checksum
How to use checksums
c5cc2ccbfff85044e129e0e1bdb4a89da0cc5dd4cfca6caecd9f4bf89ee7b1fd
BLAKE2b-256 checksum
How to use checksums
cd084f290348369b9ae1eac49d18b5fd7d544d2ea526edc22b72e657b9c23b74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.4.2 CPython/3.11.3 Darwin/22.4.0

Release files / dr_snapper-0.3.5-py3-none-any.whl

Download URL dr_snapper-0.3.5-py3-none-any.whl
Size 8.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
11f8b0bbcb7a1bc9245a5660f250b8864ebb047d0282b46b11ecdac4d727f6a7
BLAKE2b-256 checksum
How to use checksums
fbbdf5725c5e40fece165e8865f9b19f77f3e9b59bf9a9759f8c4ebf79bae400
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.4.2 CPython/3.11.3 Darwin/22.4.0

Release history Release notifications | RSS feed

This release

0.3.5 This release

2 release files

0.3.3

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page