Unify can't scan Spitfire Audio Plugin

@boerni

The first thing to try is to remove the Yair Elazar Glotman - Speculative Memories.vst3 file from the VST3 folder (normally /Libraries/Audio/Plug-Ins/VST3) and try the scan again. If it runs to completion, then that plug-in is what is causing the scan to hang.

If it still does not run to completion, the problem may actually be caused by another plug-in, and Unify's PlugScanner program just happened to be displaying that name when it got struck. You may want to try removing other VST3 files until the scan completes.

A better suggestion is to scan VST3 files individually, by clicking the Operations button and choosing either "Select plug-in file(s) to scan..." or "Select and scan directly...". Do this in the Unify stand-alone app, not with Unify running in a DAW.

The difference between the two menu items is that the first one ("Select plug-in file(s) to scan...") uses the PlugScanner helper program, but with the second one, Unify itself attempts to load the selected plug-in. Sometimes one will work, while the other does not. I have no idea why either fails; the issues are usually specific to the individual plug-ins.

If you are unable to get the plug-in into Unify's known plug-ins list by either method, I suggest you contact Spitfire's tech-support group for help. They have Unify and should be able to reproduce the issue, and they are also able to contact me directly to discuss their findings.

Hey Shane,

I d'nt have any answer from Spitfire, but it's not only this VST, also Zebra 2 from U-HE crashed during the scan. But it's loaded into Unify well and work without any problem 😆 

All the best
Bernie

@boerni

As I mentioned above, the fact that a given plug-in's name is displayed in the PlugScanner window when it crashes or hangs does not always mean that this specific plug-in is the cause. It may be another plug-in earlier or later in the scan sequence.

Are you testing on a PC or a Mac? Which operating system version? Which version of Zebra2?