Skip to main content

Create a new timeline 'snapshot' to revert to when trying out risky ideas in DaVinci Resolve

Project description

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.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

dr_snapper-0.3.3.post1.tar.gz (7.4 kB view details)

Uploaded Source

Built Distribution

dr_snapper-0.3.3.post1-py3-none-any.whl (8.3 kB view details)

Uploaded Python 3

File details

Details for the file dr_snapper-0.3.3.post1.tar.gz.

File metadata

  • Download URL: dr_snapper-0.3.3.post1.tar.gz
  • Upload date:
  • Size: 7.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.4.2 CPython/3.11.3 Darwin/22.4.0

File hashes

Hashes for dr_snapper-0.3.3.post1.tar.gz
Algorithm Hash digest
SHA256 61c32f62f1965b571ef6bb744b14103df7d647e1372ea107733c9fbcca0f32b5
MD5 eaa007465a772a32c0e90488f1bc1685
BLAKE2b-256 ffe79ba0ca55cf9f4c3bc6e3ff30561e6f1b748ae66b1b5813b7080f7c71e76a

See more details on using hashes here.

File details

Details for the file dr_snapper-0.3.3.post1-py3-none-any.whl.

File metadata

File hashes

Hashes for dr_snapper-0.3.3.post1-py3-none-any.whl
Algorithm Hash digest
SHA256 7cdd3962fd42156a5501d2b5e8626304dd892429c7a13a527c53aefdb2656e36
MD5 f0716c6feda04448c033267a140b833a
BLAKE2b-256 8584d37adcb6fbb9a660f1c897cae12dab140c71e511cdfb4cda3baa748a8993

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page