The most common cause is that the plugin has lost track of where the samples are stored. Open the plugin in your DAW. Click the Settings icon (top-left gear icon). Look for the Instrument Path setting.
Browse and select the actual folder containing your library (e.g., AGT_Library for Guitar Taylor or ABPL_Library for Bass Lite). Restart your DAW to see if the changes take effect. 2. Check Permissions (Mac & Windows)
If the plugin can't "read" the folder, it will fail to load even if the path is correct.
Windows: Right-click the Ample Sound library folder, go to Properties, and ensure it is not set to "Read-Only". Run your DAW as an Administrator.
Mac: Ensure you have write access to /Applications/Ample Sound/ and /Users/Shared/Ample Sound/. If you see a red minus sign on the folder, you need to adjust permissions in the Get Info panel. 3. Watch Out for Cloud Sync (OneDrive/iCloud)
Ample Sound specifically warns that if your "Documents" folder is synced to OneDrive, it can break the sample loading process.
Move your "Documents" folder back to its local location or move the Ample Sound library folder entirely out of any cloud-synced directory. 4. Verify Component Installation
Visual C++ (Windows): Ensure you have the latest Visual C++ Redistributable (x64) installed, as the plugin relies on these libraries to function.
Lite Versions: Even "Lite" versions require a sample library to be present. Ensure you didn't just install the plugin (VST/AU) without the accompanying library download.
Standalone Test: Try opening the plugin via the ASHost standalone application. If it works there but not in your DAW, the issue is likely with your DAW's plugin database or permissions. Summary Checklist
The "Loading samples failed" error in Ample Sound plugins is a common technical issue usually caused by incorrect library paths permissions conflicts cloud storage interference
. Users frequently encounter this "Error coded: InstDir Read Error; 7" immediately after installation or after moving their sample folders. Common Causes & Solutions OneDrive Conflicts
: One of the most documented causes is having your "Documents" folder synced to Microsoft OneDrive
. This often prevents the plugin from reading the sample library.
Move your "Documents" folder back to its original local path or ensure the Ample Sound folder is excluded from cloud syncing. Incorrect Library Path
: The plugin needs to be manually pointed to the exact folder where the samples (e.g., files) are stored.
(gear icon) in the plugin interface and use the "Instrument Path" or "Library Path" setting to re-link the folder. Permission Issues (Mac/Windows)
: On newer OS versions like macOS Ventura, the plugin may lack "Write Access" to its own directory in /Applications/Ample Sound/
Manually grant full read/write permissions to the Ample Sound folder or try reinstalling to a different drive (e.g., a dedicated D: drive on Windows). Instance Caps
: Older versions of Ample Sound (pre-2.0) had a hard cap on how many instances could be open simultaneously; exceeding this limit caused subsequent instances to fail sample loading.
Update to the latest version of the software where this limitation has been addressed. Quick Troubleshooting Steps Check Standalone Mode ample sound loading samples failed
executable (standalone version) to see if it loads there. If it does, the issue is likely with your DAW's configuration rather than the plugin itself. Verify Library Download
: Ensure you didn't just install the plugin "installer" but also downloaded and extracted the separate package, which contains the actual audio data. DAW-Specific Patches : For users on GarageBand
, a specific installation patch (shell script) is often required to fix library pathing issues. Vi-Control
This tutorial provides a clear walkthrough for installing and linking Ample Sound libraries to avoid loading errors:
The "Loading Samples Failed" error in Ample Sound plugins is typically caused by the plugin being unable to locate or access its library of files. Use the following steps to resolve the issue: 1. Verify the Instrument Path
The most common fix is manually pointing the plugin to your sample library folder. Locate your samples: Find where you installed the library (e.g., Ample Guitar M Library ). It should contain multiple Set the path: Open the plugin in your DAW, click the (gear icon) on the top left, and use the button to select that exact library folder. Close and reopen the plugin to trigger the reload. 2. Move Out of OneDrive (Windows) folder is synced with Microsoft OneDrive
, it can block the plugin from reading its configuration or library files.
Move the Ample Sound library folder to a local directory (e.g., C:\Ample Sound\
Update the instrument path in the plugin settings as described in Step 1. 3. Check for Administrative Permissions
The plugin may fail to load samples if it doesn't have "Write" access to its own directory. Try running your DAW as an Administrator Ensure you have write access to /Applications/Ample Sound/
. If issues persist, try deleting the folder manually and reinstalling. If you are on a non-admin account, run the "non-admin-install" option provided in the Ample Sound installer. 4. Reinstall the Library Separately
Ample Sound instruments often come with two separate installers: one for the Plugin (VST/AU/AAX) and one for the
Ensure you have actually run the Library installer. The plugin itself is only a few megabytes; the samples are usually several gigabytes.
If you already installed it, try a clean reinstall by uninstalling both and running the installers again, noting exactly where the library is placed. 5. Check Instance Limits
In older versions of Ample Sound, there is a "hard cap" on how many plugin instances can be open simultaneously. If you exceed this limit, new instances will trigger a "loading samples failed" error. Try removing unused instances from your project to see if the samples load. "Loading samples failed" - Ample Sound Forum - KVR Audio
Sounds like you're seeing an "Ample Sound loading samples failed" error. I’ll give concise troubleshooting steps to fix it.
Confirm sample location
Verify files exist and permissions
Run the Ample Library Installer / Re-run activation
Check disk path characters & length
Ensure sufficient disk space and drive health
DAW plugin/rescan steps
Sample streaming / buffer settings
Antivirus or security blocking
Corrupted sample files
Plugin version & OS compatibility
If you want, tell me:
The sound loading sample has failed to load, resulting in an error. This report aims to provide a detailed analysis of the issue.
Do not uninstall the VST plugin itself. Instead:
D:\Ample\ or Macintosh HD\Users\Shared\Ample\). Avoid long, nested folder names or special characters.-log to plugin launch parameters.The "Loading Samples Failed" error in Ample Sound is rarely a sign of a broken product—it is almost always a path, permission, or corruption issue. By methodically checking your file paths, running your DAW as an administrator (Windows) or ensuring Full Disk Access (macOS), you can resolve the issue in minutes.
Once the green light returns and those massive .pak files load correctly, you will remember why you invested in Ample Sound in the first place: the sheer, undeniable realism of their virtual instruments.
When the red letters of "Loading samples failed" (often accompanied by error codes 7 or 14) appear in an Ample Sound plugin, it usually signals a disconnect between the virtual instrument's brain and its body of sound files. This error often turns an inspiring session into a troubleshooting mission, but the fix is typically found in one of these four areas: 1. The Disconnected Library Path
The most frequent culprit is a simple location error. Even if you haven't moved anything, the plugin might lose its way after a drive change or update. : Open the plugin's (the gear icon) and check the Instrument Path . It must point directly to the folder containing the
files. If the path shows "FileNotFound," you'll need to re-browse to the library folder manually. 2. OneDrive and "Document" Folder Interference
Ample Sound instruments frequently store essential data in your computer's "Documents" folder. The Conflict : If your Documents folder is synced to
, it can cause "InstDir Read Errors" because the plugin cannot reliably access files locked or moved by the cloud service.
: Move your "Documents" folder back to its original local location or ensure the Ample Sound subdirectory is excluded from cloud syncing. 3. Missing Library Installation It is a common pitfall for new users to download the plugin installer (the small VST/AU file) but forget the library installer (the multi-GB sample pack). : You see the plugin interface, but it's totally silent.
: Ensure you have downloaded and run the separate library installer found on the Ample Sound download page 4. Permission and Activation Barriers
Sometimes the system itself blocks the plugin from "reading" its own samples.
Getting the "Loading samples failed" or "Error 7: InstDir Read Error" message in Ample Sound can be frustrating, but it is usually a simple fix related to your library path or folder permissions. 🛠️ Top 5 Fixes for "Loading Samples Failed" 1. Re-link Your Sample Library Path The most common cause is that the plugin
The most common cause is the plugin losing track of where the samples are stored. Open the Ample Sound plugin in your DAW.
Click the Settings icon (usually a gear or wrench at the top). Look for Instrument Path or Library Path.
Click it and navigate to where your library is installed (e.g., C:\Users\Public\Documents\Ample Sound or your custom external drive path). Restart your DAW after setting the path. 2. Move Samples Out of OneDrive (Windows)
If your "Documents" folder is synced to OneDrive, it can block Ample Sound from reading files correctly.
Check if your Ample Sound folder is inside C:\Users\[User]\OneDrive\Documents.
If so, move the entire library folder to a local path (like C:\Ample Sound Libraries) and re-link it in the plugin settings as described above. 3. Fix Folder Permissions & Admin Rights
Sometimes the plugin cannot read the configuration files due to permission restrictions.
Run as Administrator: Try opening your DAW (Ableton, FL Studio, etc.) by right-clicking and selecting "Run as Administrator".
Copy Config Files: On Windows, navigate to C:\Users\Admin\AppData\Roaming\Ample Sound and copy the files to your current user's roaming folder: C:\Users\[Your_Username]\AppData\Roaming\Ample Sound. 4. Special Fix for GarageBand (macOS)
GarageBand uses a "Sandbox" system that often blocks third-party plugins from accessing the Documents folder.
Ample Sound provides a "GarageBand Installation Patch" on their download page (often hidden in the "Demo Song Projects" section).
Running this .sh script manually copies necessary config files into the GarageBand container so the plugin can "see" them. 5. Check Your Activation Status
If the plugin isn't activated, it may fail to load the high-quality samples.
Open the Ample Sound Activation Manager (installed separately on your computer).
Ensure your product shows as Activated. If it’s in trial mode and the trial has expired, it will stop making sound.
💡 Pro Tip: If you are using the "Lite" free versions, you still must download and install the Library file separately from the plugin installer. Many users skip the library download, thinking it’s built-in.
For a visual walkthrough on setting your library path and finishing the installation:
This guide focuses on Ample Sound instruments (Ample Guitar, Ample Bass, Ample Metal, etc.) used in DAWs like Ableton Live, FL Studio, Logic Pro, and Cubase.
When you see the error "Loading samples failed", it means the plugin cannot locate the audio files (.wav) associated with the library on your hard drive.
Here is the step-by-step guide to fixing it. Confirm sample location