Proxymity application icon

Build verified editing proxies inside DaVinci Resolve Studio.

Select Media Pool clips, review audio routing, choose output folder and profile, and generate locally from Workspace > Scripts > Proxymity.

BetaVersion 0.9.2 beta · macOS 12 or later · Apple Silicon tested · Windows 10 or 11 (beta, not yet tested on a physical PC by the author) · DaVinci Resolve Studio 21 or higher

Download

Or paste this into Terminal

curl -fsSL https://proxymity.moo.llc/get.sh | bash
Proxymity main window in DaVinci Resolve with clip selection, audio routing and profile controls

Features

Inside Resolve

Works in DaVinci Resolve Studio 21 or higher from Workspace > Scripts > Proxymity.

Profiles and settings

Named profiles and saved settings; quarter, half, and full size; filename and timecode burn-ins.

Progress and QA

Progress and ETA, cancel, resume, retry, QA reports and logs.

Audio

Keeps the original embedded audio channel count while baking boom, lav, and camera mapping into separate PCM channels.

Picture

Outputs keep exact source frame rate and timecode, H.264 all-I with no B-frames.

Frame rates

23.976, 24, 25, 29.97, 30, 50, 59.94 and 60 fps, with drop-frame timecode kept where it applies.

Data Burn-In

Burn-in styles (classic strip, dailies, minimal, Resolve look) and a choice of fields: source name, timecode, frame number, frame rate, resolution, and custom text. After each encode, a check reads the burned text at three sample frames.

ProRes on Mac

Optional Apple ProRes encoder on a Mac that has it.

Make reel

Join ticked clips into one dailies file with chapters, CSV and EDL.

Auto-link

Optional auto-link of proxies in Resolve (opt-in, off by default).

RED R3D

RED R3D decode through REDline that you install yourself; Proxymity does not redistribute REDline.

Saved lists

Saved lists for repeatable clip sets and batch workflows.

Local encoding

Runs locally with no per-frame model calls.

Editorial tools

Editorial command-line tools: index, search, stringout, view, audio, lint, diff, music-cut.

Screens

Close-up of the Proxymity audio routing panel with output channels 1 and 2 assigned to Cam 1 and Cam 2
Audio routing close-up: each output channel gets a source, with a waveform to check it.
Proxymity Saved lists dialog
Saved lists dialog for named clip sets.

Requirements

  • DaVinci Resolve Studio 21 or higher. The free version of DaVinci Resolve is not supported: Proxymity needs the external scripting that only Studio has.
  • A Mac with macOS 12 or later. The app is a universal build (Apple Silicon and Intel), but it has only been tested on Apple Silicon with one current macOS. Intel Macs are untested.
  • Windows (beta): 64-bit Windows 10 or 11, DaVinci Resolve Studio 21 or later, Python 3.11 or later, and ffmpeg with the libx264 encoder. Details in the Windows (beta) section.
  • Python 3.11 or later.
  • ffmpeg with the libx264 encoder, for example via Homebrew: brew install ffmpeg.
  • Optional: REDline from RED's REDCINE-X PRO for fast R3D decode (you install it; Proxymity does not ship it).
  • The installer creates a Python virtual environment and installs packages from requirements.txt for you.

Download

Proxymity 0.9.2 beta for macOS 12 or later (Apple Silicon tested, Intel untested). Needs DaVinci Resolve Studio. A first Windows beta is also available: see Windows (beta).

File: Proxymity-0.9.2-macOS.zip

Windows (beta)

A first Windows build: version 0.9.2 beta, for 64-bit Windows 10 or 11. Open PowerShell and paste this line:

irm https://proxymity.moo.llc/get.ps1 | iex

Requirements:

  • 64-bit Windows 10 or 11.
  • DaVinci Resolve Studio 21 or later.
  • Python 3.11 or later.
  • ffmpeg with the libx264 encoder.

Beta: not yet tested on a physical PC by the author. The download is not signed, so Windows SmartScreen may warn when you run it.

Install

Recommended: run the one-liner in Terminal (downloads and runs the installer):

curl -fsSL https://proxymity.moo.llc/get.sh | bash

Manual route:

  1. Download Proxymity-0.9.2-macOS.zip and unzip it.
  2. Open the folder and double-click Install Proxymity.command, or run bash install.sh from that folder in Terminal.
  3. The first time after download, right-click Install Proxymity.command and choose Open, because the app is not signed by Apple and macOS may otherwise refuse to open it.
  4. When install finishes, open DaVinci Resolve, then Workspace > Scripts > Proxymity.

Limits

  • Generation is verified. Playback of linked proxies is verified only for linked-recorder clips.
  • DaVinci Resolve Studio is required. The free version is not supported.
  • Camera-raw formats (Blackmagic RAW, ARRIRAW, Canon RAW, ProRes RAW) are not supported. Those clips are skipped, and the run says so.
  • Frame rates outside the supported list are skipped, including 48 fps and 120 fps. Variable-frame-rate phone footage and R3D at 25 and 30 fps are untested.
  • R3D decode needs REDline from REDCINE-X PRO, which you install yourself.
  • No encoder speedup is claimed.
  • The burn-in check reads the burned text at three sample frames, so it cannot prove every frame. A similar-looking digit can pass it.
  • Clips that were already proxied keep their old burn-in when they are joined into a reel.
  • Windows is a first beta for 64-bit Windows 10 or 11. It has not yet been tested on a physical PC by the author.
  • macOS 12 or later. Universal app, tested on Apple Silicon only with one current macOS. Intel Macs are untested. The download is not signed by Apple.

FAQ

What is Proxymity?

Proxymity is a proxy builder for DaVinci Resolve Studio on macOS. You run it from Workspace > Scripts > Proxymity, select Media Pool clips, and generate H.264 editing proxies with controlled audio routing and burn-ins.

What does it cost?

Free to use. All rights reserved. There is no subscription for Proxymity itself.

Does it change my Resolve project?

The proxy builder reads the clips you select and writes proxy files to the folder you choose. The one thing it can write to your project is auto-link, which is off by default. When you turn it on, Proxymity links each finished proxy to its clip. It leaves a clip alone if Resolve already has a proxy linked, and it undoes the link if the clip's audio mapping changes. The editorial command-line tools are separate and write to Resolve only when you run them for that: stringout builds a timeline with markers and saves the project, and the audio tool changes clip gain only with its apply option.

Where do generated files go?

You choose the output folder in the app for each run. The app itself lives under your Library Application Support folder after install, with logs and data beside it.

How do I uninstall?

From the unzipped download folder, run bash uninstall.sh. It moves the installed app files and the Resolve launcher script to the Trash. It does not delete anything with rm.

Why a Terminal one-liner?

The curl script downloads the current zip, checks its checksum, unzips to a temp folder, and runs install.sh so you do not have to fetch the archive by hand.

Is Windows supported?

Yes, as a first beta: 64-bit Windows 10 or 11, installed with one PowerShell line (see the Windows section). It has not yet been tested on a physical PC by the author.

What does Data Burn-In do?

Data Burn-In draws text into the picture of each proxy: the source file name, the source timecode, the frame number, the frame rate, the resolution, and custom text you type. You choose a style (classic strip, dailies, minimal or Resolve look) and which fields to show. After each encode, a check reads the burned text at three sample frames.

How does RED (R3D) work?

ffmpeg cannot read R3D directly. Proxymity can decode through REDline from REDCINE-X PRO if you installed it. REDline is never redistributed with Proxymity.

Is anything sent to the cloud?

No. Encoding runs locally with no per-frame model calls. Editorial tools read your Resolve project on the machine where you run them.

What Resolve version do I need?

DaVinci Resolve Studio 21 or higher on macOS. The free version of DaVinci Resolve is not supported because it has no external scripting.

Does it run on Intel Macs?

The app is built for both Apple Silicon and Intel (macOS 12 or later), but it has only been tested on Apple Silicon. Intel Macs are untested.