Mastering Autochroma: The Complete Guide To Importing And Managing Preset Banks

To successfully import Autochroma banks, users must synchronize specific JSON-formatted preset files and their associated audio assets within the plugin’s designated local directory hierarchy. Achieving a 100% success rate in bank recognition requires maintaining absolute file path integrity and ensuring that the host operating system grants the Digital Audio Workstation (DAW) full read/write permissions for the Imagine Research application support folders.

Prerequisites for Granular Library Integration

Before initiating the transfer of Autochroma banks, sound designers must ensure their system environment meets the technical requirements for granular synthesis performance. Autochroma relies heavily on rapid disk I/O to stream grains from samples, meaning that the location of your imported banks significantly impacts real-time granular jitter and spray performance.

Managing these banks involves two distinct data types: the preset metadata (JSON) and the source audio material (typically WAV or AIFF). If these two components are decoupled during the import process, the plugin will fail to recall the sonic characteristics of the bank, resulting in silent patches or "missing file" error prompts.

Essential Gear and System Standards

• Software Compatibility: Autochroma VST3, AU, or AAX version 1.2.0 or higher is recommended for stable bank indexing.
• File Format Requirements: Banks must contain .json files for parameter data and 24-bit or 32-bit floating-point WAV/AIFF files for sample data.
• Administrative Access: You must have "Read & Write" permissions enabled for the System Library or AppData folders to modify the preset database.
• Storage Hardware: A Solid State Drive (SSD) with a minimum sequential read speed of 500 MB/s is highly recommended to prevent grain dropouts during high-density playback.
• Time Allocation: Initial manual setup and indexing typically require 10 to 15 minutes, depending on the size of the sample library associated with the bank.

Executing the Autochroma Bank Import Protocol

The process of importing banks into Autochroma is not handled via a traditional "Import" button within the GUI; rather, it requires manual directory management. This approach provides professional users with greater control over library organization but demands precise adherence to folder naming conventions and file placement.

Step 1: Locating the Global Preset Directory

The first step in the import process is identifying the specific folder where Autochroma scans for user content. This location differs fundamentally between macOS and Windows environments.

On a macOS system, navigate to the following path: /Users/YourUserName/Library/Application Support/Imagine Research/Autochroma/Presets. Note that the "Library" folder is often hidden by default; you may need to use the "Go to Folder" command in Finder (Shift + Command + G) to access it.

On a Windows system, the directory is located at: C: Drive > Users > YourUserName > AppData > Roaming > Imagine Research > Autochroma > Presets. If the AppData folder is invisible, enable "Hidden Items" in the View tab of Windows Explorer.

Step 2: Structuring the Bank Folder Hierarchy

Autochroma organizes its browser based on the folder structure found within the Presets directory. To ensure your new bank is categorized correctly, you must create a dedicated subfolder.

1. Inside the Presets folder, create a new directory and name it according to the bank title (e.g., "Cinematic Textures Vol 1").
2. Open this new folder and create two distinct sub-directories: one labeled "Presets" and another labeled "Samples."
3. Place all .json files provided by the bank developer into the "Presets" subfolder.
4. Move all accompanying audio files into the "Samples" subfolder. Maintaining this internal structure is critical because many third-party banks use relative file paths to locate audio data.

Step 3: Verifying Sample Path Integrity

One of the most common failures during bank import is the "Broken Link" syndrome. Autochroma presets store a pointer to the sample file. If you move the bank after it has been indexed, or if the developer used absolute paths rather than relative ones, you may need to manually point the plugin to the sample source.

To prevent this, ensure that the audio files are never separated from their respective JSON files. If you are creating your own banks for export, always use the "Collect All and Save" mentality by keeping the assets in a unified root folder before distributing the bank.

Step 4: Initializing the Plugin and Refreshing the Index

Once the files are physically placed in the correct directory, you must force the plugin to update its internal database.

1. Launch your DAW (Ableton Live, Logic Pro, FL Studio, or Pro Tools).
2. Load an instance of Autochroma onto a MIDI or Audio track.
3. Open the Autochroma Preset Browser by clicking on the preset name at the top of the interface.
4. If the new bank does not appear, click the "Refresh" icon (usually a circular arrow) or simply close and reload the plugin instance.
5. Select a preset from the newly imported bank. If the waveform display populates with audio data, the import was successful.

Step 5: Setting Default User Folders (Optional)

For power users with massive sample libraries, storing everything on the primary C: or System Drive is often impractical. You can redirect the user library to an external NVMe drive. This is done within the Autochroma global settings menu. By changing the "User Library Path" to an external location, you can simply drop new banks into that external folder, and the plugin will index them upon startup, bypassing the restricted System folders entirely.

Technical Specifications and File Architecture Matrix

The following table outlines the technical parameters that govern how Autochroma interprets imported data. Adhering to these specifications ensures that imported banks do not crash the plugin or cause significant CPU spikes.

Resolving Directory Sync and Metadata Failures

Even when following standard procedures, local system configurations can interfere with the import process. Below are the most frequent failure scenarios encountered by sound designers and their corresponding technical fixes.

Scenario 1: The Bank Folder is Visible, but the Preset List is Empty

• Root Cause: This usually occurs when the .json files are incorrectly encoded or are placed in a subfolder that is too deep for the Autochroma scanner to reach. It can also happen if the file extension has been accidentally changed or appended with a hidden .txt extension.
• Actionable Fix: Ensure all preset files end strictly in .json. Move the files one level higher in the folder hierarchy and restart the DAW. Verify that there are no special symbols (like #, %, or @) in the folder names, as these can break the scanning script on some versions of Windows.

Scenario 2: Presets Load but the Waveform Display is Blank (No Sound)

• Root Cause: The preset is successfully reading the parameter data, but the link to the source WAV/AIFF sample is broken. This happens when the "Samples" folder has been renamed or moved relative to the "Presets" folder.
• Actionable Fix: Manual relinking is required. Click on the sample name within the Autochroma GUI and navigate to the correct folder location on your drive. To prevent this in the future, always keep the "Presets" and "Samples" folders within the same parent "Bank" folder.

Scenario 3: Permissions Error When Copying Files to Application Support

• Root Cause: macOS and Windows 11 have heightened security protocols that prevent third-party applications from writing to the "Roaming" or "Library" folders without explicit administrative consent.
• Actionable Fix: On macOS, right-click the "Imagine Research" folder, select "Get Info," and change "Permissions" to "Read & Write" for all users. On Windows, run your File Explorer as an Administrator before attempting to move the files into the AppData directory.

Scenario 4: Plugin Crashes Immediately After Adding a New Bank

• Root Cause: A corrupted audio file or a malformed JSON string within the new bank is causing the plugin’s parser to fail during the initialization scan.
• Actionable Fix: Remove the newly added bank folder from the directory and restart the plugin. Re-add the presets one by one (or in small batches) to identify the specific file causing the conflict. Often, re-saving a problematic WAV file in a standard audio editor like Audacity will fix header corruption issues.

Frequently Asked Questions

How do I move my Autochroma banks to an external hard drive?

To move your banks, copy the entire Imagine Research folder to your external drive, then open Autochroma and navigate to the Settings menu. Locate the "User Path" configuration and update it to point to the new location on your external drive; the plugin will then re-index the library from that source.

Why does Autochroma use JSON files instead of standard .vstpreset files?

JSON is a lightweight, human-readable data format that allows for easier cross-platform compatibility between macOS and Windows. It also enables advanced users to manually edit grain parameters or modulation assignments using a simple text editor if the GUI is not accessible.

Can I import banks from other granular synthesizers into Autochroma?

No, you cannot directly import banks from plugins like Portal or Quanta because the parameter mapping and engine architecture are proprietary. You can, however, manually import the raw sample assets from those libraries and use Autochroma’s engine to create new, equivalent presets.

Is there a limit to how many banks I can import?

While there is no hard-coded limit to the number of banks, the plugin's browser performance may degrade if you exceed 1,000 individual presets. For optimal performance, it is best to organize your library into smaller, thematic "Collections" and archive banks that are not currently in use.

What should I do if my DAW cannot see the Autochroma plugin after I add banks?

This is likely a DAW-level scanning issue rather than a bank issue. Force a "Rescan Plug-ins" command in your DAW preferences; if the problem persists, ensure that you haven't accidentally moved the actual .vst3 or .component file while you were navigating to the preset folders.

Optimize Your Sound Design Workflow

Now that your Autochroma banks are correctly integrated, you can leverage the full power of granular textures in your productions. Enhance your library further by exploring custom grain window shapes and high-fidelity sample packs designed for complex spectral manipulation.