Genvid Connector lets compositors work inside Nuke against a live production tracker — read shot media into Read nodes, publish composited keyframes and shot videos back to the bound shot, and trigger Genvid AI generations from the comp output. Every publish writes a parsed comp DAG plus the raw .nk sidecar to provenance, with full C2PA digital-source-type tagging. PKCE OAuth, OS-keychain credential storage, no embedded secrets.
Genvid Connector for Nuke — AI generation with provenance
First submitted: 21 May 2026
Author: Gerard Heinz
Website: https://genvid.com
Compatible Nuke versions: 14.0 or later
Compatibility: Linux, Mac, Windows
What it does
Genvid Connector turns Nuke into a first-class node in a Genvid-tracked production. A compositor signs in, binds the current `.nk` script to a shot, and gets a Genvid Browser panel that mirrors the web app's shot and asset media. Drop shot keyframes or generated videos straight into the Node Graph as Read nodes, comp them, publish the result back to the shot, and watch it surface in the web UI with a Nuke corner badge and the full parsed comp DAG attached as provenance.
The plugin also adds two custom nodes:
GenvidGenerate. Triggers an AI generation (I2I, I2V, KF2V, V2V, or Upscale) using the upstream comp output as the input image / video. Result media is auto-bound back to the shot.
GenvidRead. A Read node variant that lazy-fetches signed URLs from Genvid Storage, so your script does not break when a media file is relocated or expires.
Highlights
Workflow-native. No file copying, no manual upload. The Browser panel is keyboard-driven; double-click a thumbnail to drop a Read node.
Provenance built in. Every publish writes a parsed comp graph (JSON) and the raw `.nk` sidecar to Storage. The web app shows a Nuke corner badge on the media node and a "Comp Graph" sidebar tab with a read-only React Flow view of your DAG and a `.nk` download link.
C2PA-correct. `digital_source_type` is selected dynamically — `composite` when all inputs are camera-original or human-made, `compositeWithTrainedAlgorithmicMedia` when any upstream input was AI-generated. No manual flagging required.
Standards-conforming auth. OAuth 2.1 + PKCE for desktop clients. Refresh tokens live in the OS keychain via `keyring` (Keychain on macOS, Credential Manager on Windows, libsecret on Linux). The plugin never sees a long-lived secret.
Multi-DCC ready. The publish endpoint is `dcc=`-tagged, so the same backend will absorb Photoshop, Resolve, and After Effects connectors as they ship. Your Nuke provenance does not become a silo.
Requirements
Nuke 14.0 or later (NukeX / Indie / Studio all supported)
Python 3.9+ (bundled with Nuke 14+)
macOS 11+, Windows 10+, or Linux (RHEL / Rocky / Alma 8+)
A Genvid account on a production where you are a member
Install
Individual artist — pip
# bash
# From inside Nuke's terminal, or against Nuke's interpreter:
nuke --python-only --script "import pip; pip.main(['install', '--user', 'genvid-nuke'])"Then add to your `~/.nuke/menu.py`:
import genvid_nuke
genvid_nuke.install()```Studio shared install — zip
Download `genvid-nuke-<version>.zip` below
Unzip into a directory on `NUKE_PATH`, e.g. `/studio/nuke/plugins/genvid-nuke/`
Add to `init.py`: `nuke.pluginAddPath('/studio/nuke/plugins/genvid-nuke')`
Both methods register the menu entries, the custom nodes (`GenvidGenerate`, `GenvidRead`, `GenvidConfig`), and the Browser panel. First launch walks you through PKCE sign-in.
Quickstart (2 minutes)
Sign in. `Genvid → Sign in…` opens a browser tab for PKCE OAuth. Approve, return to Nuke.
Bind a shot. `Genvid → Bind to shot…` opens the project / sequence / shot picker. Selection writes a `GenvidConfig` NoOp node into the script — that node is the binding, so the binding travels with the `.nk`.
Pull media. Open `Genvid → Browser` (or hit the panel hotkey). Double-click any keyframe or shot video to drop it as a Read node.
Comp. Whatever you would normally do.
Publish. `Genvid → Publish comp as keyframe` or `Publish comp as shot video`. The plugin renders the active Write or Viewer output, serializes the comp DAG, uploads the `.nk` sidecar, and posts to `/projects/{p}/comps`.
Generate (optional). Tab → `GenvidGenerate`, set mode to I2V / KF2V / V2V / Upscale, hit Execute. The plugin polls for completion (5s while the panel is open, plus a sync sweep on every script open) and a Read node downstream of `GenvidGenerate` auto-populates when the result lands.
What gets stored
When you publish, the following lands in Genvid:
The rendered output (PNG / EXR / MP4 / MOV depending on what you wrote)
The raw `.nk` script as a Storage sidecar (signed URL only — no public exposure)
A parsed JSON `comp_graph` keyed by node, capturing class, label, inputs, key knob values, and channel routing
A `media_media_link` row per upstream input, with `link_type` set to one of `nuke_input`, `nuke_clean_plate`, `nuke_matte`, `nuke_track_ref`, `nuke_grade_ref`
The `model_provider` on the resulting media row is set to `Foundry Nuke`. Domain events from the plugin carry `source='nuke_plugin'` so downstream listeners can route accordingly.
Versioning & support
Versions follow semver. `0.x` while Nuke 14 is the only target; `1.0` once Nuke 15 ships and is qualified.
Documentation and bug reports: https://app.genvid.com/docs/integrations/nuke
Studio pilots and bulk-license discussions: see https://genvid.com
or register to download or rate.
Comments