Skip to main content

"Error #1 Something went wrong" in Spitfire instrument

Updated over 2 weeks ago

Error #1 usually occurs when the plugin is unable to load the patches and presets in a library. It may be caused by missing patches and presets, or whenever a library is moved to a new machine and hasn't been repaired.

1.png

If you get this message when loading up a Spitfire instrument, please follow the steps below.

This error means that the instrument is failing to find any presets/patches.


  1. Close your Digital Audio Workstation (DAW) and find your Library Contents Folder in the location you installed the library to.

    Screenshot_2020-10-15_at_17.27.31.png
  2. Click on the Library folder, and delete the Patches and Presets folders found within.

    Screenshot_2020-10-15_at_17.28.22.png
  3. Go to the Spitfire Audio App, click on the Library Artwork, and Repair the Library by clicking on the cog and selecting Repair. On the next page, make sure you select the Library Folder as the destination for Repair.

    Repair.gif



  4. Once the repair is complete in the Downloads Tab, close the Application and open the plugin in your DAW. The plugin should now work with the most up-to-date patches and presets.

  5. If there is still an error with your plugin, please contact support by clicking the "Help" or "Chat" icon in the bottom right hand corner of this page and make sure you attach your plugin log in order to assist our troubleshooting:

    Click here to find out how to produce a plugin log.

IMPORTANT - Error 1 issues that are not resolved directly by a repair attempt as above can also be caused by one or more of the below:

  1. The Spitfire app is set to open using Rosetta, and so the Intel/Rosetta specific version of the plugin is being installed, which will not work with a Silicon/Universal DAW.

  2. The library is being installed on an external drive formatted ExFat, which is not supported.

If you are experiencing an Error 1 you cannot resolve with a repair, please check the possible causes above. If you continue to have issues, as above, please contact us with a copy of your latest plugin log for further troubleshooting.

Did this answer your question?