"Error #2 something went wrong" in Spitfire instrument

Follow

Comments

14 comments

  • haha haha

    so please i need help, i got this error but didnt understand anything from the instrucitons so i deleted the app and the files including the vst dll files because i thought redowloading it would solve the problem but now when i redownload i dont get the vst dll files from the download and cant open it as a plugin on ableton because i dont have the vst dll files downloaded

    1
    Comment actions Permalink
  • Elite Artz

    It could also appear meanwhile you're downloading a preset and load it in(LABS) meanwhile installing/downloading

    0
    Comment actions Permalink
  • bib didly

    This happened when I downloaded the newest version of LABs  as it made me update as  I was trying to get the two new instruments that were available, but since then this error has been popping up and I don't know why. I re scaned the vst , the locations of the vst matches ,yet the error still exists.

    1
    Comment actions Permalink
  • Luca Bregolato

    Today I downloaded the "Moon Guitar" and "London Atmosfere", attempted to open those but labs wasn't working anymore. I've tried following the instructions of the video but it didn't work. The patches seens to be the same, I don't really know the problem.

    Hope someone helps me out

    3
    Comment actions Permalink
  • Lucas Alvarez

    I keep getting the same error after doing this steps several times, and the new instruments (London Atmos, Moon Guitar) wont load, but the older ones work without problems

    0
    Comment actions Permalink
  • Willian Ordoñez

    I need help, I have downloaded the "strings 2" library, when I open it the ad appears "error # 2", I have read the instructions and I have carried them out, however I was not successful. Any other solution?

    0
    Comment actions Permalink
  • Alex Petkov

    I had the same error and fixed it by loading a different DAW version of the plugin (Labs x86 as opposed to the previous one I've used, which was VSTi 3). See if this will fix the error for you guys as well.

    1
    Comment actions Permalink
  • nada nada

    Hi Spitz, How do I move my LABS library to a different location (partition) without breaking it (AGAIN... yaawwwn)?

    Errors? I've had 'em all.. two days straight I've been downloading them again and again and again - new accounts, different order of steps, wearing a different pair of socks in case that's the reason they don't work.. (it might as well be, for all the sense I can make of it) so frustrating and not what I've come to expect from Spitfire.

    Works fine in Windows - I can hardly believe it! How did you manage to make something that works a treat in WIN but on MAC I'm shit outta luck?! Must be a world first! Certainly a new experience for me and it's playing havoc with my delicate little sensibilities. Help. ;p

    1
    Comment actions Permalink
  • Zane Parkinson

    I recently started experiencing this error again, but now the Spitfire Audio app refuses to open. I am running macOS 10.14.6 (Mojave). I have reinstalled the app by downloading the .dmg from the website four times now to no avail. 

    0
    Comment actions Permalink
  • Frank Acht

    For me, it is also the same problem again. I would have to install all labs again, but I do not want to do that. I will not use Spitfire labs any more.

    0
    Comment actions Permalink
  • Steve Cload

    I do appreciate they are free and they are really good but if I had dollar for every time I have downloaded, installed, repaired, reset, uninstalled, re-installled, re-downloaded, re-repaired and re-reset and then started all over again I think I might be bordering on being a rich man. Unless the free bit is just a ploy to get us to test the security of the Spitfire App it makes me think twice about ever actually purchasing something. Because if I did and I had this much trouble I would be very sad. Spitfire make great sounds and we are very lucky to get anything for free but surely there must be a better way. It's the quality that keeps us coming back though, so for now I will deal with the mind numbing, inspiration killing, creativity crushing idiosyncracies of a piece of software that was apparently crafted in hell, fashioned in pugatory and released to us demons as a blessing!

    0
    Comment actions Permalink
  • Gordon Watts

    I was having the same issues but, thanks Alex! Loading the Labs x86 version solved it for me.

    0
    Comment actions Permalink
  • Nick Bardoni

    LOGIC USERS

     

    I too struggled with the above instructions. However, after downloading a new Labs instrument and getting the above Error message, I quit Logic and then re-started Logic. This fixed the problem and I was able to then install further (new) Labs modules without further problems.  Hth.

     

    I'm using: MacOS 10.13.6 High Sierra / Logic 10.4.8 on a late 2012 iMac.

    0
    Comment actions Permalink
  • David Wallace

    Cubase Elements & Switch from Discovery to Core

    Upgraded BBC SO from Discovery to Core (thanks for summer sale!!) & opened existing project in Cubase Elements 10.5. Instruments edit showed Discovery and used switch to change to Core. Added SSO String Bases and red indicator showed error #2. Checked all the locations which are fine. Base strings play fine. Is this is false positive and caused by something during the change/switch of SSO instances?

    0
    Comment actions Permalink

Please sign in to leave a comment.