"Error #1 Something went wrong" in Spitfire instrument

Follow

Comments

99 comments

  • Olaf Lambrich

    Was tryin to fix Labs. What i didn´t know was that  "repair"  means downloading all the labs .

     

     

    0
    Comment actions Permalink
  • Marcus Tyler

    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?

    0
    Comment actions Permalink
  • Richard Cooper

    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.

    0
    Comment actions Permalink
  • Kevin Williams

    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.

    0
    Comment actions Permalink
  • Richard Cooper

    Actually, I take it back.  It worked until I downloaded a new sample set (Soft Piano), now it doesn't work anymore

    0
    Comment actions Permalink
  • Paweł Mazurkiewicz

    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.

    0
    Comment actions Permalink
  • Acer Stevens

    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.

    0
    Comment actions Permalink
  • Fredrik Lagnetoft

    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.

    0
    Comment actions Permalink

Please sign in to leave a comment.