Tips / checklist

Autograph OFX plugin testing order before you trust a project

Published May 1, 2026 - Updated June 14 with RE:Vision OpenFX startup caveats.

Autograph's OFX story is real enough to test, but not broad enough to trust blindly. Maxon has official Red Giant support, RE:Vision has Autograph-specific host pages, and Maxon also documents an OFX blacklist path for plug-ins that prevent Autograph from starting. That combination says the right workflow is controlled testing, not plugin enthusiasm.

The testing order

Start with a clean Autograph launch before installing or enabling extra OFX plug-ins.
Enable Red Giant first if your test depends on it, because Maxon publishes the clearest Autograph support and compatibility trail there.
Test RE:Vision tools one family at a time: Twixtor, RSMB, RE:Lens, RE:Match, RE:Map, REZup, DE:Noise, or Effections should each get a tiny reload test project.
For vendors without an Autograph-specific support page, treat OFX loading as an experiment, not as confirmed support.
After every plugin update, reopen the tiny test project, save a copy, close Autograph, and reopen it again before using that plugin in paid work.

Red Giant access path to verify

Maxon's current Red Giant page says Autograph can reach Universe and Red Giant OFX tools from the Autograph Modifier list or the integrated Maxon Studio plugin page. Treat both as test points: confirm the effect appears in the Modifier list, confirm the Maxon Studio plugin page opens the same tool family, then save and reopen a small project before relying on either path.

Startup caveat to check on Apple Silicon

RE:Vision's Autograph FAQ adds a small but practical host note: on Mac M1 / ARM64, use plug-ins released from February 2, 2023 or later, and remember that problematic OpenFX plug-ins can be blacklisted by author. That does not prove every RE:Vision effect is safe in every Autograph project, but it gives a concrete first triage step when Autograph fails before you can even open a scene.

What to record

Autograph version, plugin version, OS, GPU, and whether the project reloads after saving.
The exact effect names used, not just the vendor name.
Any startup failure, visual mismatch, black frame, clipping, licensing prompt, or save/reopen problem.

Confirmed support versus inference

Use different language for different evidence. Red Giant and named RE:Vision Autograph pages are confirmed public support signals. Boris FX guidance is useful because it explains the difference between an OFX host and a qualified supported host, but if Autograph is not on a given vendor's supported-host list, do not call it supported. Call it test-only until the vendor says otherwise.

The RE:Map release notes are useful because they are not a generic RE:Vision claim. They name an Autograph-specific 4.1.11 build and say an upgrade is needed for Autograph 2026, which makes RE:Map a confirmed test candidate.

The REZup release notes are a maintenance watchpoint, not a reason to claim a new Autograph-only feature. Version 2.2.0 is listed on the Autograph release-note page dated May 27, 2026, but the new bullet is Flame Linux support. Treat it as current RE:Vision maintenance plus Autograph-host page evidence, then test the exact REZup workflow before using it in paid work.

Sources

Back to article list