I don't understand something. (Note that this is not a criticism, just a question.) What is the point of unifying some recent VSTs that already have a very effective patch navigation tool (such as U-he, Cherry Audio, Arturia, Native-I, etc.)? Let me give you a concrete example. If you use the lastest unified library of the GX80, this library is not very usable because Unify "seems" to completely reload the VST every time you are changing a patch, which takes 5/10 seconds! Whereas if you change the patch from the internal VST browser, It's instantaneous ! When you're trying to quickly find a sound, this librairie not very usable in Unify. so, other than creating layering sounds, and/or apply new effects on native patchs, what is the interest of creating unified libraries for these lastest VST's ? , given that the VST browser is very efficient and also has a search and tagging tool for favorites as unify ? TIA.
It can be useful if you choose to browse presets by category within all your (unified) libraries, i.e. you can search for the "synth pad" and the results are not limited to just one vst. Also, you've got your macro knobs assigned.
I don't understand something. (Note that this is not a criticism, just a question.) What is the point of unifying some recent VSTs that already have a very effective patch navigation tool (such as U-he, Cherry Audio, Arturia, Native-I, etc.)?
To add to what @robert-p said, this reduces the number of clicks required when adding a VST patch as a new embedded Unify layer.
...this library is not very usable because Unify "seems" to completely reload the VST every time you are changing a patch, which takes 5/10 seconds!
This can be mitigated by setting up layer reuse: https://pluginguru.net/unify/manual/doku.php?id=layer-reuse. Briefly, if you add the line
<PluginRule vendor="Cherry Audio"/>
to your ReuseAcceptRules.xml file, Unify will attempt to re-use instances of all Cherry Audio plug-ins. In testing, we have not yet found a case where this fails.
Because editing XML files can be difficult, I have attached a zipped ReuseAcceptRules.xml file which you can use by simply replacing your existing one.
The random button is another great reason to Unify your VST presets, as well as being able to favorite patches across all VSTs. You can also create library subsets, which helps if you want to search specific instrument types, genres, etc. I personally like Unifying everything - even MIDI VST presets, which I include a copy of Blue Cat connector after in the patch, with a send, so I can send the MIDI from Unify to my DAW instantly.