Notifications
Clear all

Unified - Spitfire LABS (final) - strange behavior?


thsve
(@thsve)
Estimable Member
Joined: 1 year ago
Posts: 132
Topic starter  

There is something strange with most of John's patches in the LABS library. It seems that they work as they should (?), but they are not selected in the browser when you select them unlike the others. If you try to step to next patch with arrow down it jumps to the first patch in the list.

Win 10/Cubase Pro 11/Wavelab 8/Spectrasonics all/NI 13/Izotope MPS2Serum/Cthulhu/MusicLab guitar vsts/etc


Quote
sonyroc
(@sonyroc)
Eminent Member
Joined: 11 months ago
Posts: 45
 

Good evening @thsve, I noticed the problem with John's patches (zXXX ...) which do not have the same name in the browser and the patch. In addition, no highlighting and inability to bookmark it.

See you later and have a good livestream.


ReplyQuote
thsve
(@thsve)
Estimable Member
Joined: 1 year ago
Posts: 132
Topic starter  

Did a full db rescan and it solved the problem.

Win 10/Cubase Pro 11/Wavelab 8/Spectrasonics all/NI 13/Izotope MPS2Serum/Cthulhu/MusicLab guitar vsts/etc


ReplyQuote
sonyroc
(@sonyroc)
Eminent Member
Joined: 11 months ago
Posts: 45
 

Hello, I removed all zXXX patches from the "Unified - Spitfire LABS" library, then I opened Unify, then run a database Rebuild and close Unify. When it reopens, everything seems to work better. Unfortunately, after a while (after more than 20 patch changes) I had a sudden exit from Unify. I have the impression that there is a side effect on the management of the Spitfire LABS plugin with Unify on Windows. I have no problem with "PlugInGuru DiscoverStation".

Am I the only one having these problems?

Added : Hello @Shane, I just saw your answer on SpiteFire LABS, thanks.

"Quite a few people (including John) have experienced crashes with the LABS plug-in. Based on the crash reports I have seen, it appears to be a bug in the LABS plug-in itself. I will be reporting it to Spitfire Audio."

This post was modified 2 months ago by sonyroc

ReplyQuote
transmit
(@transmit)
Member
Joined: 2 years ago
Posts: 74
 

I also had similar problem with highlighting, (WIN 10) 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 in green when clicked,

everything is now very clear and works just as well as all other libraries!

System:
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. …


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@transmit

Thanks for sharing this result. This kind of thing can happen when multiple versions of a library are installed over time, especially when manipulating files directly. Sometimes a clean-out and re-install of only the latest version is the best solution.

Another thing that can happen in these cases is that Unify's patch database gets messed up, and the best remedy is usually to perform a full rebuild, either by using the dedicated button on the Settings view, or holding down ALT (Option on Mac) while clicking the "lightning bolt" at the top of the patch browser.


mj_prod liked
ReplyQuote
SALC
 SALC
(@salc)
New Member
Joined: 2 months ago
Posts: 2
 

MAVC OSX 10.14 .6 UNIFY 1.4

Most of the LABS patches work  but some have the percussion patch mixed in somehow. All the "Trumpet patches do not work. All of those just play the percussion patch? I rebuilt the data base. Any ideas???

Tks

Sal


ReplyQuote
SALC
 SALC
(@salc)
New Member
Joined: 2 months ago
Posts: 2
 

Here is the screenshot


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 
Posted by: @salc

Most of the LABS patches work  but some have the percussion patch mixed in somehow. All the "Trumpet patches do not work. All of those just play the percussion patch? I rebuilt the data base. Any ideas???

The LABS plug-in has its own database, which is managed by the Spitfire Audio app, and it seems this can get corrupted at times. I suspect that's what is happening here, because when LABS tries to load some sound-set that used to work before, it now seems to load the new Percussion set instead.

Try opening the Spitfire Audio app, and check to see if any LABS libraries indicate that they need to be "repaired".

I actually had to delete and re-download the entire series of LABS library folders on my Mac at one point.


ReplyQuote
Erik van Wees
(@erik-van-wees)
Eminent Member
Joined: 1 year ago
Posts: 28
 

I have found LABS directory structures nested within LABS (user error maybe, i did want to relocate the samples from their default; or after their repair) dunno but only when I resolved this it became functional.

 


ReplyQuote
Share: