How To Import Autochroma Banks
Autochroma banks expand your generative visual palette by introducing curated color palettes, custom gradients, and algorithmic texture profiles directly into your animation workspace. Successfully importing these preset packages requires navigating specific directory structures, ensuring version parity between the preset file and your host software, and refreshing your local cache to prevent missing asset errors.
Pre-Operation & Initial Setup Requirements
Before initiating the import process, you must verify that your working environment meets the minimum software specifications and that your asset files are correctly formatted. Autochroma operates as an advanced procedural color manipulation engine, meaning that improperly formatted zip archives or legacy preset variations can result in silent import failures or unrendered parameter nodes.
- Essential Tools and Assets: An active installation of the Autochroma plugin, administrative read-and-write permissions to your host application directory, and the target Autochroma bank files (typically ending in the proprietary
.achromextension or packaged within verified.ziparchives). - Prerequisite Knowledge: Familiarity with your operating system's hidden file directories, understanding of file path hierarchies, and basic competency in managing third-party plugin user data folders.
- Budget and Time Benchmarks: Zero financial cost for the import process itself, with an estimated duration of two to five minutes depending on the volume of preset banks being transferred.
Step-by-Step Autochroma Bank Import Workflow
Step 1: Locate and Prepare the Target Directory
Navigate to the root directory where your host application or the Autochroma plugin stores its user data and preset libraries. On macOS systems, this is typically located within the User Library under Application Support, while Windows users will find the corresponding path inside the AppData Roaming directory. If a dedicated banks folder does not yet exist within the Autochroma sub-directory, you must manually create a new folder and designate it exclusively for custom color banks.
Pro-Tip: Always extract compressed
.zipfolders to your desktop first to inspect the file contents; dragging a zipped archive directly into a plugin directory will cause the host application to ignore the asset files entirely.
Step 2: Transfer and Organize the Preset Files
Copy your unzipped .achrom bank files or structured preset folders and paste them directly into the newly designated Autochroma banks directory. Ensure that you maintain the folder hierarchy provided by the original creator, as flattening nested directories can disrupt relative color reference paths and algorithmic mapping rules within the plugin interface.
Warning: Do not alter the file extensions of the preset banks. Renaming file suffixes from
.achromto standard text or image formats will corrupt the data container and render the bank unreadable by the plugin engine.
Step 3: Initialize the Host Application and Refresh Cache
Launch your primary digital content creation or video editing suite, open a project composition, and load the Autochroma effect onto a test layer. Access the plugin dashboard panel, navigate to the preset dropdown or bank management menu, and click the manual refresh or rescan cache utility button to force the software to index the newly added files.
Step 4: Verify Bank Integrity and Parameter Mapping
Select the newly imported bank from your preset dropdown menu and apply several individual color palettes and texture profiles to a test graphic element. Check the parameter readouts to ensure that all procedural nodes, gradient stops, and blending modes translate accurately without throwing error dialogues or displaying flat magenta missing-texture placeholders.
Autochroma Bank Specifications and Compatibility Matrix
| Parameter / Metric | Standard Preset Banks | Custom User Banks | Legacy v1.0 Banks |
|---|---|---|---|
| File Extension | .achrom | .achrom | .achrom or .txt |
| Maximum Resolution | Infinite Procedural | Infinite Procedural | Fixed Bitmaps |
| Color Space Support | Display P3, sRGB, Rec. 2020 | sRGB, Rec. 709, Custom ICC | sRGB Only |
| Minimum Plugin Version | v2.0 and above | v2.0 and above | v1.2 or earlier |
| Manual Refresh Required | No (Auto-Indexed) | Yes (Manual Rescan) | Yes (Legacy Conversion) |
Common Import Failures and Field Fixes
Symptom: The imported bank does not appear in the dropdown menu after launching the software.
- Root Cause: The preset files were placed in the general application plugin directory rather than the specific Autochroma user data folder, or the files remain trapped inside a compressed zip archive.
- Actionable Fix: Locate the exact user data path specified in the Autochroma documentation, extract any zipped archives, and ensure the loose
.achromfiles reside directly inside the designated banks subfolder before restarting your host application.
Symptom: Error notification stating "Corrupted or Incompatible Bank Format" upon loading a preset.
- Root Cause: The bank was exported from a newer, unreleased beta version of the software, or the file download was interrupted, resulting in an incomplete data transfer.
- Actionable Fix: Update your Autochroma plugin to the absolute latest stable release version, or re-download the bank package from the original verified source to ensure file integrity.
Symptom: Colors appear washed out or inverted after applying a newly imported bank.
- Root Cause: A mismatch between the project's working color management profile (such as ACES or native Log) and the targeted sRGB color space of the imported bank.
- Actionable Fix: Adjust the color management input settings within the Autochroma panel to match your project color space or apply a corrective color conversion node downstream in your node graph.
Frequently Asked Questions
Where should I store my Autochroma banks if I share a workstation with multiple users?
You should place the custom bank files inside the shared public documents directory or configure a custom global path within the Autochroma plugin preferences panel. This ensures that every user profile on the machine can access the exact same preset library without needing duplicate file installations.
Can I batch-import multiple banks at the same time?
Yes, you can drop an unlimited number of individual .achrom files or structured parent folders into the designated Autochroma banks directory simultaneously. The plugin will automatically parse and categorize the directory tree the next time you trigger a manual rescan from the plugin interface.
Why are my custom gradient parameters missing after importing a third-party bank?
This typically happens when the bank was created using proprietary third-party color profiling tools or proprietary shaders that your current installation lacks. Verify that you have installed all requisite supplementary asset packs required by the bank creator.
How do I back up my custom imported Autochroma banks?
Navigate to your local Autochroma user data directory, select your custom banks folder, and copy it to an external drive or cloud storage provider. Because these files are lightweight and self-contained, manual copying provides a secure, instantaneous backup solution.
Streamline your motion graphics workflow today by organizing your custom color libraries and unlocking advanced procedural aesthetics in your next project.