pixRepaint

Home / Changelog

Changelog

Version numbers change only with public releases; versions are listed from newest to oldest.

0.4.72026-10-25
  • Account management: “Use other keys when concurrency is full” is now “Auto-switch to a working key”. When ticked, the next API Key in the “Manage Keys” order is used whenever the key in use is at its concurrency limit, out of RH coins, out of wallet balance or has used up its spending limit; keys that were not used, and why, are shown in the node’s status line. See the documentation.
  • When an API Key has used up its spending limit, the message now says so instead of “Invalid API key”.
  • Rp M Paint, Rp M Paint Pass2 Upscale, Rp M Sharpen, Rp M Motion Fix and Rp M Remove estimate the size of the job before submitting; if it is over what the model can process at once, a dialog warns you and suggests shortening the frame range or reducing the canvas, and you can submit anyway or cancel.
  • When a job fails because a file stored on RunningHub is corrupted, the message explains this, and the next submission uploads a fresh copy automatically.
  • Fixed: a finished job occasionally kept one of the account’s concurrent-job slots for 2–3 minutes, so later jobs queued longer.
  • With projects on a network drive, opening a node panel with crop preview and changing the resolution no longer lags.
  • For a node inside a Group that takes its footage through the Group’s input, changes upstream outside the Group are now picked up on the next submission (previously the old footage could be reused).
  • After saving the project to another folder, Rp M Paint Pass2 Upscale no longer reports that the previous pass’s footage cannot be found.
  • Stability improvements and bug fixes.
0.4.62026-10-22
  • Clearer messages when a submission fails: not enough RH coins on RunningHub, an invalid API key (mistyped or deleted on RunningHub), a temporary RunningHub error, or RunningHub being unreachable or blocked by your company network are now explained directly; an invalid API key no longer makes the plugin upload the footage again and again. See the documentation.
  • When the live progress connection drops, the status now says the job is still running and that progress refreshes every 5 seconds.
  • Rp M Remove, Rp M Motion Fix, Rp M Sharpen and Rp M Tile Upscale now have “Randomize” (off by default): when checked, each submission uses a new seed.
  • “Restore source node” now unchecks “Randomize”, so the restored node keeps the seed that was used.
  • Stability improvements and bug fixes.
0.4.52026-10-21
  • Stability improvements and bug fixes.
0.4.42026-10-20
  • Installing a new version from “Check for updates…” in the plugin menu no longer requires closing Nuke: it installs in the background and lets you know when it’s done. Save your script and restart Nuke (every open Nuke) to use the new version; a Nuke that hasn’t been restarted will ask you to restart when you submit a job.
  • Updating from 0.4.3 or earlier to this version still requires closing all Nuke windows. If it keeps saying Nuke is still open after you’ve closed them all, end the remaining processes whose names start with “Nuke” in Task Manager (Nuke’s background render processes sometimes don’t exit on their own), then click “OK”.
0.4.32026-10-20
  • Clearer messages when a job fails to submit or run: insufficient RunningHub balance, an invalid API key, a busy platform, an unavailable machine tier or an oversized footage file are now explained together with what to do. When a job fails in the cloud, the plugin suggests a fix for common cases such as running out of GPU memory, an interrupted job or footage the platform cannot read, instead of showing the platform’s raw error. The full original error is still printed to Nuke’s Script Editor, for when you contact us. See the documentation.
  • When a job does not succeed, the plugin sends an error code to the licence server so that we can see why jobs fail and improve the messages; the code contains no footage, prompts, generated results or file paths. See the privacy policy.
0.4.22026-10-20
  • If several computers share one account, please update all of them to 0.4.2. 0.4.2 changes the input order of newly created Rp M Paint Pass2 Upscale nodes (source / mask / refs / control); submitting such a node from an older plugin version may swap the reference and mask inputs.
  • New Rp M Motion Fix: repairs smearing and motion blur caused by fast movement or whip pans, regenerating only the blurred frames and keeping the plate everywhere else. See the documentation.
  • New Rp M Remove (experimental): removes people or objects inside the roto and fills in the background, generating long shots in segments; when unwanted content appears in the removed area, the segment can be regenerated automatically. See the documentation.
  • Video node panels now match Rp M Paint: frame range, fps and transfer quality share one row and fps is a drop-down; every video node has “Get upstream range”, which also reads the upstream fps; single-input nodes name their input source. Existing nodes switch to the new layout when their panel is opened, and an fps referenced by another node's expression is left unchanged.
  • Rp M Paint Pass2 Upscale: newly created nodes use the input order source / mask / refs / control; “Get upstream range” is also available with direct video input; “Get previous prompt” is renamed “Get upstream prompt”.
  • Account management: “Remove Key” becomes “Manage Keys”, which sets the order of several API Keys. With two or more keys saved, “Use other keys when concurrency is full” (off by default) submits with the next key in order when the key in use is at its concurrency limit. Both Consumer / Member and Enterprise / Shared API Keys can be used.
  • Each submission saves a copy of the project as it was in the job archive for later reference; the latest 30 per project are kept, and “Package Project To…” leaves them out.
  • Machines in the machine list are numbered within your account (#1, #2…).
  • “Randomize” is on by default in new Rp I Edit nodes.
  • Fixed “Invalid LUT selected” on Read nodes created when video dragged into a project using ACES or another OCIO config is converted, and the Pass2 “From previous step” mask preview showing black.
  • The installer, uninstaller and the entry in Windows “Settings > Apps” now show the pixRepaint icon.
0.4.12026-10-18
  • If Nuke is closed or crashes while a cloud job is running, reopening the project resumes the unfinished job: the node status shows that the job is being resumed, progress continues, and the result node is created as usual.
  • If the node is deleted, cut or moved while its job is running (or a new or different project is opened), no incomplete result node is created; a message tells you where the output was saved instead.
  • Uploads are retried automatically after network errors, timeouts or a busy server (up to 4 times per file, shown in the status), and a stalled upload stops at once when cancelled.
  • Downloading results keeps retrying for about 5 minutes through network outages, and retries when the output file is briefly locked by antivirus software. If a cancelled job could not be cancelled in the cloud, the node status shows the task ID so it can be cancelled on the RunningHub website.
  • Fixed “Invalid LUT selected” when submitting from projects that use ACES or other OCIO configs.
  • When the source has non-square pixels (for example anamorphic footage), the “Submitted” status suggests reformatting to square pixels first, so generated content keeps the right proportions.
  • Fixed submissions reusing a stale cache after an upstream node was disabled or enabled. Changing the project's color management settings also re-renders the inputs (the first submission after installing this version renders the inputs again).
  • “Collect Files into Project” and “Package Project To…”: fixed copies of read-only footage that could not be overwritten later and footage with [ ] $ in its name overwriting each other; replaced sequence frames of the same size are no longer treated as already copied.
  • Fixed “Fast” transfer quality failing for sources with an odd width in Rp M Tile Upscale, Rp M Sharpen, Rp UltraSharp, Rp ColorMatch and Rp Control.
  • Rp M Refs no longer shows the “With audio” option, which had no effect in the cloud; “Show advanced parameters” in Rp I Edit no longer reveals settings that have no effect.
  • Fixed Chinese text in the Pass2 Upscale status, and Rp I Edit's rewriting state not being recognised when a project is opened in the other interface language. Clicking OK in “Options…” no longer reverts a language change that has not taken effect yet.
  • If the site cannot be detected from the API Key during activation, the account is activated for the site selected under “Platform” instead of stopping on the activation page. Queue and quota in the account window are now queried on the international site for international accounts.
  • Fixed an error after signing in, or the machine ID being regenerated (using up an extra seat), when the settings files were briefly locked by another program; fixed occasional failures to submit while offline.
0.4.02026-10-15
  • English interface: menus, node panels, account windows, status messages and error messages are all available in English. The installer asks for the language (English or Chinese) and preselects it from the Windows display language; you can change it later with “语言 / Language” in the “Sign in…” and “Activate…” windows or in “Options…”, and the change takes effect after restarting Nuke. Nodes already in a project keep the language they were created in.
  • Support for RunningHub's international site (runninghub.ai): “Activate…” has a new “Platform” option, and when an API Key is entered the site is detected from the key. All nodes that run in the cloud are available on the international site. The “View RunningHub ID” and “Get API Key” links open the pages of the selected site.
  • Open beta for international users: activating with the trial code 8888 on the international site gives a 30-day free trial.
  • Rp I Upscale: new “Adherence” parameter, setting how closely each tile follows the original while repainting. The default of 1 keeps previous results unchanged; lower values add more detail but may change content such as faces or text.
0.2.1 – 0.3.12026-09-17 – 2026-10-12
  • Earlier versions were released with a Chinese interface for RunningHub's China site; their changes are listed in the Chinese changelog.