Release Notes

3.4.2 11 September 2026

Fixed

• The point-size icons on the canvas now follow the selected tool. Previously, after switching to the refine tools, they could stay as circles from the point selected before. Switching tools now drops the point selection, and the icons take the shape and colour of the new tool. Clicking a point to edit its size works as before.
• Several minor bugs fixed.

3.4.1 6 September 2026

New

• A toolbar right on the canvas. Two rows of buttons now sit above the Object panel. The first row holds the five tools (select, box, point, FG and BG refine points), the point size (four dots — Point Detail Level), a padlock and Reset Scene. The second row holds an INIT button (its arrow shows where the init frame is; a click jumps there) and the Display Mode switch (OVERLAY · MATTE · RGB*A · RGB+A). These are the same settings as in the node panel — the buttons only mirror them on the canvas, and the active tool is finally visible. The padlock: closed (the default) — the tool never switches by itself; open — after you create an object the tool returns to Select / Edit. The padlock is remembered on this computer for every project. The Object panel is now always shown, on an empty node too; drag it by the OBJECTS bar or by the strip above the buttons.

Changed

• Jumping to the init frame is now the INIT button's job alone. Clicking the "INIT FRAME" line in the Object panel used to do it as well. The new panel carries an INIT button whose arrow already shows which way the frame lies, so the second route was removed. The line itself stays and still shows the frame number.

Fixed

• Overlay mode no longer goes black on plates with a floating data window (stabilised EXRs, CG renders with a per-frame data window). When the host asked for a canvas one pixel larger than the source image, the plugin treated the whole row as off-frame and painted it black — the mask still drew. The source is now read strictly within its own bounds, and such frames are baked under Freeze instead of being skipped.
• Tracking extends again on footage whose frame bounds shift from frame to frame. Stabilised EXRs (each frame carries its own data window) and a denoiser upstream make the frame size wander by a pixel or two. That used to read as a switch to proxy resolution and stopped the track from extending — most often noticed when tracking backwards. The resolution guard itself is unchanged and still works: a real proxy switch changes the size several times over.

3.4.0 31 August 2026

New

• A mask and an unknown zone at once, on separate channels of one input. The two used to share the Refiner Direct input, so you had to pick one. Two lists in the Refiners group — Refiner Direct Input: Object Mask and Refiner Direct Input: Unknown Zone — now say which channel holds which: the mask in red and the zone in green, for instance. The refiner resolves the edge in **a single pass**, seeing both. Works with AI objects and without them. The two channels must differ: one channel cannot mean "definitely the object" and "undecided here" at the same time. By default the mask is read from alpha and the zone is off, which behaves exactly as before. If your mask arrives as three channels with no alpha, name the channel yourself.

• Four masks instead of one on the Mask Composite input. The input stays a single one, but four masks are now read out of it: the original plus three colour channels — Mask Composite Mode R, G and B. Each has its own operation, so one mask can be added while another is subtracted in the same pass; until now every mask had to be merged upstream, which left you with a single operation for all of them. 🔴 Order of application: main → red → green → blue. It only shows when operations of different kinds meet: two Adds give the same result in any order, while an Add together with an Intersect does not. If something must be subtracted after everything else has been built up, put it in a later channel. The three new lists default to Off, so nothing changes for anyone already using the input. A channel the incoming clip does not carry does nothing.
• A new Multiply with Mask operation in all four lists. It differs from Intersect on semi-transparent edges: Intersect keeps the darker value and leaves a step, Multiply keeps the edge soft.

Changed

• The Refiner Direct Mode list is gone from the panel: what a mask means is now decided by the channel it arrives on. Projects saved in 3.3.2-3.3.3 behave exactly as before.
• Refiner Direct Scope is now Unknown Zone Scope — it governs the zone whichever way it arrived.

Fixed

• A stray click on the frame no longer costs you a bake under Freeze. The overlay is hidden while frozen, but the pen still reached the plugin: a click created an object, the inputs counted as changed, Freeze switched off and the frame was recomputed over the baked one. With the canvas hidden the pen now belongs to the host, not to us.
• Switching Freeze on parks the tool back on Select / Edit. Objects cannot be created while frozen anyway, so an armed drawing tool promised something that would not happen. Outside Freeze the tool is never switched for you.
• Refiner Model can no longer be changed under Freeze. The refiner affects the result, so switching models on a frozen node forced a recompute that **overwrote frames you had already baked**. The list now greys out along with the other settings that feed a bake.
• Nuke no longer prints version warnings when a saved project is reopened. Reopening used to print Illegal version number change lines to the console. Nothing was broken, but it read like something was.
• The unknown zone is drawn in purple instead of amber in the trimap view. This view paints, over the picture, the band along the mask edge that the refiner works on for fine detail — hair, soft edges: it shows exactly what the refiner will process, and you tune it with the Trimap Erode / Dilate sliders. The new colour stands out better on warm footage.

⚠️ Restart your host after installing. Updating with the host still open leaves the old plugin in memory, and it will not talk to the new server — masks simply will not appear.

⚠️ If you used the unknown zone and already baked frames, those frames will be recomputed the first time you open the project. The zone's scope setting now affects the result in more input combinations, so the earlier bake no longer matches. Everyone else is unaffected: if you never used the zone, your baked frames are served exactly as before.

3.3.3 24 August 2026

New

• New Open Bake Folder button — opens the bake folder of THIS node. It sits next to the existing Open Cache Folder, which opens the shared cache root holding every node's folder. Each node writes to its own subfolder named after the prefix, and this button opens that one directly, with no hunting through the rest. Handy when frames are baked under Freeze and brought back in with a Read node. Grayed out until a Cache Folder is set.

Fixed

• Switching the viewer resolution (proxy) no longer looks like a full cache. Masks computed at one resolution do not fit another, and the plugin reported it as "cache full, raise the memory" — which was never the reason. It now says the mask was tracked at a different resolution and names both ways out: switch back (the masks return instantly, nothing was lost) or re-track from the init frame.
• Continuing a track at a different resolution no longer damages what was already computed. It used to overwrite the earlier track with no way back. The plugin now asks you to start from the init frame, and the previous track stays intact.

3.3.2 22 August 2026

New: point the refiner at the hair by hand — Refiner Direct Mode

Fine hair that strayed outside the silhouette used to be lost, however high you pushed the quality settings. You can now paint over that spot and have the refiner work it out.

The Refiner Direct input has two new lists in the Refiners group:

• Refiner Direct Mode — Foreground (the previous behaviour, and still the default: nothing changes in your existing projects) or Unknown Zone, where the painted area means "undecided here" and the refiner pulls out strands it could not reach before.
• Refiner Direct Scope — Override the AI mask or Outside the AI mask, for masks that came back too solid or that are simply missing hair beyond the edge.

A rough brush stroke is enough — precision is not needed. How to use it, and when to pick which list: Refiner Direct Mode and Refiner Direct Scope in the manual.

Flame no longer cuts hints short

Flame showed only part of a hint: the text broke off mid-word, leaving a stub like "Point Detail Level sets h" instead of an explanation. More than a third of all hints were cut.

The limit turned out to be hard - about 255 bytes - and there is no way around it: Flame has neither a scrollable tooltip nor a setting for its length. So every hint that did not fit was rewritten shorter specifically for Flame: what the parameter does and why it matters now fits whole. The details live in the manual, which the Open Documentation button opens.

In every other host - Nuke, DaVinci Resolve, Fusion, Natron - the hints are unchanged, word for word: there is room enough there.

Eight parameters got hints they never had

Input Levels (Black / White / Gamma), Output Levels (the same three) and Mask Offset X / Y had no description at all - hovering over them showed nothing. Each one is explained now: the input levels shape the soft mask before it becomes a hard matte and so change what the refiner sees; the output levels are the last step and touch neither tracking nor the refiner; the offset shifts the finished mask by whole pixels.

Fixed

• The Gamma slider on Input and Output Levels ran further than it worked. It allowed 0.05 to 5.0, while only 0.1 to 2.0 reached the picture — past those the slider moved and the image did not. The range now matches what the engine actually applies. No project changes as a result: values outside that range already behaved as the limits.
• The & in the Display Mode hint went missing — hosts read it as a control character and swallow it. It is spelled out now.

3.3.1 18 August 2026

The plugin now tells you when you are working where there is no picture

A sequence can sit on the timeline away from frame one — files starting at 1001 while the project ruler starts at 1, for instance. Outside the clip the host holds the first frame: there IS an image on screen, and the spot looks like the head of the shot. An object seeded there tracks across one frozen frame, and that takes a while to notice.

• A warning on the very first frame. When the current frame has no source under it, the plugin says so at once: NO FOOTAGE ON THIS FRAME - SOURCE 1001-1190. Not twenty tracked frames later.
• Guides name where the shot lives. When the tracked frames and the source frames disagree, the guide shows both: GO INSIDE FRAMES 1-8 (SOURCE 1001-1190) TO CONTINUE TRACKING.
• The advice points where it helps. If the whole track ended up outside the shot, the guide no longer sends you back into it — it offers to reset and start again on the frame you are on: TRACKED FRAMES 1-2 ARE OUTSIDE SOURCE 1001-1190 / RESET HERE TO START AGAIN ON THE FOOTAGE.

When the track and the shot agree — normal work — the guides are unchanged, word for word.

Unattended installation across many machines (Windows, Linux, macOS)

The installer now runs from start to finish without a single prompt, so it can be rolled out with Action1, Intune, PDQ, SCCM and similar management tools. Verified on all three platforms. The exact switches, the exit codes and how to detect an existing installation are in the documentation, under Installing.

• Your host is never closed for you. If Nuke, DaVinci Resolve, Fusion or Natron holds the plugin, the installation stops and leaves the machine exactly as it was, rather than interrupting an artist mid-shot.
• Updating no longer asks permission to remove the previous version. That is stated on the installer's first screen instead, alongside the GPU requirements and the reminder to close your host.
• The "Installation complete!" box is gone — the wizard's final page reports the result.

The panel is laid out in the order of the work

Refiners has moved directly under Display Mode, and the remaining groups are arranged in the sequence a shot is actually built in, so the panel reads top to bottom instead of jumping around.

Fixed

• Reset Parameters returns the tool to Add Bbox Object. After a reset the node came back with the tool left on whatever had been selected before, so the first click did something other than what the panel showed.
• The host was told a frame range whose start was greater than its end when the clip began later than the current frame. The declaration is now correct.
• The hint on the License Status line carried an example trial period. The number in that example was read as the real number of days left. The examples are gone from the hint.

3.3.0 12 August 2026

Mask memory — the headline of this release

• The tracked-mask cache now holds roughly 90× more. Masks are stored compressed: a 6K frame takes about 1 MB instead of 59. Within the same memory budget the cache holds on the order of 12,000 frames instead of about 130 — long shots no longer evict themselves, and masks stop disappearing when you scrub back.
• Cache size is set in gigabytes. In the Memory and Undo group: Tracked Mask RAM (GB) — what you set is what you get. The previous percentage setting hit a hidden ceiling on large machines, leaving only two of its thirty-six positions meaningful.
• A warning when the cache runs short. If frames start being evicted during tracking, a warning appears right away rather than after you find a hole in a finished range.
• The init frame is never evicted from the cache, so tracking keeps its anchor.
• Baking no longer writes empty frames to disk. A frame evicted from the cache could previously be written out black and carry a valid signature — meaning it read back as correct next time the project was opened.

Working with objects

• Object letters no longer shift. A label is assigned when the object is created and stays with it: delete A from A B C D and the others keep their letters, while the next new object gets E. Labels used to be recomputed from the list of live objects, so deleting one silently renamed the rest.
• Text search: the threshold slider no longer recreates objects. Moving Score threshold reconciles the new detections against what is already there: matching objects keep their letter, colour, edits and tracking memory. Every slider move used to wipe the whole set and build it again — hence the long wait and the runaway labels.
• Text search: a new shot finds its own objects. A detection result is now tied to the frame's image, not just to its number and the word. A second node using the same word on the same frame number could previously receive boxes from the first shot.

Flame

• Boxes drag smoothly. Dragging no longer waits on a frame recompute: the box updates about three and a half times more often, and it no longer slows down with each additional object.
• Bake range counts frames the way the host's timeline does. A range of 50-100 bakes exactly 50-100; previously the first frame was skipped and one extra was added at the end. The frame number in the baked file name now matches what Flame shows as well.
• ⚠️ Because of this, baked file names have shifted — delete old cache folders on Flame before re-baking, or one folder will end up holding two numbering schemes.

Other

• Linux: the log no longer reports a server start that did not happen. A failed launch is now recorded as a refusal with the system's reason.

3.2.3 8 August 2026

• macOS: macOS 15 Sequoia or newer is required. The requirement previously stated 14 in error: on 14 the models cannot be compiled and no mask appears at all.
• macOS: a normal, double-click installer. Instead of Terminal commands, a disk image with an installer: welcome, licence, Install, one password prompt. The previous version is removed automatically; your licence and model cache are kept. Close your host before installing; if it was open, restart it — otherwise it keeps the previous version in memory.
• Fixed: in Flame, boxes and points sometimes were not drawn. When a node that had been showing the overlay was deleted or replaced, the right to draw stayed with it and the next node responded neither to drawing nor to the mouse; clicking another node and back was the only cure. Most common for users with many OFX plugins installed.
• Fixed: a warning about busy video memory could stay on screen. Waiting for the server is now bounded in time.
• The log survives and says more. It used to be wiped entirely when it outgrew its cap — newest session included; now only the oldest entries are dropped. Each session starts with the machine, the version and an integrity check, and refusals name their reason — so the answer is usually already in the files you send to support.

3.2.2 5 August 2026

• Fixed: the plugin would not open in Flame 2025. The node could be added but stayed empty — no parameters appeared, and Flame's status line read "Plugin com.onyx.aimatte3 not found". While creating the node the plugin restored internal bake state, and on Flame 2025 that step aborted node creation entirely. It no longer can — the node opens, and the state is picked up on the first render instead. Flame 2026 and 2027, Nuke, DaVinci Resolve, Fusion and Natron were never affected.
• Diagnostics for node-creation failures. If a host ever refuses to hand the plugin a parameter or an input, the log now names it in a single line — previously nothing was visible at all.

3.2.1 5 August 2026

• Documentation opens straight from the plugin — and works offline. A new Open Documentation button in the Help and Diagnostics group (formerly Server Tools). It opens the copy of the manual installed with the plugin, so it is available on machines with no internet access; if that copy is missing, onyxofx.com/docs opens instead.
• The Server Tools group is now Help and Diagnostics — it still holds the plugin version, the logs folder and detailed logging.
• Licence texts reviewed. The current TensorRT licence edition is now included, wording in the rights section was clarified, and third-party licences were brought in line with what actually ships.

3.2.0 3 August 2026

• macOS support (Apple Silicon). The plugin now runs on Mac — in Nuke, DaVinci Resolve and Flame. Inference runs on Apple's built-in neural engine; no separate GPU required.
• Flame support (Autodesk) — macOS & Linux.
• The Mac build is notarised by Apple — no system warnings on install.

3.1.6 25 July 2026

• Reliable mask writes to disk (Freeze). A write failure no longer loses the frame — it retries automatically, and if the folder is momentarily busy (antivirus, indexer) the write still goes through without destroying the already-finished frame. The failure reason is now written to the log (stage + system message). The red "CANNOT WRITE TO CACHE FOLDER" plate now shows only on a real persistent folder problem, not on a one-off glitch (false alarm removed).
• Fixed a rare host crash when saving a mask to EXR.
• New: red "SOURCE INPUT NOT CONNECTED" plate. When the node has no input wired, a centered warning appears — so a missing mask is not mistaken for a bug. The node stays usable: you can still draw boxes and points, and the plate clears the moment an input is connected.

3.1.5 24 July 2026

• Fixed a silent bake loss on a bad cache folder. A path that cannot be used (a missing drive, a folder with no write permission) used to turn Freeze on while nothing was written to disk. Freeze now checks the path: a dialog names the path and the reason and offers to pick another. Relative paths are allowed. If the folder exists but writes fail (read-only, full disk, network drop), a red "CANNOT WRITE TO CACHE FOLDER" plate shows and clears itself once a write succeeds.
• Object panel: per-node position, panels no longer stack. Several nodes used to pile their panels in one spot — the one underneath was hidden. Each node now remembers its own place and new nodes cascade down-left. Works in both modes, with and without "Pin". The position is saved in the project.

3.1.4 23 July 2026

• Bake the cache by frame range (Freeze → "Limit Bake to Frame Range" + "Bake From / Bake To"). Right under the Freeze button, a checkbox and two fields: when on, only frames inside the range are baked and shown, and frames outside the range pass the source through (no inference runs, nothing is written to disk). Bake a shot in sections into ONE folder — one node bakes frames 1–100, a second node with the same Name Prefix and Cache Folder bakes 101–200; the halves join on disk (read the assembled sequence back with an ordinary Read node). Enabling it sets the range to the scene's init frame (where the object was seeded) — extend it by hand. Tracking banners are suppressed outside the range. The "Overwrite baked masks?" prompt is now range-aware: it does NOT warn when the node writes to frames not yet in the folder (baking in sections), and it honestly states what it MAY overwrite versus what it keeps.
• Object Tools: the active tool is now grayed out and cannot be toggled off by clicking it again. Previously, clicking the already-selected tool could clear its checkbox or lag (needing several clicks). The active tool is now non-clickable, so exactly one tool is always selected.
• Fixed: white alpha on no-mask frames in Matte Overlay / RGB modes. With a partial Freeze bake, after reopening the project, frames with no baked mask (outside the baked range) showed alpha = 1 (white) instead of empty. Now, where there is no mask, alpha = 0 (black / transparent) as it should be. "Matte Only" was already correct.

3.1.3 19 July 2026

• New "Reset Track" button (Scene Cleanup group). Clears only the tracking — the AI's computed masks and memory — for a clean re-track from the init frame when a track went wrong after re-seeding or refining. Objects, seed points and refines are kept (unlike Reset Scene, which removes objects). Does not touch the Bake cache; grayed out while Bake is on.
• Object panel and boxes stay visible off the tracked range. Under the "GO TO INIT" banner (e.g. after duplicating a node), the object panel, the AI CROP badge and the object boxes now stay on screen — the panel's Reset button is reachable, and the badge and boxes no longer flicker.
• Red "GPU NOT SUPPORTED" banner on an unsupported GPU. If the card cannot run the plugin (no NVIDIA CUDA GPU, or a card older than RTX 2060 / pre-Turing), a red "GPU NOT SUPPORTED" banner with the detected card name appears in the center of the viewer. It is a warning — the node stays usable — so it is clear why there is no result (previously the plugin fell back to CPU silently). No banner on a supported RTX 2060+.

3.1.2 19 July 2026

• Correct handling of anamorphic material in Fusion. For non-square-pixel material (PAR ≠ 1) in Fusion Studio and the Fusion page in DaVinci Resolve, horizontal stretching of the overlay (box, crop, labels, dashes) and off-frame displacement of the mask are eliminated — geometry is derived from the actual pixel aspect ratio. Nuke, Natron and Flame are unaffected.
• Correct object-panel (OM) proportions in Fusion. On anamorphic material, horizontal stretching and displacement of the panel are eliminated, and cursor hit-testing on its controls is restored.

3.1.1 17 July 2026

• A "Reset Scene" button on the object panel. A round button in the "OBJECTS" title bar: press-release to wipe the scene (same as the Reset Scene parameter). Move off the button before releasing to cancel.
• A screen-pinned object panel no longer flies away. A pinned panel ("Pin Object Panel On Screen") can now be dragged anywhere on screen — it won't go off the edge or drift while zooming.
• Overlay appearance settings are saved globally. The overlay scale and colours ("Overlay UI Color", "Mask Overlay Color") are remembered on your computer and apply to every project — no re-tuning per project. The mask colour is no longer keyframe-animatable.
• Nuke before v16: the panel is no longer clipped by the top toolbar strip.

3.1.0 17 July 2026

• Input colour switch: "Apply sRGB LUT". A new "Input Color" group sits at the very top of the parameters, with a checkbox that is on by default — existing projects behave exactly as before. If your project is ACES or you manage colour yourself, turn it off and feed the colour in your own way (e.g. through OCIO): previously the input was always pushed to sRGB, so on an ACES project SAM3 saw distorted colour and segmentation behaved differently. Out-of-range values are clamped to 0–1 in either mode. Change it on the init frame (like the Crop parameters).
• License activation through a proxy. For studios on an isolated network (no direct internet): the License panel now has "Use Proxy", "Proxy Server", "Proxy Password" and a "Save Proxy" button with a status line. License activation and deactivation go through the specified company proxy (with a login and password if it requires them). With the checkbox off, everything works directly as before.
• Objects at the frame edge are no longer eaten away. When an object runs partly past the frame border, the mask now stays clean right at the edge (previously it could erode at the border).
• Stability in multi-threaded hosts. Fixed rare crashes caused by thread race conditions — between frame rendering and the UI / node teardown, and in the cold-start server exchange. The plugin is more reliable.
• New option: "Pin Object Panel On Screen". The "UI Appearance" group has a new checkbox that pins the object panel to a screen corner, so it stays in place while you zoom and pan (off by default: the panel moves with the image as before). The setting is saved on your computer and applies to every project.

• The INIT FRAME line in the object panel is clickable. Hover it — it turns green; click — the playhead jumps to the init frame. Same as the "Go to Init Frame" button, but on the canvas. Inactive on the init frame itself, and in DaVinci Resolve too — that host does not perform playhead jumps, so the button is hidden there as well. _Side note:_ the panel now drags by the "OBJECTS" title bar only — the INIT/TRACKED lines became a click target.

Point and mask-cleanup refinements:

1. Point Detail Level — 'Auto' removed, per-point size everywhere. The "Point Detail Level" dropdown no longer has "Auto" — four explicit sizes (Tiny detail / Object part / Large object part / Whole object). "Add Point Object" defaults to Whole object, the FG/BG Refine tools to Object part. Most importantly, every point (point object and refine point) now keeps its own size on the init frame too — previously a refine point's size only took effect on tracked frames. Projects from an earlier version open cleanly (values migrate automatically). Point Detail Level shows the selected point's size. When you select a point, the "Point Detail Level" dropdown now reflects that point's own size, so you can see its level at a glance (previously there was no feedback).

2. Remove Sprinkles — speckle cleanup is now per-object, not whole-frame. Previously small-island removal was computed over the whole merged frame mask at once, so a large neighbour inflated the total and a small whole object could fall under the threshold and vanish entirely. Now cleanup runs per object (each by its own size), so a small intact object survives while speckle is still removed. The default is lowered from 1000 to 100 px.

3.0.9 8 July 2026

• Backward tracking no longer drops the object. Previously, tracking forward, returning to the init frame (“Go to Init”) and then tracking backward could briefly lose the object for 1–3 frames before it recovered. The crop window now correctly resumes at the right edge — no drop. Verified with single and multiple objects, in both crop modes (Union and Per-Object) and in both directions.
• Cleaner cold start. On a first launch (or after clearing the cache), when engine preparation takes a few minutes, the plugin no longer spawns a redundant second server process or floods the log with errors — startup is more stable and clean (no more double GPU warm-up).

3.0.8 8 July 2026

• The scene's init frame is now visible. An Init Frame line under the Mode dropdown (Tracking Mode group) always shows the frame the scene's tracking started on.
• "Go to Init Frame" button. Jump to the init frame in one click. Works in Nuke and Fusion Studio; disabled in DaVinci (the host does not let a plugin move the playhead).
• Plugin version in Server Tools. The installed version now shows as the first line — handy to quote when contacting support.
• Object Manager. In the "INIT FRAME" and "TRACKED FRAMES" lines the label is flush left and the number flush right, so the number is easier to spot.

3.0.7 7 July 2026

• Better detection quality — detection and tracking are now steadier.
• Reset + text no longer hangs — after Reset Scene a new text prompt is created again and no longer stalls at the detection stage.
• Refine points now show which object they belong to — each refine point has a label (square + object name); in refine mode the selected object is focused and the others reveal on hover; the point diamond is slightly larger.
• On-canvas object labels — text objects are labelled with the found word ("BREAD 1"), point objects show "POINT 1" above the box; refine points are smaller.
• Colored group logo.

3.0.6 5 July 2026

• Fixed a text-prompt input bug in DaVinci / Fusion.
• Improved tracking accuracy.
• Refine corrections now hold on the following frames — previously a point correction could slip.
• Default text-detection threshold 0.3 → 0.4. Fewer false positives on similar-coloured objects.

3.0.5 2 July 2026

• Refine points: moving, adding and deleting a point now honestly recomputes the frame's mask; deleting all points restores the tracked mask.
• A refine click outside the frame now widens the processing window (using the UI padding) — you can extend the object when the frame has slipped; works for point objects too.
• On the init frame, an FG point placed outside the drawn box now grows the box itself — the starting prompt covers the whole object for cleaner segmentation.
• No Init mode: editing the box on a frame now re-seeds the scene — the mask follows the box.
• Switching tracking modes (Locked / Dynamic / No Init) inside the tracked range no longer resets your track.
• Mask Prompt: the input mask can now be corrected DURING tracking — move your roto while parked on a frame and a correction key is set exactly there (the mask applies on that frame, tracking continues from it); an animated/interpolating roto does not spawn extra keys. Keys show as diamonds on the MASK row, a diamond click removes the key, and keys survive project reopen.
• Show Trimap now displays when working through the Refiner Direct input — both with and without AI objects.
• Per-Object Crop: refine clicks on the second and further objects are no longer lost.
• Object Manager: the visibility circle fills green when an object has visibility animation keys.
• Installer (Windows): upgrading no longer wipes the warmed TRT cache — after an update the plugin starts right away, no engine re-warm (the cache is validated at launch and rebuilt only when truly stale: runtime, GPU or driver changed).
• Documentation: added the Node Inputs section — all four node inputs (Source, Mask Prompt, Refiner Direct, Mask Composite).