"Error #1 Something went wrong" in Spitfire instrument

Follow

Comments

86 comments

  • Daniel Towns

    I'm hearing a lot of unwanted noise. It's especially noticeable when playing quietly or as the note tails off. I may uninstall because of this. Apart from that, I have no other issues. Reason 10 on Alienware R3 15.

    0
    Comment actions Permalink
  • Daniel Gloor

    Useles Librarie, nothing Work with Eric Whitacre Choir. I tried it 2 Months, now i have buy a Windows Machine, and dthe same Problems, cant use the Lybrarie! All Spitfire Kontakt Libs work fine, but this never work on both Systems. It makes me bad! Sensium

    0
    Comment actions Permalink
  • Ben

    Hi Daniel, sorry to hear that, I have created a ticket with our support team so that they can resolve this for you.

    0
    Comment actions Permalink
  • brian ramsey

    I reinstalled every thing still have message seems if you ignore it it still works as far as I can tell

    0
    Comment actions Permalink
  • Alin Cristian Oprea

    I get this message and kind of figured out why it does appear. I have two ethernet cards (one for internet connection) which I turn off after installing Labs for example and One for Vienna Ensemble Pro). As soon as I turn of the ethernet Card connection on Windows 10 (Cubase1o) the problem seems to appear. I had a similar product from a different developer who is also not using any license key and they explained to me that their protection system is somehow tied to the "ethernet" or "hardware" state of the computer. Maybe its the same problem here ?

    Cheers...

    0
    Comment actions Permalink
  • noel flores

    I'm having problems with spitfire audio labs
    I followed all the steps to reset the program and it didn't work

    0
    Comment actions Permalink
  • marquis rhodes

    wtf

    0
    Comment actions Permalink
  • Aitugan Sarbassov

    What's the reason of keeping folder "Spitfire Audio - LABS" on external HDD, if it still needs to connect to the internet and download the instruments? I don't have the fast internet on my second computer and when I copy folder "Spitfire Audio - LABS" from first computer and choose this folder as my content path, Spitfire Audio App still asks for repairing it via downloading from the internet. Sucks!

    0
    Comment actions Permalink
  • Jeremiah Lyles

    @Aitugan Sarbassov

    You're right. 

    The software does sound wonderful but the configuration in the way it works and installs is problematic for some. Me as well.

    I tried a few other free variations and found that of the many, https://vis.versilstudios.com/vsco-community.html#articulations was one of the better ones that is continually in development by multiple individuals in multiple formats.

     

    Spitfire has similar quality in their sounds but the developers mentioned above along with many others, do not have the installation or execution issues.

    I removed spitfire from my system for similar issues but remain loyal since the quality of their sounds would be a benefit to me.

    1
    Comment actions Permalink
  • andrea irwin

    I have had to repair my entire library multiple times now. I don't know what causes it, but occasionally the entire thing all gets corrupted (or something) all at once. It's happened at least once because the computer bluescreened while the Spitfire VST was loaded in a DAW (although, that probably shouldn't have affected the files themselves, if it was making proper copies in memory...), but I don't know why it's happened the other times.

    Please add a "Repair All" button to the app, and do something to stop the libraries from needing to be repaired so often. This shouldn't even happen, the VST shouldn't be writing over the audio files, so the fact that it keeps occurring is incredibly bizarre.

    3
    Comment actions Permalink
  • Aitugan Sarbassov

    @Jeremiah Lyles thanks a lot man! This VSCO VST is really a good one, enjoyed messing aroung with the sounds.

    Wishing good luck to guys from LABS, keep making your plugin better ;)

    0
    Comment actions Permalink
  • Ben Taylor

    I followed all instructions here to repair and now it only gives me the option to install a 233gb update. I cannot download that with a 40gb cap each month. It's impossible for me to do. I have projects that need to be finished before the 5 months it would take if I could leave my PC on that long... It is impossible.

    1
    Comment actions Permalink
  • Sam Zarei

    If you get error#1 on Windows, please try to use the default location of your DAW for the VST file. in my case, it was Cakewalk and I deleted the soft piano VST file from my preferred location and copied it on Cakewalk VST plugin location (C:\Program Files\Cakewalk\vstpluging)

    0
    Comment actions Permalink
  • Dave Hart

    I found that if you have the LABS installed on an external drive I was constantly getting this error. The install would fix but only for a day and then the error would come up. moreover, if i hit repair all, it would have to download ALL the samples again, multiple GBs!. you might even find that you get caught in message box hell, with a message box repeating and repeating. Anyway, I looked in the logs and it seems that the spitfire audio app seems to get confused as to which filesystem the installation is on.

    I fixed this by creating a special type of link on my windows os, called a directory junction. it's a special type of symbolic link, like a fancy shortcut, that makes all programs think one location is somewhere else. You can then tell Spitfire Audio to install on your c drive but the files will actually end up on your external drive. Having done this the error disappeared and all files loaded correctly.

    Assuming that you've got a Spitfire folder in your my documents and one on your external drive, then go to a command line (Windows Key + R, and type cmd) and then use the following command:
    mklink -J "c:\Users\<username>\Documents\Spitfire\Spitfire Audio - LABS" "E:\Spitfire\Spitfire Audio - LABS"

    replace the username in the first path with your username to get your "my documents" location, and the second path to the relevant drive letter. Now go into the Spitfire App and change the default content path to your my documents path, and relocate the libraries and everything should be fine.

    hope this helps someone, I've been avoiding using LABS for ages because of this, but this seems to get me past the error. 

    0
    Comment actions Permalink
  • Robin Bell

    Well, this is driving me crazy! Installed LABS on my main computer, all works well. Now trying on my Music Studio computer and nothing but problems! Every time I try to load it in my DAW  (Reaper) I get the Error #1 Something went wrong and looking in the logs Spitfire fails to load the patches, presets etc. Tried repair all, resulted in all instruments redownloading and installing. Tried again in Reaper and same error. I cannot afford the downtime to continually download these instruments. They are already installed on my hard disk, so why on earth must they have to down load each time a fix/repair is attempted. I've tried Locate, Reapir individual instruments and Repair All but nothing seems to fix the error.

    And just a minor rant - in the Spitfire App, why are there no scroll bars? I have a temporary mouse problem in that the scroll wheel doesn't work. With all LABS instruments installed, it's impossible to gain access to them all.....

    2
    Comment actions Permalink
  • Dave Hart

    Robin Bell Hi Robin, are you on Windows on your Music Studio computer and if so is the spitfire audio location  on the main drive. Perhaps you have a partitioned drive setup and trying to put the library on the D drive? I had issues for ever and eventually after cgoing through the logs I found when my Labs were on a separate drive like an external it couldn't locate them. see my comment above yours about how I tricked the spitfire audio library to use an external location. I think it's a bug to do with multiple filesystems not being resolve properly.

    wrt to the other issue, the spitfire app on mine does have a scroll bar on the right but it's black on black so hard to see and only shows when I hover over it, perhaps it's there? 

    just another user, don't work for spitfire just trying to help!

    my comment here: https://spitfireaudio.zendesk.com/hc/en-us/articles/360005196074/comments/360000578937

    0
    Comment actions Permalink
  • Robin Bell

    Thanks Dave. I have 2 physical discs on my Music Studio computer, which is running Windows 10 Pro. The Spitfire Audio App is installed on my C: drive (SSD) but my LABS instruments are installed on a directory on my 2nd HDD in D:/My Data/ Spitfire/Spitfire Audio - LABS. The odd thing is that I also have the BBC Symphony Orchestra from Spitfire located on the same HDD in D:/My Data/Spitfire/Spitfire Audio - BBC Symphony Orchestra and that works fine in Reaper. The required sub-directories are present for the Patches, Presets etc. but the log files repeatedly say 'failed to load patch/preset at ......' giving the directory path where the files actually are. I have tried moving the files to a different directory and using the 'Locate' option but to no avail. I also changed the VST plugin directory from my own directory on the D. drive to the default directory on the C: drive but still same errors after redownloading everything. My last attempt will be to create a directory on the C: drive for the LABS stuff and see if that makes a difference....

    And thanks - I've just found the scroll bar on the Spitfire App - poor design to have it black on black....

    I pity anyone on a limited download connection - this system of redownloading everything to fix a simple location error is just too ridiculous....

    0
    Comment actions Permalink
  • Dave Hart

    Robin Bell In my first comment on here I talked about external drives, but partitioned drives will have the same effect (in your case your D drive). I'm sure it's a bug, the log files show that it looks for Labs on the wrong file system after the first installation. I did raise this with them. It's not about your VST locations, it's specifically to do with Spitfires installation only ever looking for labs on the main system drive (usually C).

    As far as I can tell from what I saw and what worked with me is that you have two options

    1. install it on your C drive and it should just work (you're trying that I believe and I'm confident it will fix it)
    2. make LABS think it's on your C drive, when it is actually somewhere else (this is the Directory Junction fix I posted in my first comment here (https://spitfireaudio.zendesk.com/hc/en-us/articles/360005196074/comments/360000578937).

    there's a third option that you wait for Spitfire to fix it, but options one and two get you using the software more quickly, which is the point I guess.

    One more comment on the downloading everything again, it is  ridiculous, but it is also an outcome of looking on the wrong drive. the app can't find anything, not just the presets, but the sample sounds too, so it thinks it has to download everything again. If they fix the wrong-filesystem bug then my suspicion is that the download would be small and only download preset files in the event that they were corrupted

    I really hope they fix it, like I say I have raised it with them and would be happy to show them the logs and what I found.

    Good luck. If you want me to help you with the junction thing then I'd be happy to do so.

     

    0
    Comment actions Permalink
  • Robin Bell

    Hi Dave - yes, I think you're right! I moved the Spitfire directory from my D: drive to my C: drive under 'Users', changed the default settings path to the new directory, then used 'Locate'. On attempting to load the VST in Reaper I still got this #1 - Something went wrong message but looking at the log file it was only 5 instruments that had the failed to locate patches, samples & presets error. I manually moved those out of the way from the Spitfire directory, ran Reaper and the remaining instruments loaded and worked OK. I then tried Repair on each instrument that had the failed to load error previously. On loading the VST all the instruments loaded OK, but with no sound from those 5 which previously had the problem. Checked again and found there were no 'Samples' folders for those, so moved just the Samples folders back to Spitfire and now everything works - for the time being anyway.

    Still strange how everything works OK on my other computer with the Spitfire app on the C: drive and the Spitfire directory on the D: drive (2 physically separate disks). And the BBC Symphony Orchestra worked OK on this computer previously when I was using the D: drive for the Spitfire files.

    At least it works but after so many failed attempts and umpteen re-downloads I'm not impressed! Thanks for your help!

    0
    Comment actions Permalink
  • Alex Fisher

    Im on mac and have done EVERYTHING, from re installing the app, to reinstalling the pug ons packs on the app. NOTHING IS WORKING. I know its free so i cant be too mad but i spent HOURS trying to figure this out and no luck. I deleted everyhting involving spitfire on my computer and tried form the begginign and still run into error #1. Ridiculous. 

    1
    Comment actions Permalink
  • Dave Hart

    Alex Fisher Hey. I had issues for ages with LABS and there definitely seems to be a bug where if you install it on a non-standard drive (e.g. an external drive, or if you have a partitioned hard drive) it will cause error #1 when you next load it up because it always tries to look on the default drive and not where you just installed them.

    Are you perhaps trying to install the libraries on an external drive / separate volume / network location?

    Mine was on windows where I was trying to use an external drive, but on a Mac I guess you have to make sure that you're installing it on the whatever the default filesystem is (the one with Mac OS on it) and not in a separate volume or an external drive. 

    I don't work for Spitfire btw, just had a lot of frustration with the error until I worked out what was going on, so trying to help out others. the libraries are good if you can fix it! 

    1
    Comment actions Permalink
  • Alex Fisher

    Dave Hart, thanks for your help man. Im trying to install it in my "user/me/documents" on my mac. Im not using a usb if thats what your referring to as an external drive. Im not a computer guy either so its been pretty difficult considering its usually just download and bam its ready. I noticed when i try and install the pack it had 2 options, regular download, and HDD, im not sure what hdd is but i tried both and neither worked. and yeah ive heard great things but im not sure its worth it at this point, ive spent like 3 hours on it now. 

    1
    Comment actions Permalink
  • Alex Fisher

    Dave hart, the really annoying thing is that its in my files, and when i open my DAW it comes up on my vst plug ins but like we had mentioned the error 1 still pops up. IM SO MAD lol

    1
    Comment actions Permalink
  • Michael Soutar

    Such good instruments, especially for free, but even after trying all the things mentioned here if I leave it a week or so and come back ALL the instruments need repairing. The files are still all in the default locations etc and having to download them all again just to continue my production work is sub-optimal. :/ 

    1
    Comment actions Permalink
  • Dave Hart

    Michael Soutar frustrating isn't it. this was happening to me for ages but I did fix it and haven't had error #1 since that fix (a few posts on page 3 here) I know you've said that you're using the default locations, but can I just check: if you're on windows and your default documents location isn't on your operating system drive it will go wrong. so if your default location is something like D:\ then you'll have a problem (even if its not an external drive). there's a bug and it needs to be on your main drive.

    I don't work for Spitfire btw, just had a lot of frustration with the error until I worked out what was going on, so trying to help out others. the libraries are good if you can fix it! 

    0
    Comment actions Permalink
  • Michael Soutar

    Dave Hart Thanks! I saw your earlier comments but alas my content location is the default location on my C: drive. The only non-default locations I've set are the VST folders. This just happened to me again and I was producing just last night. I'm basically having to download about 1GB of data every time I launch my DAW

    0
    Comment actions Permalink

Please sign in to leave a comment.