AIFX v0.2.6

The MatAnyone2 pipeline no longer needs a custom ComfyUI node to pick its
reference frame.

All three platforms ship this version. The change is not platform-specific;
Windows was rebuilt from the 0.2.6 tree on 2026-09-03.

Changed

• MatAnyone2 no longer depends on the custom Frame Select node. The
  reference frame handed to SAM3 is now picked with ComfyUI's native
  ImageFromBatch (node 197, batch_index + length: 1) instead of the
  custom Frame Select node (node 179, select). That is the whole point of
  the swap: one less custom node on the ComfyUI server that can go missing or
  break on an update. MatteMaMa and SegmentationSAM3 already used
  ImageFromBatch, so all three plugins now pick their reference frame the same
  way.

  The Reference Frame parameter is unchanged and existing projects load as
  before. Both code paths were updated — the built-in workflow and the bundled
  resources/workflow/matte_ma2.json template — so a custom workflow file keeps
  working too.

  ⚠️ One behavioural caveat. ImageFromBatch.batch_index is 0-indexed. If
  the custom Frame Select node's select input was 1-indexed, the same
  Reference Frame value now selects the frame before the one it used to.
  Worth one confirming render on a shot where the detection is obvious.

Known issue — macOS blocks the installer

The .dmg is not notarised, so macOS 15+ refuses to launch the wizard. Use the
tarball's install.sh instead — a script run from a terminal is never
gatekeeper-assessed:

tar xzf aifx-0.2.6-macos-universal.tar.gz
cd AIFX-0.2.6-macos-universal
./install.sh              # /Library/OFX/Plugins — required for Flame / Flare

The Windows setup.exe is unsigned, so SmartScreen may warn on first run:
More info → Run anyway.

SHA-256

8ae30d83020d16e5438d91f1d8d5a106f85b14b247992afa0b3c00ab741ac767  aifx-0.2.6-macos-installer.dmg
c14eb971b0a8b71c7717c4564660258aa182642d9ef08d200c7e5a2e4ba2b22c  aifx-0.2.6-macos-universal.tar.gz
f5a721470bac637270b65228b191f0c083787839895d0aa952e3c724c5a4bcde  aifx-0.2.6-linux-x86_64.tar.gz
03a499093b5d5bec1ed1eb1722e41fa48fd2701bef3d424e0b9dcfb4d85c347c  aifx-0.2.6-windows-setup.exe
3bf37995e09a8d9cd46946f1a2989dfa25a95dabb619c60f478880eb84df7c59  aifx-0.2.6-windows-x86_64.zip

AIFX v0.2.5

The macOS wizard could not complete an install at all, a workstation could be
told to ignore whatever it installed, and SeedVR2 came back cropped in Flame.

All three platforms ship this version. The SeedVR2 fix below is not
platform-specific; Linux and Windows were rebuilt from the 0.2.5 tree on
2026-08-28.

Fixed

• SeedVR2 upscaling 1280x720 → 1920x1080 in Flame delivered a 1280x720 crop.
  The EXR on disk was correct; only what came back into the host was wrong. Flame
  is a fixed-format host (kOfxImageEffectPropSupportsMultiResolution == 0) and
  is spec-compliant when it ignores the RoD we return and allocates an
  input-sized buffer. The cache reader could not tell that apart from a tiled
  render — a (0,0)-(1280,720) window is "inside" a 1920x1080 result — so it
  extracted the corner. It now checks the canvas the host actually allocated
  before testing for a sub-region.

• The macOS wizard's progress bar froze at 80% for the whole install, through
  the password dialog and the entire copy, which reads as a hung installer. That
  phase is one osascript invocation with nothing to count, so the bar now goes
  indeterminate instead of showing a fraction it cannot measure. A failed install
  no longer leaves the bar frozen at 80% either.

• The macOS wizard failed at the last step with Operation not permitted. It
  staged the bundles in the app's confined temp directory
  ($TMPDIR/TemporaryItems/NSIRD_…). Staging runs as the operator and worked;
  the install runs as root via AppleScript, in a different security context, and
  the sandbox refused it the read. EPERM, not EACCES — being root did not
  help. Staging now happens in /tmp. The terminal installer (install.sh) was
  never affected.

• setup-env.sh hijacked OFX_PLUGIN_PATH machine-wide. Setting up a build
  environment exported it into the developer's shell profile, pinning every OFX
  host on that workstation to one per-user directory permanently. Installing
  system-wide afterwards changed nothing: the host still read the old path, with
  no error to explain it. It no longer sets the variable.

  ⚠️ Workstations set up before this keep the export until it is removed by
  hand. Check with echo $OFX_PLUGIN_PATH; if it is set, remove the
  export OFX_PLUGIN_PATH=… line from the shell profile and log out and back in.
  See Troubleshooting.

  This one is POSIX-only — the Windows setup script never touched the variable.

Added

• install.sh warns when OFX_PLUGIN_PATH is set and does not cover the
  directory it just installed into — the one case where a fully successful
  install still leaves the host with no plugins.

Known issue — macOS blocks the installer

The .dmg is not notarised, so macOS 15+ refuses to launch the wizard. Use the
tarball's install.sh instead — a script run from a terminal is never
gatekeeper-assessed:

tar xzf aifx-0.2.5-macos-universal.tar.gz
cd AIFX-0.2.5-macos-universal
./install.sh              # /Library/OFX/Plugins — required for Flame / Flare

The Windows setup.exe is unsigned, so SmartScreen may warn on first run:
More info → Run anyway.

SHA-256

40f426216f9c434e80c9dee426a3e69657e00e25e404b3cc30129bc5de8e3d50  aifx-0.2.5-macos-installer.dmg
81bab7481cd673f04db702eb7d6938814735be64b646adf14940a4e0720f714c  aifx-0.2.5-macos-universal.tar.gz
8c6f9039f3de6bab93c7965337761ddf5f54167284a7112830ea03898f4a1c8c  aifx-0.2.5-linux-x86_64.tar.gz
f4faa85071b8ac23df81620bd62baff23127ea75adefe5b89e4b951bb803b36d  aifx-0.2.5-windows-setup.exe
216fc3f0d3f2727a95e3c8c5e8fe7839b1c9f2f2a0a72f3edb137a44a62a07f3  aifx-0.2.5-windows-x86_64.zip

Note — the .dmg was replaced in place on 2026-08-28 to carry the progress-bar
fix. Installer-only: no plugin code changed, the .tar.gz artifacts are the
originals, and every bundle still stamps version=0.2.5.

AIFX v0.2.4 (macOS + Linux + Windows)

Two field-reported plugin fixes, plus the install-scope default inverted.

All three platforms ship this version. Windows caught up with a rebuild —
neither fix was platform-specific, so a Windows workstation was hitting the
MatAnyone2 naming bug on the 0.2.2 build.

Fixed

• MatAnyone2 rendered every frame and re-imported none. Its workflow was the
  only one of the seven whose SaveEXR node carried version: 0 instead of -1,
  so ComfyUI wrote <basename>_v000.0056.exr while the plugin looked for
  <basename>.0056.exr (no version suffix — the version is already the output
  directory's name). The job completed, the EXRs landed on the share, the host got
  nothing back, and nothing logged an error. Affected all three platforms.
  ⚠️ Outputs already rendered under the old _v000 names will not be found by the
  cache and need re-rendering.

Changed

• Video MaMa's Max Resolution control is removed from the panel and fixed at
  1024. The VideoMaMa sampler misbehaves on Linux for values that are not
  multiples of 1024. The parameter is retained but hidden, so existing projects
  still load; the default moves from 1080 to 1024.
• System-wide is now the default install scope on both the POSIX script
  (./install.sh, with --user to opt out) and the Windows wizard. Autodesk Flame
  and Flare only scan the machine-wide OFX directory, so the old per-user default
  gave operators a clean "installed" and an empty effects browser.

Windows

Run aifx-0.2.4-windows-setup.exe and accept the default all-users location
(%COMMONPROGRAMFILES%\OFX\Plugins) — the only one Flame and Flare scan. The
installer is unsigned, so SmartScreen shows "Windows protected your PC": click
More info → Run anyway. The zip is the manual alternative — unpack the
.ofx.bundle folders into the same directory.

Target machines need the Microsoft Visual C++ Redistributable (x64).

Known issue — macOS blocks the installer

The .dmg is not yet notarised, so macOS 15+ refuses to launch the wizard.
Use the tarball's install.sh instead — a script run from a terminal is never
gatekeeper-assessed:

tar xzf aifx-0.2.4-macos-universal.tar.gz
cd AIFX-0.2.4-macos-universal
./install.sh              # /Library/OFX/Plugins — required for Flame / Flare

Linux

tar xzf aifx-0.2.4-linux-x86_64.tar.gz
cd AIFX-0.2.4-linux-x86_64
./install.sh              # /usr/OFX/Plugins — required for Flame / Flare

SHA-256

84c8a648ee3186cf14bc4d2fd60203c5a7d31bbee2c4706e2ee7805ac5231dfa  aifx-0.2.4-macos-installer.dmg
f1cc3f32e9773b414f39fa23f854dd9d1e4b50a4610a379131e1fcc5ee1b6673  aifx-0.2.4-macos-universal.tar.gz
f0d8aca5d9c85b4a3e1914ae454ad50ac6e8ed03a42ef45c63d2f485f9542fc6  aifx-0.2.4-linux-x86_64.tar.gz
fc3c00eb6120cee5353818f906b841af1958cb19c7f0a286fb888532db4f6c86  aifx-0.2.4-windows-setup.exe
a72f7c09830ecacb316c736a7c893f011ab0f66d55c65cf2f4ba4cbfceafd17c  aifx-0.2.4-windows-x86_64.zip

AIFX v0.2.3 (macOS)

macOS only. Linux and Windows stay on
v0.2.2, which is
current and carries the SaveEXR fix — nothing here changes their binaries.

The installer no longer needs an Apple Developer ID

The .dmg wizard is unsigned, so macOS 15 and later refuse to launch it and
offer no bypass. Rather than ask every operator for a workaround, the macOS
tarball now ships install.sh — a script run from a terminal is never
checked by Gatekeeper.

tar xzf aifx-0.2.3-macos-universal.tar.gz
cd AIFX-0.2.3-macos-universal
./install.sh --system      # /Library/OFX/Plugins — required for Flame and Flare
./install.sh               # ~/Library/OFX/Plugins — Nuke, Resolve, Fusion

Same prompts as the wizard: ComfyUI server address and port, this machine's view
of the shared folder, the ComfyUI server's view of it, timeout. It writes them
into all seven plugins, copies the bundles into place and clears the quarantine
flag. ./install.sh --help lists the non-interactive flags for fleet rollout.

It is the same script that ships in the Linux tarball, so the two cannot drift.

Fixed

Quarantine was never actually cleared

macOS 26 removed xattr's -r flag. Every de-quarantine call in the project
used xattr -dr, which now exits 64 having cleared nothing — and in the SwiftUI
installer that call was best-effort, so it failed without a word. If you were
told to run xattr -dr com.apple.quarantine … for an earlier release, that
command did nothing. The working form is:

find '<path>' -exec xattr -d com.apple.quarantine {} \; 2>/dev/null

Every call site, doc and release README now uses it.

The installer script could not have run on macOS

It used mapfile, a bash 4 builtin. macOS still ships bash 3.2 at /bin/bash,
where it does not exist — the script would have died looking for the bundles.

Still open

The .dmg remains unsigned; use install.sh above, or the workaround in
Troubleshooting.

Verifying

tools/verify-ofx-abi.sh

All seven bundles should report OK — 0.2.3.

Full changelog: https://github.com/Dev-Reepost/aifx/blob/v0.2.3/CHANGELOG.md

SHA-256

dfdd9ef8788f2ddff0bc2d304c4ff72f519b307ef27172110c376fd7e819813b  aifx-0.2.3-macos-universal.tar.gz
1a1512dbf80153b728e428521ced314e99e80ff70dd7dedd057ef6cec5e8a44a  aifx-0.2.3-macos-installer.dmg

AIFX v0.2.2 (macOS + Linux + Windows)

Field fixes from the first Flare/macOS deployment. All three platforms are on
0.2.2 — macOS, Linux and Windows binaries were all re-cut for this release.

Fixed

Renders produced no output

All seven workflows sent create_path_if_missing: true to the SaveEXR node,
which current builds of that ComfyUI custom node reject — the job ran and
nothing came back. Now false everywhere, in both the bundled workflow
templates and the hardcoded fallbacks.

This affects every platform — the Linux and Windows builds shipped here carry
the same fix. If you are still running 0.2.1 or earlier on any OS, renders will
produce nothing.

Nothing is lost by this: the plugin already creates the full
out/<project>/<workflow>/<version> tree itself before submitting, and fails
loudly if it cannot. Changed in all seven plugins, not just the four reported —
the SaveEXR node is identical across them, so the rest would fail the same way
as soon as they were exercised.

The installer put plugins where Flame and Flare cannot see them

It defaulted to ~/Library/OFX/Plugins, which Autodesk's hosts do not scan, and
the system-wide option was never actually implemented. The install reported
success and the plugins never appeared in the host.

System-wide now works: the installer stages the patched bundles in a temp
directory, then copies them into /Library/OFX/Plugins through one macOS
authorisation prompt. It is the new default, and the location picker states
which hosts read each directory.

If you are upgrading from an earlier install, remove the old per-user copies:

rm -rf ~/Library/OFX/Plugins/{DepthAnything3,DepthCrafter,MatteMA2,MatteMaMa,NormalCrafter,SegmentationSAM3,UpscaleSeedVR2}.ofx.bundle

The installer's progress bar stayed at 0%

The engine ran every file operation on the main actor, so SwiftUI never got to
redraw until the whole install had finished. Per-bundle work now runs off the
main actor and the bar advances as it goes.

The DMG would not open on some Macs

hdiutil defaults to APFS on a recent build host, and an APFS disk image does
not mount on macOS 10.12 or earlier — silently, so double-clicking appears to do
nothing. The image is now HFS+.

Not a bug: Depth Anything 3 has no "Collect & Process" button

DA3 is the only per-frame plugin — monocular depth, each frame independent, so
there is nothing to batch. Its panel shows an Enable Processing toggle
instead. Every other plugin is sequence-based and shows Collect & Process.

Known issue — macOS blocks the installer

The .dmg is not yet signed with an Apple Developer ID, so macOS 15 (Sequoia)
and later refuse to launch it: "Apple could not verify 'AIFX Installer.app' is
free of malware". Neither right-click → Open nor the Open Anyway button
is offered for an unsigned app. Copy the app out of the read-only DMG and clear
the quarantine flag:

cp -R "/Volumes/AIFX 0.2.2/AIFX Installer.app" /Applications/
xattr -dr com.apple.quarantine "/Applications/AIFX Installer.app"
open "/Applications/AIFX Installer.app"

The .tar.gz contains no app and is unaffected.

Known issue — Windows SmartScreen warns on the installer

aifx-0.2.2-windows-setup.exe is not code-signed, so SmartScreen shows "Windows
protected your PC" on first run. Click More info → Run anyway, or verify the
SHA-256 below and use the .zip instead (copy the seven .ofx.bundle folders to
C:\Program Files\Common Files\OFX\Plugins\).

Verifying the install

tools/verify-ofx-abi.sh

All seven bundles should report OK — 0.2.2. On Windows the script does not
apply — check that each installed bundle's Contents\Resources\aifx-build.txt
reads version=0.2.2.

Full changelog: https://github.com/Dev-Reepost/aifx/blob/v0.2.2/CHANGELOG.md

SHA-256

14bd091f812005fc4d241952bf0bb76296555e6374eb2cd1d987a5ed8d483487  aifx-0.2.2-linux-x86_64.tar.gz
edff9979e19d069e54d2ec3121b09ee1a9838fd803fcde48825758d8e1aff1ce  aifx-0.2.2-macos-installer.dmg
1a7ff10c49e73d0864d8731d922a885daa9781c968a8a9edaa3538e4327ab5f3  aifx-0.2.2-macos-universal.tar.gz
7ce6a45aee5b8c7bb37a7a00bb498a047ee630aec4a8f227f7c5b72ce02cc821  aifx-0.2.2-windows-setup.exe
b1881a950ea29a85609a2b20d62d98f46571421432d2ab26c2d2288879aa91a8  aifx-0.2.2-windows-x86_64.zip

AIFX v0.2.1 (macOS + Windows + Linux)

All three platforms ship 0.2.1. The Windows artifacts were re-cut from the
v0.2.1 tag on 2026-08-26, so every published bundle — macOS, Windows, Linux —
now carries the 0.2.1 build stamp.

Fixed

Paths sent to a Linux/macOS ComfyUI server were unusable

The plugin rewrote every submitted path to backslashes, assuming the ComfyUI box
is always a Windows storage server. On a POSIX server a backslash is an ordinary
filename character, so every LoadEXR / SaveEXR node failed with
Path not found: \Volumes\silo2\....

The separator style now follows the ComfyUI Server Mount value itself — a UNC
path (\\host\share) or drive letter (Z:\share) yields backslashes, anything
else yields forward slashes. The OFX host and ComfyUI can now be the same Linux
machine, or reach each other across any OS pairing. Trailing separators on either
mount are stripped before splicing.

Added

Every artifact identifies itself

Bundles used to all claim version 1.0.0, so a plugin found on a workstation was
indistinguishable from any other build. That is how a pre-0.1.5 bundle survived
unnoticed in /Library/OFX/Plugins and kept segfaulting Flare on macOS long after
the fix had shipped. From this release every bundle carries its version in three
places:

cat "<bundle>.ofx.bundle/Contents/Resources/aifx-build.txt"
strings "<bundle>.ofx.bundle/Contents/MacOS/<name>.ofx" | grep AIFX-BUILD

On Windows, read the same stamp from the bundle's Contents\Resources\:

Get-Content "<bundle>.ofx.bundle\Contents\Resources\aifx-build.txt"

tools/verify-ofx-abi.sh

Checks built or installed bundles and needs no build tree, so it runs on a
workstation. With no arguments it scans that OS's OFX plugin directories:

OK    DepthAnything3 — 0.2.1 (v1-gl1-cl0-cu0, openfx 96ccd1a)
FAIL  MatteMaMa — legacy build with a SHORT vtable (232B, expected >= 248B)

For bundles predating the stamp it measures the emitted ComfyUI::BasePlugin
vtable, which still identifies the known-bad pre-0.1.5 builds. If a host crashes
the instant you select an AIFX plugin, run this first — it is almost always a
stale bundle from an older install.

Compile-time OpenFX ABI guard

Every plugin translation unit now static_asserts that its view of the OpenFX
Support ABI matches the OfxSupport archive it links against. The vtable-slot
mismatch that caused the crash above is no longer buildable.

Note — artifacts rebuilt from the tag on 2026-08-26

The originally published .dmg contained an APFS volume (hdiutil's default
on a recent build host), which does not mount on macOS 10.12 or earlier — and
fails silently, so double-clicking it appears to do nothing. It is now HFS+,
which mounts on every macOS that can run an OFX host.

The Windows .zip and .exe were added the same day, built from the same tagged
source; every plugin binary in them reports version=0.2.1 (the release script
refuses to package a bundle whose stamp disagrees).

All artifacts now correspond exactly to the tagged source. The SHA-256 values
below are the current files.

Known issue — macOS blocks the installer

The .dmg is not yet signed with an Apple Developer ID, so macOS 15 (Sequoia)
refuses to launch it: "Apple could not verify 'AIFX Installer.app' is free of
malware". Neither right-click → Open nor the Open Anyway button is
offered for an unsigned app. Copy the app out of the read-only DMG and clear the
quarantine flag:

cp -R "/Volumes/AIFX 0.2.1/AIFX Installer.app" /Applications/
xattr -dr com.apple.quarantine "/Applications/AIFX Installer.app"
open "/Applications/AIFX Installer.app"

The .tar.gz contains no app and is unaffected.

Known issue — Windows SmartScreen warns on the installer

aifx-0.2.1-windows-setup.exe is not code-signed, so SmartScreen shows "Windows
protected your PC" on first run. Click More info → Run anyway, or verify the
SHA-256 below and use the .zip instead (copy the seven .ofx.bundle folders to
C:\Program Files\Common Files\OFX\Plugins\).

Upgrading

Delete any AIFX bundles from an earlier install before running the installer —
it does not remove bundles from a different install location, and a stale bundle
left in /Library/OFX/Plugins will keep crashing the host. Then verify:

tools/verify-ofx-abi.sh

(macOS/Linux. On Windows, check each installed bundle's
Contents\Resources\aifx-build.txt reads version=0.2.1.)

Full changelog: https://github.com/Dev-Reepost/aifx/blob/v0.2.1/CHANGELOG.md

SHA-256

4757109377a87414552b91a5e6bc8440e16a5e605af096ca511c865decfac67f  aifx-0.2.1-linux-x86_64.tar.gz
957a4658e1de457dcfc8d4df21c6ed794cd8f2f91dc0569c4213974fd852608e  aifx-0.2.1-macos-universal.tar.gz
c9abdcb7c6079b50e26fb089580a48acde0775084591deecd32762005b754eaf  aifx-0.2.1-macos-installer.dmg
b8663abbbe799c93f366143a937d9a8820bb83f364a063c0b22391721a2d9f28  aifx-0.2.1-windows-x86_64.zip
ad28d6421b8af82d3c8b9a0211c04216acc4498fa145b31cfd3205340d9c45f3  aifx-0.2.1-windows-setup.exe

AIFX v0.2.0 (Linux + Windows + macOS — installers)

Native installers now cover all three platforms — a macOS .dmg wizard, a
Windows .exe wizard, and a Linux install-linux.sh. The project landing page
leads with an OS-detecting Download for your OS button plus manual per-OS
choice.

Plugin binaries are unchanged from v0.1.12 — this release is about the
install experience. The macOS installer's mount-path bug is fixed (it now writes
storage.localMountPath.macos / storage.serverMountPath, the keys the plugin
actually reads). The Linux tarball now ships install-linux.sh. Windows and the
Linux/macOS plugin payloads are carried forward from v0.1.12 unchanged.

Artifacts

Platform	File
macOS installer (wizard)	aifx-0.2.0-macos-installer.dmg
macOS universal bundles	aifx-0.2.0-macos-universal.tar.gz
Windows installer (wizard)	aifx-0.2.0-windows-setup.exe
Windows bundles	aifx-0.2.0-windows-x86_64.zip
Linux bundles + installer	aifx-0.2.0-linux-x86_64.tar.gz

SHA-256

a3ee8248dcdf9e03d6268f738816d070cdc26daffffd274e396b90eee5318576  aifx-0.2.0-macos-installer.dmg
eb8488502b8eeccbe56b433d6bc15b86d33048120acd55911207b092d556b34a  aifx-0.2.0-macos-universal.tar.gz
a77cf676e96b3a8ea040ded9548a696b68488408b5f784128313f39f32db3d0c  aifx-0.2.0-windows-setup.exe
b1c5be211b61526e4d9f2ab3eee7ea87463f885c81f858296932df2abd38fed8  aifx-0.2.0-windows-x86_64.zip
ad3e03e4b914edcec0aa1024ed99ba0ee28c68ea986ecd4ae196a061141cd947  aifx-0.2.0-linux-x86_64.tar.gz

AIFX v0.1.12 (Linux + Windows + macOS)

A load-time regression from the 0.1.8 static-runtime fix: the plugins stopped being detected by Flame on Linux, failing with lib64/libc.so.6: version `GLIBC_2.35' not found.

Ships Linux, Windows, and macOS binaries. This is a Linux-only build fix, so the Windows and macOS builds (rebuilt from the 0.1.12 source) are unchanged in behaviour from 0.1.11.

Fixed

• Plugins load again on glibc 2.34 hosts (Rocky/RHEL 9). The 0.1.8 Resolve crash fix linked both libstdc++ and libgcc statically. The libstdc++ half is what actually fixes Resolve (it stops the host's re-exported std::filesystem::path::_M_split_cmpts from interposing ours). The libgcc half, built on a modern toolchain, baked the unwinder's fast EH-frame lookup _dl_find_object@GLIBC_2.35 into each .ofx as a GLOBAL undefined reference. Rocky Linux 9 ships glibc 2.34 (no GLIBC_2.35 version node), so the loader rejected the plugin and Flame never registered it.

  Now we drop -static-libgcc and keep -static-libstdc++: libgcc links dynamically so the unwinder comes from the host's libgcc_s.so.1 (ABI-stable, interposition-safe), the glibc floor returns to 2.34, and the Resolve fix is unchanged (_M_split_cmpts stays a LOCAL, non-preemptible symbol). Verified across all seven bundles: no GLIBC_2.35 reference, libstdc++ still static.

Added

• Windows installer (aifx-0.1.12-windows-setup.exe). A native Setup.exe wizard, the counterpart of the macOS installer .dmg, shipped alongside the existing zip (same plugin binaries — a packaging + configuration convenience). It collects your ComfyUI server address/port and shared-folder mount paths on a custom page and bakes them into each plugin''s defaults.json while copying the seven bundles into place. A "keep bundled defaults" checkbox skips the rewrite.

Install

Linux — extract and copy the seven *.ofx.bundle directories into /usr/OFX/Plugins/ or $HOME/.OFX/Plugins/, then restart your OFX host.

Windows — run the installer .exe (a wizard that copies the seven bundles into your OFX plugin folder — per-user or all-users — and bakes your ComfyUI server address and shared-folder paths into each plugin''s defaults.json), or extract the zip and copy the seven *.ofx.bundle directories into C:\Program Files\Common Files\OFX\Plugins\ yourself. Then restart your OFX host. Requires the Microsoft Visual C++ Redistributable (x64). The installer is unsigned — if SmartScreen warns, click More info → Run anyway.

macOS — universal binaries (Apple Silicon + Intel). Either run the installer .dmg (a one-shot wizard that copies the seven bundles into ~/Library/OFX/Plugins/), or extract the tarball and copy the seven *.ofx.bundle directories into ~/Library/OFX/Plugins/ or /Library/OFX/Plugins/ yourself. Then restart your OFX host. The build is unsigned — if Gatekeeper quarantines a bundle or the installer, clear it with xattr -dr com.apple.quarantine ''<path>'' (or right-click → Open the installer the first time).

SHA-256

aifx-0.1.12-linux-x86_64.tar.gz       2af7b8c820e5ac0e0fb95c3e06f308c57d984c76bd2ef80e849d78a3f8cbd136
aifx-0.1.12-windows-x86_64.zip        b1c5be211b61526e4d9f2ab3eee7ea87463f885c81f858296932df2abd38fed8
aifx-0.1.12-windows-setup.exe         A77CF676E96B3A8EA040DED9548A696B68488408B5F784128313F39F32DB3D0C
aifx-0.1.12-macos-universal.tar.gz    eb8488502b8eeccbe56b433d6bc15b86d33048120acd55911207b092d556b34a
aifx-0.1.12-macos-installer.dmg       62c812b418504b66104b3b99c4a060d83fc7cb57d93d29aca1352d94c6ea1f00

AIFX v0.1.11 (Linux + Windows + macOS)

A "File exists already" failure surfaced by a real SeedVR2 upscale on DaVinci Resolve (Linux): a multi-minute sequence job that completed the upscale but crashed at save. Root-caused to duplicate in-flight submissions, plus a cache toggle that never did anything.

Ships Linux, Windows, and macOS binaries. The fix is in shared code, so the Windows and macOS builds (rebuilt from the 0.1.11 source) carry the same fix.

Fixed

• No more "File exists already" aborts from the HQ-Image-Save SaveEXR node. That node refuses to overwrite, so a second submission for the same output frame is fatal once the first job has written it. Two holes, now closed:
  • In-flight de-duplication. The output cache check only sees files already written, never a job still running — and a sequence upscale can run for minutes. A second Collect & Submit during that window queued a duplicate that died at save. The submit path now ignores a press while a job for the same output prefix is QUEUED/PROCESSING.
  • Button no longer cancels-and-forgets. Collect & Submit tripped the generic parameter-invalidation branch, which cancelled the job locally only — the server kept running it, wrote its output, and blocked the resubmit. The button is excluded from that branch, and a genuine output-affecting param change now interrupts the server instead.

Changed

• The "Enable Cache" toggle now actually works. It was fetched but never read. Now: cache on serves an existing output and skips submission; cache off deletes any stale output first so SaveEXR writes into a clean slot. Wired into renderAsync, executeWorkflow, and the sequence Collect & Submit.

Install

Linux — extract and copy the seven *.ofx.bundle directories into /usr/OFX/Plugins/ or $HOME/.OFX/Plugins/, then restart your OFX host.

Windows — extract and copy the seven *.ofx.bundle directories into C:\Program Files\Common Files\OFX\Plugins\, then restart your OFX host. Requires the Microsoft Visual C++ Redistributable (x64).

macOS — universal binaries (Apple Silicon + Intel). Either run the installer .dmg (a one-shot wizard that copies the seven bundles into ~/Library/OFX/Plugins/), or extract the tarball and copy the seven *.ofx.bundle directories into ~/Library/OFX/Plugins/ or /Library/OFX/Plugins/ yourself. Then restart your OFX host. The build is unsigned — if Gatekeeper quarantines a bundle or the installer, clear it with xattr -dr com.apple.quarantine '<path>' (or right-click → Open the installer the first time).

SHA-256

aifx-0.1.11-linux-x86_64.tar.gz       c95f5a3a38c45ea9d1fcb8d5ca2384ff0ea81e3cadbe5133edfba95e0cd35f2c
aifx-0.1.11-windows-x86_64.zip        aec6b46ae884671fca5f3dafdba6ca3fe8dfa14be9da4b9ffc99b4809228df6d
aifx-0.1.11-macos-universal.tar.gz    605c96c810a5e05e0148091bd38120bbd79da9684b213869b86c3077c6ee955e
aifx-0.1.11-macos-installer.dmg       8005db84703c1e26c3806e12a619fd38f4b95af8b9ce0fbface5899abe30a581

AIFX v0.1.10 (Linux)

A teardown-time crash fix found while auditing the job lifecycle after 0.1.9. Linux binaries only.

Fixed

• No use-after-free when a plugin is torn down mid-submission. The per-frame async path (submitJobAsync, used by per-frame plugins such as DepthAnything3) launched a detached worker thread capturing the job manager, the ComfyUI Client, and the plugin, then called back into all three. The destructor joined the monitor/sequence-write threads but could not join this detached worker, so deleting the node / closing the project / switching clips mid-submission could dereference freed objects. ~AsyncJobManager now tracks in-flight workers with a counter + condition variable and drains them before its members are destroyed; workers re-check the shutdown flag and bail early (notify under the lock to avoid a CV teardown race). Lifecycle sibling of the client-recreation use-after-free fixed in 0.1.9.

Includes everything from 0.1.9 (client-recreation fix, clean placeholder config) and the 0.1.8 Linux crash fix (static-linked C++ runtime). Supersedes 0.1.9.

Install

Extract and copy the seven *.ofx.bundle directories into /usr/OFX/Plugins/ or $HOME/.OFX/Plugins/, then restart your OFX host.

SHA-256 (aifx-0.1.10-linux-x86_64.tar.gz):

b20e2db86aa941dbd04c49e691f8bd4357b14bc1255aa4f7eb6987f3fcb4edf1