LABS Unified Final
loving these patches, working my way throgh them, many thanks to all the members who contributed. What an awesome community.
I did find a small problem with zBPM Synth Stardust Zone REP
errors loading Unify preset
Loading VST plugin "Unify"
BPM Synth Wave Prophet Level 1
If you load it manually it is a great sounding patch, many thanks REP
ps and zPad Whale Sanctury REP
Thank you for the feedback. I've passed this on to John.
It appears that patch was made by loading the VST version of the Unify plug-in, a practice we now actively discourage. You should always load the "built-in" Unify plug-in. It's more efficient and compatible.
Thank you for finding this one - I will release 1 more update in a few days with the various errors you guys find that I missed!
Life is Sound / Sound is Divine
many thanks for the quick response.
I load Unify manually and search for the plugin patch (title name on Layer) then save, hope that is OK
again, loving the updated patches.
Here's the buggy patches I noticed:
zBELL - Frozen Spaces - REP (wrong Unify) zBPM KEY - Sparkling Ghost Piano SW (wrong LABS) zBPM PAD - Organ Pulse Pad - REP (wrong Unify) zBPM SPLIT - Reflection GP (1 Octave too low) zBPM SYNTH - Stardust Zone - REP (wrong Unify) zGTR - Guitar and Dulcimer Echoes - REP (wrong Unify) zGTR - Space Dulcimer - REP (wrong Unify) zGTR - Strums of Memories - REP (wrong Unify) zKEY - Harp and Piano - REP (wrong Unify, extra space in patch name) zKEY - Cyclosa Piano Pad - REP (wrong Unify) zKEY - Ethereal Keys of Pluto - REP (wrong Unify) zKEY - Organ Heaven - REP (wrong Unify) zPAD - Choral Flutes - REP (wrong Unify) zPAD - Mountain Snow - REP (wrong Unify) zPAD - Whale Sanctuary - REP (wrong Unify)
In addition, while going through all the z patches, Unify crashed at least half a dozen times - each time when attempting to load the next patch. Other than that, I never figured out an obvious pattern. So I wasn't able to identify a repeatable test scenario.
Experienced with Unify 1.3.2 Standalone on Win10 (20H2 / Build 19042.867 ) Unify library data stored on Samsung NVMe SSD.
Cubase 11 Pro, Win 10 Pro (x64), several different midi controllers
@getdunne Hi Shane, I have different issue with Labs since installing new patches .
They play ok but selected patches don't stay highlighted in the menu bar
zkey Baby Ice Queen
zkey I the Quite of the Day
zkey Stereo Buddies
zpad Strawberry Trumpets
zBPM DRUM 1 Knob 8 Skip Grooves
zBPM DRUM Chill Get Down
zBPM PAD Toybox Laboratory
z GTR Little House on the Prarie
zGTR Love Plucks a Trembling
zKey 3's Company
I also had similar problem with highlighting of selected patches, then I deleted all data and patches from folder " Spitfire LABS Unified Final" in the main folder, then reinstalled everything again completely and re-read....
now all patches are highlighted green when you click on them, everything is now very clear and works just as well as all other libraries
WIN 10 Intel Core i7-10700K CPU @ 3.80GHz, 64 GB RAM, SSD 970 EVO Plus 2TB, USB C 3.2 - Studio One 5
Motif XF, Roli Seaboard Rise, QuNexus, MASCHINE JAM, Presonus ATOM, Wavestate, Presonus Faderport 8 uvm. …
Ok I'll try that, Thanks
@transmit Hi, I deleted Spitfire LABS Unified Final" and reinstalled and it's still not highlighting the selected patches?
Try to do a total rebuild of the db. Open the browser, select ”All libraries” and alt+click the lightning icon (opt in Mac?). That did the trick for me.
Win 10/Cubase Pro 11/Unify/Wavelab 8/Spectrasonics all/NI 13/Izotope MPS2Serum/Cthulhu/MusicLab guitar vsts/BIAB 2022 etc
I have been testing just the "z" patches in the Spitfire unified library with stand-alone Unify in Windows 10. Rebuilding the entire database resolved the problem of selected patches not showing a highlight. However, as I slowly click down the list of z patches, Unify abruptly vanishes from my screen. The crash is not tied to any particular patch (that is, when I re-start Unify and go to the patch associated with crash the last time, it does no cause a crash). The crash can happen immediately (first z patch did this at least once), or after selecting a sequence of patches (two to twelve or so). This has not been a problem present in other libraries. Just wanted to chime in that the problem exists. Let us know when the next version gets posted.
I'm working with Spitfire Audio's technical staff right now, to resolve what seems to be a bug in the LABS plug-in.
From what you have written, it sounds like the crash only occurs when going from one "z" patch to another, not when switching among the non-"z" patches. This could be a VERY important clue. It might be related to patches that use ONE instance of LABS, vs. patches that use more than one. I will bear this in mind during my testing.
Can anyone else confirm or deny that the LABS issue is related to multiple LABS instances?
I just tried switching between the non-z presets in Unified Spitfire LABS on standalone Unify 1.3.2 and also the latest Unify beta using the "next preset" button in Unify.
Crash/exits occurred in both 1.3.2 and the latest beta after switching between a number of patches. It didn't seem to be specific patches as the crashes occur on different patches every time.
To confirm; I didn't load any z patches at all. I am using the latest Unified LABS library, the latest SA plugin and all 35 LABS libraries are installed. I also did a full database update in Unify this morning (which didn't change the crash behaviour with LABS).
@getdunne I had not done much testing of the non-z patches in the LABS unified library. I just went back, and was able to select a large number (90 or so) of patches sequentially from the top. No crashes that far, very unlike the z patch section. HOWEVER, when I got to modular pianos, Unify suddenly vanished from my screen. So the issue is not limited to the z patches, just much more frequent there. On re-opening (still stand-alone), I was able to resume selecting patches starting mid-list with mandolin patches. On reaching the second modular piano patch, Unify vanished again. Went back and was able to select the second modular piano patch fine, then tried the first one and had an immediate crash of Unify again. I have not been rebooting between crashes. Not sure how much testing I'll be able to do, but thought this worth reporting. Maybe I should try some non-LABS libraries too. Hmmmm.
This is VERY useful feedback. Thank you. I'm sorry you're having to struggle like this. Hopefully we can get to the bottom of it soon, so you and everyone else won't have to struggle anymore.
@getdunne Not a huge issue overall since I can still use many other patches. I rebooted then went to Unify standalone with no other major programs running. Went to Plugin Guru Cloud City V1. Decided to navigate patches with down arrow instead of mouse click to remove another source of variability. Was able to get through the patches with no Unify crash. Down arrow stalled out several times when a duplicate patch existed (could not select the duplicate with mouse click or arrow method). Then went to the Unified - Spitfire LABS and resumed down at the mandolin patches. Used down arrow to select next patches. Mandolin patches fine again, but with the very first modular pianos -01 granular.... , Unify vanished again. So definitely not limited to z patches, but so far seems to be something with the LABS library. I just now reopened Unify and LABS and mouse clicked on the first modular piano patch with no crash. Down arrow to next modular piano patch instantly reproduced the crash. So a little less inconsistency, maybe.
If you would like to suggest other testing I could do that might isolate the issue better, let me know.
If Unify is crashing when switching from patch A to patch B, we need to find out if the crash happens when tearing down A or when loading B. My guess is the former, and if that's the case, then what matters is not which patch you're attempting to load, but which already-loaded patch you're attempting to replace.
I was just trying the LABS plugin in Cantabile (free version I use for doing quick plugin tests). After using the LABS UI to select next patch a few times it also crashed but generated a crash dump (mdmp file and a few logs). Would that be of any use (maybe to Spitfire Labs)?
@getdunne Getting inconsistent results still. Reopened Unify, went to LABS library, mouse clicked on modular pianos 12, then up arrow to select all the modular piano patches with no crash. After selecting the mandolin patch next in line, tried going back down the list. Got through all the modular piano patches with no crash. So this does not reproduce immediate preceding patch as being culprit.
Tried again starting just below the modular piano 12 patch and using down arrow to select sequentially. First try of this produced a crash on reaching the OPIA - Bass Synth Bend patch. Tried exactly the same thing again but no crash on reaching the OPIA patches. Crash waited until reaching one of the Scary Strings patches. ON reopening, starting just above scary strings and cycling downward does not make a crash in any of the scary strings. I tried going progressively further up the list (1 higher, then two, etc. gave up at 10 higher) and then arrowing down through the scary strings, again with no crash. I then arrowed further down and got no crash until the second z patch. Hope the description is understandable.
My experience so far has been that Windows crash-dumps are gigantic and pretty much useless to me. If the file size is hundreds of megabytes, just junk it. If not, go ahead and zip/attach the crash dump here, and I'll figure out if I can use it.
I have just completed a bug report for Spitfire Audio, where I provide a trivial sequence of operations that seems to crash any host, every time. This should help them to track down the cause.
If anyone is interested, the steps are:
- Create an instance of LABS (VST or VST3)
- Open its GUI, load "Opia: Sub Bass", close the GUI again
- Delete the instance.
I actually confirm, I myself am also completely stuck on a reaper project one track of which contains a LAB zbpm split "action this day" patch. Reaper is completely blocked when I open it.
I can't even delete the affected track from the project. Reaper immediately closes at the slightest manipulation. I'll put it in the trash.
In stand alone mode when I select this patch and switch to another, Unify closes immediately.
WIND 10 Reaper 6 Kronos / Omnisphere 2.8 / Keyscape / Stylus / Ravenscroft / Spitfire Originals collection & BBC SO CORE & ABBEY ROAD 2 & FROZEN STRINGS , Arturia Pigments , Rapid Parawave ,Plasmonic, Surge ,Flow motion,Pianoteq pro,Memorymode,Eight voices,Dreamsynth,Lion,Royal Albert hall Organ
Please report these issues to Spitfire Audio, and say this is in connection with Ticket number #169679.