Ashigrain
Try free
On this page

Troubleshooting

The plugin does not appear

Start with these three steps:

  1. Check that the bundle is installed at /Library/OFX/Plugins/Ashigrain.ofx.bundle (the top-level /Library, not ~/Library). In Terminal:

    ls /Library/OFX/Plugins/

    If it is missing, run the installer again; see Installation.

  2. Check that your Mac meets the system requirements and that your host is not marked Not supported in the host compatibility matrix. Ashigrain needs a Mac with Apple silicon.

  3. Quit the host application completely and start it again. Hosts look for new plugins when they start.

If the plugin still does not appear, follow the instructions for your application below. You may need to refresh its cached plugin list. For further help, contact us with the application name and version.

DaVinci Resolve

  1. Quit and restart DaVinci Resolve. Resolve scans for plugins only at startup.
  2. Choose DaVinci Resolve > Preferences, open Video Plugins in the System tab, and check that Ashigrain is in the list and enabled.

Nuke

Nuke caches the OpenFX plugins it finds in an ofxplugincache folder, by default /var/tmp/nuke-<uid>/ofxplugincache on macOS, where <uid> is your user id (or under $NUKE_TEMP_DIR if you set it). Quit Nuke, delete the folder, and start Nuke again; it rebuilds the cache:

rm -rf /var/tmp/nuke-$(id -u)/ofxplugincache

Nuke looks in /Library/OFX/Plugins and /Library/OFX/Nuke, and in any folder listed in the OFX_PLUGIN_PATH environment variable. Nuke Non-Commercial cannot load third-party OpenFX plugins at all.

Fusion Studio

Quit Fusion Studio completely and start it again. If Ashigrain still does not appear, contact us with your Fusion Studio version.

SCRATCH and Live FX

SCRATCH reads plugins from /Library/OFX/Plugins/ and /Library/Application Support/Assimilator/Plugins, and from the folders in the ASSIMILATE_PLUGINS and OFX_PLUGIN_PATH environment variables. Restart SCRATCH.

Flame

Flame keeps a plugin cache in a file named ofxPluginCache.xml. If Ashigrain is missing, quit Flame and delete that file, or start Flame with the environment variable DL_OFX_PLUGIN_CACHE_ENABLED=0, which turns the cache off.

Flame does not load plugins listed in its ignore list, cf_ofx_ignore_list.cfg, in /opt/Autodesk/presets/<version>/status. Plugins that crashed Flame at startup go there. If Ashigrain is listed, remove its line and restart Flame.

Flame also reads the folders in the OFX_PLUGIN_PATH environment variable. If Ashigrain still does not appear, set it to /Library/OFX/Plugins and restart Flame.

Natron

Natron 2.5 runs only under Rosetta; see Natron only through Rosetta.

  1. In Natron’s preferences, check that Enable default OpenFX plugins location is on, or add /Library/OFX/Plugins to OpenFX plug-ins search path.
  2. Clear the plug-ins load cache from Natron’s Cache menu, then restart Natron.

Silhouette

Silhouette runs only the third-party OpenFX plugins that Boris FX has qualified, and Ashigrain is not one of them. It is not supported there; see Silhouette is not supported.

The image has an “ASHIGRAIN TRIAL” watermark

The watermark appears when Ashigrain is in trial mode. Open About and read the License field to find the reason, then follow the matching steps below.

  • Never activated: activate as described in Activate your licence. One activation covers every host application on the Mac, so you don’t need to activate again in each host.
  • A render node: each Mac needs its own activation, including render nodes. A render node without one renders the watermark.
  • More than 30 days offline: the plugin works offline for up to 30 days after its last renewal, then returns to trial mode. Connect the Mac to the internet and restart your host application; the plugin renews in the background and the watermark disappears. You don’t need to activate again.
  • Moved to another Mac: activating another Mac, or pressing Deactivate next to this Mac on your account page, ends this Mac’s activation at its next online check. Press Activate here to move the licence back.
  • Refunded or deleted account: a refund or an account deletion ends the licence at the plugin’s next online check, and at the latest 30 days after its last renewal. See the Refund Policy.
  • Any other status: contact us with what the License field says.
  • If ~/Library/Application Support/Ashigrain/activation.json was deleted, press Activate again.

Activation still says “Waiting for approval”

After selecting Activate, confirm the matching code in your browser. Until then, the plugin’s License field shows “Waiting for approval”.

  • In DaVinci Resolve, the status field refreshes after you adjust a control. Change a control and restore its value to see “Licensed”. Other applications may behave the same way. The watermark disappears on the next render even before the status refreshes.
  • The code is valid for 15 minutes. If the browser page says the code has expired, press Activate again for a new one.
  • If the browser did not open, check that you have a default browser set in macOS, then press Activate again.
  • If the page says your account has no licence, sign in with the account you bought with, or see Pricing.

Activation fails or never finishes

  • Firewall or proxy: the application you use Ashigrain in must be allowed to make HTTPS connections (port 443) to the Ashigrain website. If you use an outgoing firewall such as Little Snitch, or a company network filter, allow each host application you use Ashigrain in. Activation, renewal and Deactivate all need this connection.
  • Mac App Store edition of DaVinci Resolve: activation is not supported in it. Install the edition downloaded from Blackmagic Design’s website instead.
  • Deactivate says it needs a connection: connect the Mac and try again, or press Deactivate next to the Mac on your account page.

Colours look wrong or too contrasty

Start by matching Ashigrain’s input and output settings to your project’s colour management:

  • Washed-out image or excessive contrast: the plugin’s output mode does not match what follows it. A display-referred output must be the final colour conversion; a scene-referred output needs the host’s own output or display transform left on.
  • Wrong input: the plugin must receive the colour space your images are actually in. Check the plugin’s Input Color Space and Input Gamma against your project or working colour space; see the Color Space fields.
  • Input set to Auto: when the host does not say which colour space its images are in, Auto falls back to an assumption that depends on the host: Linear / Rec.709 in Nuke and Natron, Rec.709 / Gamma 2.4 everywhere else. See Input colour space in Auto. If your images are in another space, set the input by hand.
  • Differences between viewer and render: check that the render uses the same colour management settings as the viewer.

In DaVinci Resolve, the input is usually the timeline colour space, for example DaVinci Wide Gamut/Intermediate or ACEScct, and a scene-referred output needs Resolve’s output transform left on.

The workflow guide describes the supported setups, where to place Ashigrain, and which colour-management settings each output mode needs.

Contact support

If you need more help, contact support and include:

  • the host application’s name and version (and edition, for example DaVinci Resolve Studio or Nuke Indie);
  • your macOS version and Ashigrain version;
  • a screenshot of the node tree or effect stack and the colour management settings.

You can send a diagnostic log instead of a screenshot. Enable Debug log in the plugin, reproduce the issue, then attach ~/Library/Logs/Ashigrain/ashigrain.log. See the parameter reference for the control’s location.