Clear all

[Sticky] UNIFIED LIBRARIES - HOW TO Make & HOW TO Sign Up!  


Owner/Guru Admin
Joined: 1 year ago
Posts: 104
September 3, 2020 12:07 am  

I will fill this out more in the near future but I'm trying to wrap up work on Big Bad Beats!


If you wish to Unify a Patch Library or a Plug-In, here is where the instructions will be placed on how to do that, Naming protocols and other Instructions for Unify. There are some simple rules that must be followed so here is where they will be listed.


RULE #1 Signing Up to Unify a Plug-In or Patch Library:


ADD A NEW TOPIC in this forum with the PlugInGuru Library Name and say in that thread that YOU are doing the conversion. That way others can quickly scan the list and see if a certain library has already been completed. I will put a STICKY on the Library Name to keep it at the top of the list until it's been completed, and then it will be UnStuck. If you start a Topic for Signs of Life - then all discussions about Signs of Life should happen there - if you have ANY questions, email me at


Rule #2 - WHICH Libraries/PlugIns can be Unified?:


DO NOT Unify the patches to a library that is not a PlugInGuru library unless you have talked and received written confirmation that it is okay for you to save their patches, untouched in Unify format AND that they will agree to include a .guru file of the library when it is done that they will agree to include in the download for the library they sell. You can NOT post ANY patches on a public forum unless they are patches YOU created from scratch because they do not belong to you. They are not protected so if you post them, then anybody can now have a copy of that Library that will load in most cases working even if they don't install the library (only Omnisphere sample based libraries won't work since you have to install the library and the samples).

As to PlugIns, please contact me at to discuss this. We're trying to coordinate promotions with various manufacturers so that when we release Unified patches they will provide a way of PlugInGuru customers getting the plug-in at a discounted price if they don't already have it. Also you must check to make sure the PlugIn comes in VST format for both PC and Macintosh. We are not going to release any Unified libraries for a Plug-In that everybody can't enjoy.



Rule #3: Unify stuff:


a) You should set up the Macro Knobs if you're comfortable so that #1 is always Modulation Wheel, Knobs 2 - 6 control parameters in the plug-in and knobs 7-8 add effects found in Unify (Knob 7 for Aux Bus 1 level and Knob 8 for Pump House Depth). If you don't know how to do this, we can help. We can even "inject" an improved knob assignment set up to every patch thanks to the genius of Shane. Contact me if you want help - it's cool if 1 knob controls Attack, Decay, Sustain and Release to get from plucky to Pad etc. Omnisphere is not able to be set up with knob assignments due to the unassigned controller list of 512 parameters that EVERY customer sets up differently but most synths have a pre-set list of parameters that the Macro Knobs have access to.


b) Use a LoudMax with threshold (Thresh / top slider in U.I.) of -3.0db.


c) I'll think of something Later


Rule #4: How to save the Patches:


Here's where the juicy stuff will go on naming conventions, tags, categories.


For Author ALWAYS use "PlugInGuru". This keeps it simple.


Rule #5: BONUS Content

I would suggest not making bonus patches for Patch Libraries. You're basically just creating an existing library in the Unify Patch format for easy accessibility. If you save out the factory patches for a plug-in, then it is cool to add some BONUS patches at the end. Remember to add a "z" to the start of the name (zBPM DRUM - Get Down Boogie) so that it shows up at the end of the Patch List. For BONUS patches, I think it is okay to give yourself patch author credit since you are mixing and matching and editing various patches to make something new. If you use MIDI Files, please make a folder in the Library folder named "MIDI Files" that you place those MIDI Files.


Rule #6: Unique stuff about Omnisphere Libraries & Multis:

If the library contains samples then it MUST be installed into Omnisphere FIRST. Unify calls up the patches, the patch in Omnisphere calls up the necessary soundsources and if they are not installed then the patch will not make a sound. So use the "Install .omnisphere" option to first install the Library into Omnisphere.


These have some special considerations to cover because saving out each patch used in an Omnisphere Multi and redistributing them on individual Layers will make them play MUCH better than if you just call up a Multi and save it as a single-Layer Patch. We'll have more details to add here.



Myself + Shane will fill this out more in the coming week (s). If you have anything you wish to add, please comment below. Please DO NOT post specific Plug-in file information - we are not interested in reverse engineering plug-ins to make this work.


For those of you that sign up and or have already helped convert the numerous libraries that are in Unify format. THANK YOU SO MUCH for your efforts - doing these is a great help to the entire community and makes Unify just that much cooler to own and work with! Once you convert a library, contact me with the name of any patch library you would like to own (Unify libraries not included) and I'll add it to your account as a small token of appreciation for your work. 

This topic was modified 4 weeks ago by PlugInGuruForums

Life is Sound / Sound is Divine

Nico, mj_prod and J Hall liked
Active Member
Joined: 3 months ago
Posts: 12
September 4, 2020 12:20 am  

Can someone point me to a post where I can get a better understanding of what "unify a patch library" means.

I am about to embark on converting my Live set repetoire so that all plugin instruments sit inside a Unify "wrapper".  Now that we can have midi patch selection, that makes Unify ideally sorted to doing this function, as well as incorporating Fx plugins, arp etc for my live set.

Before I do that I just want to make sure that there is not maybe some overlap with what I will be doing to the "unify a patch library"process.  If there is, I'll have a read what everyone is saying about this before starting.





This post was modified 3 weeks ago by Pottz

Member Admin
Joined: 12 months ago
Posts: 1239
September 4, 2020 1:22 am  


Good question. Short answer: No, what you're planning is completely different from "Unifying a patch library".

John will be posting more details soon, but basically, "Unifying" means creating a Unify library in which every patch consists of a single INST layer with some synth plug-in on it, loaded with one patch from some older library for that specific plug-in. The new Unify library is referred to as a "Unified" version of the original library. You still need to own the original library, and the synth for which it was made; the only new thing is that all those patches can be loaded very conveniently inside Unify.

There are basically three kinds of "Unified" libraries. The first is a "Unified Factory library". This is nothing but the factory patches included with synth plug-in X, and we can only publish such libraries if we have the written permission of the plug-in X vendor. Examples are Unified - Knifonium for Knif Audio's KnifoniumUnified - Obsession for Synapse Audio's Obsession, and Unified - Waverazor for Tracktion/MOK Waverazor 2.0.

The second kind of Unified library is a "Unified" version of an existing PlugInGuru patch library for e.g. Spectrasonics' Omnisphere 2. PlugInGuru is permitted to publish these because John is the author of the original patches and hence owns the copyright. Nine such libraries are already available (see the Unify product page), and have been added to the original libraries for Omnisphere 2 and U-He Repro as bonus content.

It's also technically possible to "Unify" a third-party patch library, and you are welcome to do so for any that you own (for your own use) but this third category of library cannot be published without written permission of the copyright owners. Such permission may be granted in a few rare cases, e.g. TetraSonics for Omnisphere 2 | Unify by Tim Dale, and ESC Personal Flavours for Omnisphere 2 (and Unify) by the European Sound Collective, but these are libraries which were originally published by PlugInGuru anyway.