If you are using an M1 Mac please click on this link.
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.
- Close your Digital Audio Workstation (DAW) and find your Library Contents Folder in the location you installed the library to.
- Click on the Library folder, and delete the Patches and Presets folders found within.
- 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. If you are using LABS, you should select Repair All LABS.
- 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.
- If there is still an error with your plugin, please contact support by clicking the Help icon below 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.
Comments
115 comments
Was tryin to fix Labs. What i didn´t know was that "repair" means downloading all the labs .
I am using Logic Pro 10.6.0, and I am getting error 1. followed the fix, did not work. I am also getting an incompatible audio units error from logic on startup. Can someone please help?
Snap, I've got Logic 10.6.1, on a brand new M1 MacBook Air. Downloaded the labs app, installed strings, and it fails with this error. No idea why, none of these instructions work.
Same as Richard Cooper.
Everything was working fine for a few weeks with Reason.
I installed the trial of Logic and also at this time the Spitfire app installed a new update.
From that point forward, I see error 1 when trying to use any Spitfire plug-ins. I tried all procedures to try and resolve it. Nothing will fix it.
The logs show that the plug-in is failing to load the preset and patches, but the files are there in the correct places.
No amount of uninstalling, reinstalling, repairing, resetting, etc. will resolve the issue.
I, too, am on a Macbook Air M1.
Not sure if loading the plug-in in Logic somehow broke something or the latest Spitfire Audio app that was updated is causing the issue.
I am leaning toward the latest Spitfire app as I have completely uninstalled the plug-in and data manually. The issue will still persist prior to trying to load the plug-in into Logic.
I opened a support ticket around 3 days ago and still have not gotten any responses.
Kevin, after spending the time to file a very detailed bug, it popped up and suggested this article ... which solved my problem: https://spitfireaudio.zendesk.com/hc/en-us/articles/360017827178-LABS-Beta-for-M1-Mac-Big-Sur-OS-to-Prevent-Error-1?auth_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY2NvdW50X2lkIjoyMTI4MTksInVzZXJfaWQiOm51bGwsInRpY2tldF9pZCI6MTY2NTc0LCJkZWZsZWN0aW9uX2lkIjozNjAxNTk5MDAzMzgsImFydGljbGVzIjpbMzYwMDE3ODI3MTc4LDIwNDM1MDg1OSwzNjAwMTcyNzkwMThdLCJ0b2tlbiI6bnVsbCwiZXhwIjoxNjE2MDE4NDIxfQ.CwXNXhyYkf4mhWg2rT-McAZueLyLUzveBrtx_TV1Xi4
Actually, I take it back. It worked until I downloaded a new sample set (Soft Piano), now it doesn't work anymore
Richard, you are correct. I found a method in this madness in that whenever you install new sample set, you need to replace component again. It's a workaround obviously. What's frustrating is the fact, that it did work perfectly fine up until new Spitfire Audio app update.
Yet again more issues from bbcso core. The new update has given me error #1 almost every time I've booted, this is now the fourth time I've repaired it and I've now been blocked from resetting the library which is the only way that has fixed it over the last few days, and something I've had to do daily. Is this seriously acceptable for working professionals spending hundreds if not thousands of pounds on plugins? Kontakt has never had any issues, yet I'm plagued by problems with spitfires interface constantly.
The latest update broke my LABS plugin completely, no sounds are able to load. I've tried deleting and repairing all packages and I'm unable to get it to work.
Running Big Sur 11.2.1 on a MacBook Air M1.
LABS stopped working after trying to install a new library. Repairing did not help so I've reinstalled everything including the Spitfire app. LABS works now but BBC SO Discovery doesn't load anymore. It cannot load the patches and presets, though the files exist in the target destination. I've tried to reset and reinstall many times but nothing helped.
I'm also using an external drive on M1 Mac Mini running Big Sur 11.2.2. I've just tried to reinstall BBC SO locally, it does not work.
Any ideas are welcome.
I literally can't do anything. I've used Flex for a very long time (please dont kill me) and it sounded good (I SWEAR PLEASE DONT KILL ME I HAVE A FAMILY) at first, but later i've noticed better plugins, and now it just sounds bad. I've started looking for other plugins, and now I found Spitfire Labs. I singed up, scanned the Steinburg folder, and opened the plugin. I was so excited to see how this plugin will be, I bet it will sound really good!
ERROR #1
Some thing went wrong.
That was weird. Oh well, I guess i'll see how to fix it. After finding the folder, for like 2 hours, I did all the steps and opened the plugin again.
ERROR #1
Some thing went wrong.
Seriously?!
Luckily, I had one more trick up my sleeve. I rescanned all of my downloaded plugins. This time I had big hopes.
And guess what? The plugin wor-
ERROR #1
Some thing went wrong.
If I did something wrong, or if I'm just stupid then please let me know. I don't wanna use Flex anymore, and I'm tired of seeing the same error. Thanks!
always and only problems with your software .. go back to kontakt
Money spent on BBC Core Orchestra is thrown out the window. The thing is simple .. either solve the problems or make a refund, a voucher to buy another spitfire product is also fine but with a kontakt system ... I await a quick reply
error 1 error 2 error 5 is becoming a nightmare and once fixed the next day it starts all over again... this is not professional.
For anyone struggling with BBC SO on an M1 Mac, the beta plugin did work for me.
https://spitfireaudio.zendesk.com/hc/en-us/articles/360017698337-BBC-Symphony-Orchestra-Beta-for-M1-Mac-Big-Sur-OS-to-Prevent-Error-1
it was working everiyting with m1 chip , now its not working !!! I don't know what you did but I did delete presets patches and reinstalled those and same issue I have , not one of those aplications its not working now ! you have to fix it ! not even a phone number for solving the problem ! disappointed
Dimitru, you are in the LABS forum. LABS is completely free of charge - you can't expect any support for that by Spitfire Audio. They don't "have to" fix it, at all - but they do help, of course, as they are kind people.. But I don't think they read this forum, you'd better create a request if you need support from them (I've never tried it tbh)
But anyways, have you installed the latest beta for the M1 chips? See my previous post.
I recently got my BBC orchestra discover working. now I tried to use the choir lab but its not working. I have tried the error 1 fixing method posted on the spitfire support page, its still not working. Please help out
Gabor Olah I get what you're saying- nobody should expect support for a free app, but this seems to be a systemic problem with the delivery platform, including paid versions. I really enjoyed BBC SO Discovery and was considering upgrading to the full version, but then it and all the LABS instruments started breaking on every reboot with Error#1, so as it stands I'm definitely not going to drop hundreds of quid on it. It's a shame, because the instruments themselves are fantastic!
Corin, we can agree on that :) It would be nice to see that SA fixes the issue or at least makes a commitment about it.
BBC SO Discovery is actually not a freebie (even if it is extremely inexpensive) so imho you can expect support for that. But I'm afraid SA doesn't read this thread, I haven't seen any commits by them. You can try to submit a request if you want to, you may get an answer from them.
Do you run an Apple Silicon machine like many of us having problems w/ the SA plugin? And if so, have you tries the Beta Plugin as I mentioned above? For me it does work both w/ LABS and BBC SSO Discovery.
Yeah, I actually got the paid Discovery. I'm fully Wintel- the odd thing is the machine where I'm having problems is my new DAW machine with a totally fresh Windows 10 install, and I've tried pretty much every suggestion I can find, including another fresh Windows install on another machine. All my other plugins (Omnisphere, PianoTeq, Superior Drummer, EZMix etc etc) work flawlessly, so for the moment I'll plough on happily and keep an eye on the thread- I'm sure it'll get sorted in an update. Cheers.
I've tryed every suggestion from the first post but nothing works.
I just can't belive this LABS suddenly stopped work from nothing.
And it's not just one effect, it's happenning with all of them.
No new software installed, no new updates.
My computer configuration is good enough to play lots of VST's and VSTi's at the same time.
I'm running Cakewalk from Bandlab on Ruindows 10.
It's not acceptable that Spitfire doesn't do anything to fix it.
The first post is from 4 years ago!
"Just delete these folders and install again (or repair)"
...it works untill you close your DAW and it happens again the next day you open it.
OMG...unbelievable.
Any other new suggestion from Spitfire?
I have a problem with Labs running BBC Discovery but nothing else. I get the standard crash dialog and the lets fix it dialog that does not fix the problem when I choose that route.
ridiculously fast, come on now.
Hello ! I did delete all the patches and presets and installed those again , exactly like in the video , but unfortunately nothing work . And the most interesting thing is I had M1 chip and purchased all the softwares and it was working ! Now I used all my tried to repair and not able to to anything . Its not working guys and please fix that , I spend the money to use it to create not to deal with those types of troubleshooting with no any phone number to have an asist .
Please sign in to leave a comment.