Unifed - Spitfire LABS

@boerni

I have a similar problem. The Spitfire Audio app showed all LABS libraries as "installed", but I looked on disk and many were not there. I suspect the app may be confused because I installed them on another one of my computers. I tried "reset all LABS", which downloaded them all, but they still didn't work. (I suspect "reset" doesn't download the samples.) I'm now going to individually reset and re-install every single LABS library, one at a time. This works, but it's time-consuming and error-prone.

Please take this issue up with Spitfire support. To be honest, I find their content-management system atrocious. I've had nothing but trouble with it.

I'm a new Unify user and forum member. Since I've only owned Unify for a few days, I'm guessing some of my issues may be between the chair and the computer. But I'm getting some of the same Spitfire issues: missing libraries (Choir, Percussion, I'll go through and make an accurate list), and some of the percussion sounds are in the background of the Labs patches (they seem to be a GM layout, appearing on every key, and making the Labs patch unusable). I'll keep digging with this. I'm also getting nowhere with Decent Sampler. I've loaded the .guru file, and about 5 or 6 patches show up (way fewer than I have). But when I choose one of them, it throws an error on every one. Once again, I'll keep digging on this. Thanks for any help you can give! I love Unify - it is truly an amazing tool!

@getdunne 

Hi Shane,

ohhhh thanks !!! That I d'nt know 😊 I do it with the repair function and it works 😎 😎

Cheers Bernie

Thanks for the info, Boerni - I tried the repair function in LABS, and it did not help. The LABS Unified library is now missing the following patches, amounting to dozens of sounds. Autoharp, Bass Guitar, Christmas, Electric Guitar 80s, LA Atmos, Ondes Musicales, Organic Textures, Pipe Organ, Siren Songs, and Synth Strings. When I call up these patches, the Percussion Library in LABS substitutes for the sounds, if that's any clue. 

Just to add to the puzzle, all of the above sounds work just fine when I call LABS up in my DAW(s), which are ACID Pro 10 Suite, and Cakewalk. I am running on an HP Z800 (dual quad Xeons) with 48GB of RAM, Windows 7. Most everything else works. I just bought the BBCSO unified library, and all of the patches work beautifully! 

As I said above, I am a new owner of Unify, so I am plowing through all of my plugins to see what works and what doesn't. Thanks for your help with this!

    Jowry (Joe Bourke)

I'm starting to have some progress with getting various third-party VSTs into Unify - so far I have Magix Independence working just fine (it is quite similar to Unify in many ways, allowing multiple patches, but the interface is very difficult to navigate. Nowhere near as elegant as Unify, but very powerful nonetheless.), Decent Sampler is working (though I haven't gone through all of the patches), and Alchemy, one of my favorites! This is the Camel version of Alchemy, from before the Apple takeover. It was a freebie at some point, and only works with the couple of hundred patches which came with it, but there are some beauties, some by John Lehmkuhl (Astral Choir is a fine example). 

Posted by: @jowry

Just to add to the puzzle, all of the above sounds work just fine when I call LABS up in my DAW(s)

That's unexpected. The only thing I can think of is that you might have LABS presets/samples in more than one location, with one complete collection and another that's incomplete. Another possibility is that you might have a newer version of the LABS plug-in than the one used to create the unified libraries, and something is incompatible. Honestly, I'm grasping at straws here.

It would be really good if you could bring this to the attention of the support staff at Spitfire Audio. They might have some insight based on this observation (which I've never heard before from anyone else).

Thanks for the quick response! I will check out the possibility of there being a second location for the Spitfire VST file. I will check the Spitfire version number and post it here in case that will provide a clue. I will also hop on to the Spitfire support site and give them a heads up as to what's going on. It is odd that the patches are showing up fine in my DAWs, but not in the Unified version. I'm pretty sure all of my LABS files are in the same location, since I have an OS drive, and then an Apps drive, where I install everything - but stranger things have happened. Some plugins install automatically to the C: drive without giving you a location option. 

Thanks to all who weighed in on this. I finally figured it out - although my Spitfire LABS libraries are on my E: drive (where all my apps are installed), somehow Spitfire installed the 64 bit VST3 on my C: drive! So by going in to Unify and scanning the C:/Program Files/VSTPlugins directory (where the LABS (64 bit).dll file lives, all of the missing libraries have shown up! 

This does not mean that the above path will solve the problem for everyone out there (on a PC), but it has worked for me! Thank you again! Now to get on with actually creating something. I will also continue plowing through my other plugins to see what does or doesn't work and post my results. I'm amazed that the old Camel version of Alchemy worked! Maybe it knows that John Lehmkuhl worked on it. 🤔 

I thought John mentioned in a livestream a week or two back that the latest updates to LABS were about to appear, as he had been working on it, but I haven't seen it yet, and it doesn't seem to be in the unified list at the top of these posts - does anyone have an update?

Thanks.

@robertpeveler - I hope to have an update released later this week. They keep adding new libraries to it!

Thanks - agree!  In the UK we say this is like “painting the Forth bridge” - essentially, by the time you complete the task, it is time to start again! Maybe painting the Golden Gate takes equally as long. 

Updated version of the Labs library: https://www.dropbox.com/s/vmca71jy533r09v/Spitfire%20LABS%202022%20Unified.zip?dl=0

NOTE: This library is renamed to "Unified - Spitfire LABS 2022" because I did some house cleaning to the library and some file names were renamed, others (that were duplicates) were deleted. You can delete the original Unified - Spitfire LABS" library if you DID NOT make any edits to patches that you wish to keep.

Enjoy and let me know if you have any issues - I have not made this release public yet.

- John

Hello everyone, thanks to John and Shane for the last update of this library.

For information, there are 3 duplicates in the "Electric Guitars Indie" series.

Cordially.

Spitfire LABS Unified 11_28.zip: https://pluginguru.us4.list-manage.com/track/click?u=10665ca8914073773dda359a8&id=98a987ab97&e=9037c64c9b

I fixed "zPAD - Hayward Platform" (the second instrument was "London Atmos: On the Platform" but should be "London Atmos: 2 on the Platform". I'm going through the "z" patches looking for ones that have percussion replacing a voice. Working on this is helping me learn a lot about Unify. 

Is there a way to go through a library and update all instances where the above problem exists? "zPAD - Dark and Ghostly" instrument 2 also needs the above edit. 

Did Spitfire update the name of "London Atmos: On the Platform" for some reason to "London Atmos: 2 on the Platform? 

I use NotePad++ with a regular expression plugin to do global edits to fix stuff like this in some programs. Is that possible for the above situation?

I also use BeyondCompare 4 when I need to do an edit like above on multiple files. 

I didn't know they changed the name - that's very unfortunate. If you can send the fixed patches to me at unifysuport@pluginguru.com, I'll update the library with these fixed patches.

Hi John,

Will send the updated patches. 

Doug