"Error #1 Something went wrong" in Spitfire instrument

Follow

Comments

71 comments

  • Scott Mason

    It's working now; it appears that after the initial problems, my pro tools session became corrupt. It is running without problems in a new session. Cheers!

    0
    Comment actions Permalink
  • Jeremiah Lyles

    I have reinstalled my version of Studio One thereafter, I reinstalled the Spitfire sounds but this did not fix the audio problem.

    0
    Comment actions Permalink
  • Eldar Ibrahimovic

    I tried everything posted on this thread with no success...
    Will you try to fix the installer and let us know once it's working?

    0
    Comment actions Permalink
  • andy pawlak

    I fixed it after a right fanny on. If your on windows 10 it assumes you are the computers administrator.
    It places files under the admins user name. So go to users - find the admin name and there will be a spitfire file in there, copy it to your user name. Then make sure All the files are in your vst folder.
    Bingo. It’s fine if you are the admin , but if your not......                that’s the issue.

    0
    Comment actions Permalink
  • Oswald

    Question... anybody has a problem with the 32 bits plugin.... because for me it doesn´t seems to work... I don´t hear any sounds or few chopped sounds, wich is bad for me because I use ableton live at 32 bits

    0
    Comment actions Permalink
  • Ben

    Hello everyone. We understand the frustration for anyone visiting this page for whom the fix does not work and we're working on more descriptive error messages along with fixes for various problems that people are having.

    However, it's very important for me that we get you working, for your sake but also for ours, so that we understand the problems and can fix them for any other customers with the same issue.

    So I implore, I beg you, if the fix listed doesn't work please click on the chat icon in the bottom right of your screen and talk to us - if the chat icon isn't there and you see a "help" icon with a question mark, click that and submit a ticket.

    0
    Comment actions Permalink
  • Wes Deckers

    I do get the error message but when I click it away, can load and play the instrument. When I want to load another instrument, the message pops up again but can, again, be clicked away. Perhaps this might 'work' for others as well.
    Windows 7. Nuendo 8.

    0
    Comment actions Permalink
  • Andy Robinson

    This isn't going to answer everyone, but for those on Windows 10 and are reinstalling LABS, it may help. The "Repair" option did not work for me, but the cog symbol, to the right of the Repair option, gives you 3 options "Repair", "Locate" or "Reset". Using "Reset" reinstalled everything and is now working perfectly. Please note, you will need to do this for each LAB library you have reinstalled. Restart your DAW and fingers crossed. Good luck :-)

    0
    Comment actions Permalink
  • Jeremiah Lyles

    @Andy Robinson:
    I tried that and though the software was reinstalled, the clicking noise prevailed. Spitfire has informed me that there is an issue in the 32bit version.

    0
    Comment actions Permalink
  • Andy Robinson

    @Jeremiah Lyles: Sorry to hear it, I'm running 64bit and it solved my issue. Hope they find a solution for you. Best.

    0
    Comment actions Permalink
  • Jeremiah Lyles

    @Andy Robinson:
    When things like this normally happen, it's usually a programmer error somewhere or the lack of foresight of a programmer.
    The same, or similar can be stated for the Pallette Primary Colors string ensemble. In another forum another member mentioned the software could have run in Kontakt 5.3 or higher with a few changes but they force the end user to use 5.7.3 which results in clicking there as well.
    Unfortunately, that library will not be patched or fixed for 5.3
    Everything's good though. I'll wait for the spitfire fix.

    0
    Comment actions Permalink
  • carl koto

    After reading a bunch of these posts, I deleted the Spitfire Labs folder on my Sample Library drive and let the Spitfire app install it where it wanted to in the first place.
    I thought about moving it but seeing that all 3 instruments are just 1.6G, I just left it where it was.
    Works perfectly and I love the interface.

    0
    Comment actions Permalink
  • George Nikoglou

    even after the update the error message is still there..i tried everything it just doesn't work!!!

    0
    Comment actions Permalink
  • Kirk Kienzle

    I thought these guys were great with their service! The problem with me turned out to be that I had the LABs Folder downloaded in multiple places. Once I trashed all the old folders and then re- installed everything worked fine.

    0
    Comment actions Permalink
  • Marco Iannello

    Apparently, updating the Spitfire Audio app to the latest 1.0.3 version has resolved the error for me. When adding it as a new instrument track, or opening a previous session, I do not get the error message anymore.

    0
    Comment actions Permalink
  • jeff williamson

    So every time you prompt a new fix or even an update it creates a new folder. I now have 10 labs folders for two libraries. Should I be deleting the older folders and just keeping the ones that are newest?

    0
    Comment actions Permalink
  • Joakim Alraek

    I had tried everything, for me what did the trick was something so simple as to right click the shortcut icon for my DAW and choose run as administrator. So for people on windows, just give that a try. Hope it works for others as well.

    0
    Comment actions Permalink
  • Jacob de Graaf

    If you've got problems with the LABS on Mac, check out Sean Thompson's solution - this one really works, especially if you have your audio libraries installed on external disks.

    https://spitfireaudio.zendesk.com/hc/en-us/articles/360005196074/comments/360000406493

    Thanks Sean! :)

    0
    Comment actions Permalink
  • Markus Jansen

    Please have a check in your Download or Install-directory:
    example here:
    D:\Install\Musik\Spitfire-Audio\Spitfire Audio - LABS\Samples\LABS Soft Piano
    Please have a look in the SAMPLES-Subdirectory.
    If there are no files of your favorite instrument, please then have a complete download of LABS Soft Piano again or copy your Sample-Files into this subdirectory.
    Then eventually do your Upgrade via Spitfire Audio Library Manager.
    Then Start your DAW and select your instrument.
    Then it will work.

    0
    Comment actions Permalink
  • Tom Silvino

    Oswald, As of the first week in August 2018 it appears that the problem with LABS 32 bit on PC in Ableton Live is still there. The plugin loads and receives MIDI control but does not react to it correctly. The 64 bit plugin works perfectly. I wanted to reinstall the 32 bit plugin but couldn't find the installer on my HD or on SF website. Where do I get the LABS Plugin installer from? I can't remember! Anyone!...

    0
    Comment actions Permalink
  • Des OConnor

    I am running reaper under windows 10 and needed to perform the repair actions. After repairing all instruments I have had no further problems. The soft piano is wonderful...Thank you.

    0
    Comment actions Permalink
  • Richard Reifenstein

    Had to replace hard drive on Windows 10 64 bit machine. Previously I had no troubles with install and playback of samples. However on new hard drive with fresh install of Windows 10 64 bit, I am running into this error no matter what I try. I've done the Spitfire suggestion of the repair...no joy. I've done the "use locate" suggestion (twice) still no joy. The strange thing is that some of the samples work. I have the soft piano, drums, cello, and string libraries. The drums and cello will still sound regardless of the error. I don't understand what changed from last month to this month.

    0
    Comment actions Permalink
  • Dan Melius

    Windows 10 here, and LABS isn't loading things anymore. It wasn't working, than a repair and update did the trick, now it's not anymore. Here is the logfile. What's up with the \/ going on there?

    **********************************************************
    Labs 1.2.3 --- Build date: Sep 13 2018 time:13:06:46
    Log started: 30 Oct 2018 5:54:18pm

    [30 Oct 2018 17:54:18.927] (tid:000000000000057c) OS:Name : Windows 8.0
    [30 Oct 2018 17:54:18.927] (tid:000000000000057c) OS:Arch : 64bit
    [30 Oct 2018 17:54:18.928] (tid:000000000000057c) CPU:MHz : 3110
    [30 Oct 2018 17:54:19.010] (tid:000000000000057c) CPU:cores : 28
    [30 Oct 2018 17:54:19.010] (tid:000000000000057c) CPU:SSE2 : 1
    [30 Oct 2018 17:54:19.011] (tid:000000000000057c) CPU:SSE3 : 1
    [30 Oct 2018 17:54:19.011] (tid:000000000000057c) CPU:SSSE3 : 1
    [30 Oct 2018 17:54:19.012] (tid:000000000000057c) CPU:SSE41 : 1
    [30 Oct 2018 17:54:19.012] (tid:000000000000057c) CPU:SSE42 : 1
    [30 Oct 2018 17:54:19.013] (tid:000000000000057c) CPU:AVX : 1
    [30 Oct 2018 17:54:19.013] (tid:000000000000057c) CPU:AVX2 : 1
    [30 Oct 2018 17:54:19.014] (tid:000000000000057c) Registering common effects...
    [30 Oct 2018 17:54:19.014] (tid:000000000000057c) Registered 18 effects.
    [30 Oct 2018 17:54:19.016] (tid:000000000000057c) Instance Started
    [30 Oct 2018 17:54:19.016] (tid:000000000000057c) OS:Name : Windows 8.0
    [30 Oct 2018 17:54:19.017] (tid:000000000000057c) OS:Arch : 64bit
    [30 Oct 2018 17:54:19.017] (tid:000000000000057c) CPU:MHz : 3085
    [30 Oct 2018 17:54:19.098] (tid:000000000000057c) CPU:cores : 28
    [30 Oct 2018 17:54:19.099] (tid:000000000000057c) CPU:SSE2 : 1
    [30 Oct 2018 17:54:19.099] (tid:000000000000057c) CPU:SSE3 : 1
    [30 Oct 2018 17:54:19.100] (tid:000000000000057c) CPU:SSSE3 : 1
    [30 Oct 2018 17:54:19.100] (tid:000000000000057c) CPU:SSE41 : 1
    [30 Oct 2018 17:54:19.101] (tid:000000000000057c) CPU:SSE42 : 1
    [30 Oct 2018 17:54:19.101] (tid:000000000000057c) CPU:AVX : 1
    [30 Oct 2018 17:54:19.102] (tid:000000000000057c) CPU:AVX2 : 1
    [30 Oct 2018 17:54:19.102] (tid:000000000000057c) Registering common effects...
    [30 Oct 2018 17:54:19.103] (tid:000000000000057c) Registered 18 effects.
    [30 Oct 2018 17:54:19.104] (tid:000000000000057c) Instance Started
    [30 Oct 2018 17:54:19.111] (tid:000000000000057c) Global Created
    [30 Oct 2018 17:54:19.112] (tid:000000000000057c) SamplePool thread = 0 - Work Thread 0
    [30 Oct 2018 17:54:19.112] (tid:000000000000057c) VoicePool thread = 1 - Work Thread 1
    [30 Oct 2018 17:54:19.113] (tid:000000000000057c) Stream Core thread[0] = 2 - Work Thread 2
    [30 Oct 2018 17:54:19.113] (tid:000000000000057c) Background process thread[0] = 3 - Work Thread 3
    [30 Oct 2018 17:54:19.113] (tid:000000000000057c) Instance loaded: mixGroups=1 auxGroups=1
    [30 Oct 2018 17:54:19.114] (tid:000000000000057c) Modulation Source MAXDATA = 1157
    [30 Oct 2018 17:54:19.114] (tid:000000000000057c) Modulation MIDI Source MAXDATA = 269
    [30 Oct 2018 17:54:19.144] (tid:000000000000057c) Labs : failed to load patch config : E:/VST Libraries/Spitfire Audio - LABS/Patches\LABS Soft Piano\v1.0.3\LABS_Soft_Piano.patches.zconfig
    [30 Oct 2018 17:54:19.146] (tid:000000000000057c) Labs : failed to load preset config : E:/VST Libraries/Spitfire Audio - LABS/Presets\LABS Soft Piano\v1.0.3\LABS_SOFT_Piano.presets.zconfig
    [30 Oct 2018 17:54:19.148] (tid:000000000000057c) Labs : failed to load patch : E:/VST Libraries/Spitfire Audio - LABS/Patches\LABS Soft Piano\v1.0.2\LABS_Soft_Piano.zmulti
    [30 Oct 2018 17:54:19.149] (tid:000000000000057c) Labs : failed to load patch : E:/VST Libraries/Spitfire Audio - LABS/Patches\LABS Soft Piano\v1.0.3\LABS_Soft_Piano.zmulti
    [30 Oct 2018 17:54:19.151] (tid:000000000000057c) Labs : failed to load preset : E:/VST Libraries/Spitfire Audio - LABS/Presets\LABS Soft Piano\v1.0.2\LABS_Soft_Piano.zpreset
    [30 Oct 2018 17:54:19.152] (tid:000000000000057c) Labs : failed to load preset : E:/VST Libraries/Spitfire Audio - LABS/Presets\LABS Soft Piano\v1.0.3\LABS_Soft_Piano.zpreset
    [30 Oct 2018 17:54:19.153] (tid:000000000000057c) Labs : preset and patch parsing took 0.011 seconds
    [30 Oct 2018 17:54:19.153] (tid:000000000000057c) Labs : found 0 patches
    [30 Oct 2018 17:54:19.154] (tid:000000000000057c) Labs : found 0 presets
    [30 Oct 2018 17:54:19.168] (tid:000000000000057c) OS:Name : Windows 8.0
    [30 Oct 2018 17:54:19.169] (tid:000000000000057c) OS:Arch : 64bit
    [30 Oct 2018 17:54:19.169] (tid:000000000000057c) CPU:MHz : 3075
    [30 Oct 2018 17:54:19.250] (tid:000000000000057c) CPU:cores : 28
    [30 Oct 2018 17:54:19.251] (tid:000000000000057c) CPU:SSE2 : 1
    [30 Oct 2018 17:54:19.251] (tid:000000000000057c) CPU:SSE3 : 1
    [30 Oct 2018 17:54:19.252] (tid:000000000000057c) CPU:SSSE3 : 1
    [30 Oct 2018 17:54:19.252] (tid:000000000000057c) CPU:SSE41 : 1
    [30 Oct 2018 17:54:19.253] (tid:000000000000057c) CPU:SSE42 : 1
    [30 Oct 2018 17:54:19.253] (tid:000000000000057c) CPU:AVX : 1
    [30 Oct 2018 17:54:19.254] (tid:000000000000057c) CPU:AVX2 : 1
    [30 Oct 2018 17:54:19.254] (tid:000000000000057c) Registering common effects...
    [30 Oct 2018 17:54:19.255] (tid:000000000000057c) Registered 18 effects.
    [30 Oct 2018 17:54:19.257] (tid:000000000000057c) Setting Preload Buffer Size - 12288
    [30 Oct 2018 17:54:19.257] (tid:000000000000057c) Setting Stream Buffer Size - 65536
    [30 Oct 2018 17:54:19.258] (tid:000000000000057c) Labs: prepare to play
    [30 Oct 2018 17:54:19.331] (tid:00000000000060a4) Transport Reset
    [30 Oct 2018 17:54:19.331] (tid:00000000000060a4) Transport Reset
    [30 Oct 2018 17:54:19.476] (tid:000000000000057c) ERROR #1 : go to : https://www.spitfireaudio.com/error1

    0
    Comment actions Permalink
  • Paul Bird

    very slick install / update process - impressed!

    0
    Comment actions Permalink
  • Florian Lengyel

    I'm running ProSonus Studio 4 Professional under Windows 10 and encountered the same error. Repair did not resolve the trouble. Here's what I think went wrong, at least in my case: if you start a LABS instrument download before the previous one completes, you can get the persistent 'Let's fix it' error. Reinstalling one LABS instrument at a time for each installed instrument (I had downloaded four) resolved this trouble.

    0
    Comment actions Permalink
  • Visegrad Alliance

    Yeah...I'm definitely not spending any dough here. Good luck everyone. F

    0
    Comment actions Permalink
  • Ben

    Hi guys, if you have problems, please contact our support department at spitfireaudio.com/support and they'll get you up and running.

    0
    Comment actions Permalink
  • Jeremiah Lyles

    Contacted support, got the software running but then is stopped for some reason.
    I removed the software until the issues are fixed.
    Some of the sounds are great though.

    0
    Comment actions Permalink
  • Des OConnor

    Its worth persisting. I initially had common problems using Labs but following the corrective instructions which have been issued these problems evaporated and use of the plugins is now smooth and productive.

    0
    Comment actions Permalink
  • Gino Torres

    Thank you for the post update, Spitfire. Unfortunately, despite the troubleshoot, I am still experiencing the error upon launching the plug-in. To get it to work each time, I repeatedly have to fix the error. Hopefully, though, an updated or alternative solution comes out as I really find Spitfire's Labs instruments beautiful.

    0
    Comment actions Permalink

Please sign in to leave a comment.