Fix: Spitfire Library Not Showing in Kontakt | Audio Support
The Client’s Challenge
A talented composer I work with recently found himself in a particularly frustrating situation—the kind that stops a creative session dead in its tracks. He was meticulously setting up a new system, moving files from Sibelius to a fresh Cubase installation, and was eager to start composing with his newly acquired Spitfire Symphony Orchestra library.
He had done everything by the book. He’d used Native Access to install Kontakt 8. He’d used the Spitfire Audio app to download the vast orchestral library—all gigabytes of it—to his dedicated external sample drive. Everything appeared correct. Cubase was running, his audio interface was configured, but when he loaded an instance of Kontakt, the Spitfire Symphony Orchestra was nowhere to be found. The instrument list was empty where he expected to see violins and brass.
Symptoms at a Glance:
- DAW: Cubase
- Plugin Host: Native Instruments Kontakt 8
- Library: Spitfire Symphony Orchestra
- Issue: Despite being correctly downloaded to an external drive, the library was not visible or selectable within Kontakt.
This is a maddening scenario. You’ve invested time and money, followed the instructions to the letter, and yet the tools you need remain stubbornly out of reach. It’s a classic edge case where the installation is technically complete, but a crucial communication link is missing.
Diagnosis: The Missing Digital Handshake
My initial investigation via remote session confirmed the client’s report. The files were present on the external drive, perfectly organised. Kontakt was installed and running. The issue wasn’t a broken download or a misplaced folder; it was a problem of authorisation.
Think of it this way: downloading the Spitfire library is like having a beautiful, expensive synthesiser delivered to your studio in a locked flight case. You have the hardware, but you don’t have the key. In the world of software instruments, the platform that hosts the instrument (Native Instruments’ Kontakt) needs proof that you have permission to use the third-party library (Spitfire Audio).
The Core Conflict
The problem was a missing registration step. While the client had downloaded the library via the Spitfire app, the vital Native Access serial number provided by Spitfire upon purchase had not been added to the Native Access application. This serial number is the ‘key’ that authorises Kontakt to ‘unlock’ and display the Spitfire library. Without it, Native Access doesn’t know the library exists, and therefore, neither does Kontakt.
This is not user error. It’s a common point of confusion in a multi-layered ecosystem where different companies’ products must work together. The client had followed Spitfire’s instructions, but this one crucial cross-platform step was the missing link.
The Fix: Completing the Authorisation Chain
The solution was straightforward once the diagnostic was clear. We simply needed to introduce Spitfire to Native Instruments officially, using the digital key the client already possessed.
Locate the Serial Number
We searched the client’s inbox for the original purchase confirmation email from Spitfire Audio. This email contained the crucial serial number specifically for Native Access registration.
Register in Native Access
With Native Access open, we clicked the ‘Add a serial’ button and pasted in the number from the email. This immediately initiated the ‘handshake’.
Confirm Library Location
The Spitfire library instantly appeared in the list of products within Native Access. We simply needed to click ‘Locate’ and point it to the folder on the external drive where the client had already downloaded the content.
Relaunch and Compose
After closing and reopening Cubase, we loaded a new instance of Kontakt. There, in all its glory, was the Spitfire Symphony Orchestra, fully installed, authorised, and ready for music-making.
Additional Reflections: The Third-Party Handshake
This case is a perfect example of what I call a ‘contextual conflict’. The user did nothing wrong, and neither Spitfire’s installer nor Native Instruments’ software was broken. The issue arises from the gap between two different companies’ ecosystems.
Spitfire can provide the sample files, but Native Instruments controls the license management for any library that runs inside their Kontakt player. The serial number is the bridge between them. It’s a step that’s easy to miss, especially when you’re focused on downloading huge multi-gigabyte files. Always remember to check your original purchase receipt from any third-party Kontakt library developer for that all-important Native Access serial. It’s the key that unlocks your investment.
If you are seeking professional help because your Spitfire Audio library is not showing in Kontakt, this issue is often caused by a missing serial number registration in Native Access. One-on-one remote support services to resolve complex sample library management and plugin activation issues are available from Audio Support.
