How to Change the SSD5 Library Folder Installation Location

Superior Drummer's sample engine, SSD5 (Steven Slate Drums 5), is one of the most storage-hungry virtual instruments you'll encounter in a production environment. Its sample library can easily consume 40–50GB or more of drive space, which makes the default installation path — usually your system drive — a real problem for producers working on laptops or machines with smaller SSDs. Changing where that library lives is entirely possible, but the process has a few layers worth understanding before you start moving files.

Why the Installation Location Matters in SSD5

SSD5 separates its two core components at install time:

• The plugin itself (VST3, AU, AAX) — small, typically installed to a standard system plugin folder
• The sample library — large, streamed from disk in real time during playback

Because SSD5 streams samples from disk rather than loading everything into RAM at once, the library folder's location directly affects latency, load times, and playback stability. This is why you can't just copy files and call it done — SSD5 needs to know where the library is, or it won't find its content.

How SSD5 Finds Its Library

SSD5 uses a content path configuration stored either during initial installation or through the plugin's built-in content manager. When the plugin loads, it references this path to locate its .ssd drum kits and sample data.

If the path is wrong or broken — because you moved files without updating the reference — SSD5 will show missing content errors or fail to load kits entirely.

Method 1: Set a Custom Location During First Install 🎯

The cleanest approach is choosing a non-default path at the time of installation:

1. Run the SSD5 installer
2. When prompted for the Library/Content install location, click the folder browser rather than accepting the default
3. Point it to your preferred drive — an external SSD, a secondary internal drive, or any path with sufficient free space
4. Complete the installation normally

This method requires no manual path correction afterward because the plugin registers the correct location from the start.

Method 2: Move an Existing Library and Update the Path

If SSD5 is already installed and you want to relocate the library:

1. Locate the existing library folder — commonly found at:

   • Windows: C:Users[YourName]DocumentsSteven Slate AudioSSD5
   • macOS: /Users/[YourName]/Library/Application Support/Steven Slate Audio/SSD5/(Actual paths may vary depending on your original install choices)

2. Copy or move the entire library folder to the new destination — an external drive, a secondary SSD, or any preferred path

3. Launch SSD5 within your DAW — it will likely show a content-missing warning

4. Use the Content Manager or Preferences panel inside SSD5 to repoint the library path to the new location

5. Allow SSD5 to scan and reindex the content

⚠️ Move the entire library folder intact, not individual subfolders. SSD5 expects a specific folder structure. Partial moves cause persistent content errors.

Method 3: Use the Steven Slate Audio Application or License Manager

Depending on your version and how you purchased SSD5, the Steven Slate Audio application (sometimes called the "iLok License Manager" companion or a dedicated download manager) may offer an option to download library content directly to a custom path. If you haven't yet downloaded the full library content, specifying the target drive through this tool is often simpler than moving files after the fact.

Check whether your installer or download manager has a "Choose Download Location" step — not all versions surface this in the same place.

Drive Type and Performance Considerations

SSD5's streaming engine is more forgiving than some orchestral libraries, but high simultaneous voice counts and complex patterns can stress slower drives. The drive's sustained read speed matters more than peak speed for this use case.

Variables That Affect Your Specific Setup

How well this process goes — and which method makes the most sense — depends on factors that vary considerably from one system to the next:

• Operating system and version — file paths and permission structures differ between Windows 10, Windows 11, macOS Ventura, macOS Sonoma, and older versions
• SSD5 version — the content manager interface has changed across updates; older versions have fewer GUI options for path repointing
• How SSD5 was purchased — direct from Steven Slate Audio, through a bundle, or via a third-party bundle can affect which installer or manager tool is in play
• Drive format — macOS and Windows handle drive formatting (APFS, exFAT, NTFS) differently, and cross-platform drives introduce additional variables
• DAW behavior — some DAWs cache plugin paths or scan for content at launch, which can interact with a recently changed library location

A producer running SSD5 on a modern Windows workstation with a dedicated sample drive will have a very different experience than someone on a MacBook Air trying to point the library at an external drive used across multiple machines. The core steps are the same — but what's smooth on one system can require extra troubleshooting on another. 🔧