Notifications
Clear all
Topic starter
September 2, 2020 11:07 pm
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 unifysupport@pluginguru.com.
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 unifysupport@pluginguru.com 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.
Life is Sound / Sound is Divine
www.pluginguru.com
September 3, 2020 11:20 pm
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.
thx
This post was modified 3 years ago by Pottz
September 4, 2020 12: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 Knifonium, Unified - 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.
Kendall W Cochran III reacted
September 13, 2020 4:37 pm
Can we not take an existing plugin like Zebra2 and unify the factory patches? We would not be creating Unify patches for anything that the buyer of the 3rd part plugin would have already. Please advise.
mj_prod reacted
September 30, 2020 8:20 pm
Can we not take an existing plugin like Zebra2 and unify the factory patches? We would not be creating Unify patches for anything that the buyer of the 3rd part plugin would have already. Please advise.
This is a very important question, and the answer is quite subtle.
When Unify saves patches, it queries each plug-in for its current state, which the plug-in returns as a blob of binary data, which Unify stores in the patch. In the case of a factory preset for a commercial plug-in like Zebra2, this is effectively a complete copy of the preset, not simply a reference to it. For many plug-ins, the patch would thus load even if the original presets folder were deleted, making the Unify patch an effective substitute for the original preset. The principle of substitutability is an important aspect of international copyright law, i.e., it is no more legal to distribute a (near-)perfect substitute of a copyrighted work, than it would be to distribute the original work.
If you would like to create a Unified factory library for Zebra2, I suggest you ask permission from U-He by posting in their forum on KVR or using the contact form on their web site. I doubt they would refuse, and once you have written permission, there is no legal issue anymore.
September 30, 2020 10:43 pm
@getdunne That makes sense. If I decide to take on the task, I will reach out to u-He for their blessing before sharing. I might do it for myself as an exercise first, to see how it goes. 😉
Topic starter
October 1, 2020 1:16 am
@getdunne That makes sense. If I decide to take on the task, I will reach out to u-He for their blessing before sharing. I might do it for myself as an exercise first, to see how it goes. 😉
Actually, Urs is a friend of mine so if you wish to do this, please let me know and I'll contact him. I actually am pretty certain he would gladly give his blessing. Why? Because you have to own Zebra2 in order for the patches to load. It's just another way to present the patches, but you still have to own the plug-in. I think loading of patches is not possible in the demo version but I'm not 100% certain.
Life is Sound / Sound is Divine
www.pluginguru.com
October 10, 2020 2:50 pm
Working on Beautifully Broken + Bonus, and Signs of Life + Bonus, Hopefully you received MegaMagic Dreams from me.
JeremyH reacted
November 19, 2020 10:12 am
@pluginguruforums John, U-He Diva is probably one of my favourite synths. I could have a go at Unifying the standard library? I would also love a PG Library for Diva (I have Repro Powerpack which is awesome). Have you ever considered doing one?
March 27, 2021 2:58 pm
I almost finished Unifying Rob Papen Punch 2 presets. I have questions:
Is there some way to batch change macro preset in multiple patches? (i still figure out what assignments will be appropriate to control Punch.. so macro can change...)
Should i upload a link here or to send it by mail?
How to add picture to all patches in unified library?
March 27, 2021 4:58 pm
I have a program I use here for batch changes. It's not yet in a state for use by normal people 🤣 , but I can do it. Just set up the very first patch in your library exactly how you'd like all the others, and can do the rest.
When you're ready, zip everything and email to UnifySupport@PlugInGuru.com.
About pictures:
- A single image (.png, .jpg, file name not important) in the Patches folder will be used as the default image for the whole library
- Add a Media folder beside the Patches folder, and put in image files whose names match those of individual patches (the patch file name, not the patch name as shown in Unify -- they can be different), to define per-patch images.
- Image files should ideally be 96x96 pixels exactly.
RO-mix reacted
March 30, 2021 10:27 am
Another aspect.. in MIDI box which is used to play autoloop in Punch, i used midi file. Do MIDI box reference MIDI file on disk, or it saves midi data with a patch? Can it turn out that on other system, file won`t be able to play, because it references to another library location?
PS: I sent unified Punch 2 lib to email.
March 30, 2021 1:22 pm
MIDIBox stores a library-relative path to the MIDI file. If you want to create patches for sharing, use only MIDI files in the library you are creating, OR in the Unify Standard Library (which every Unify user will have).
If you want to use a MIDI file from a different library "X", there are three options:
- If you're OK with your new patch/library being dependent on library X, then go ahead and use it.
- If not, make a copy of the MIDI file and put it into the MIDI Files folder of the new library you're creating.
- You will need permission from the creator of the MIDI file, to distribute a copy.
- If permission is not granted, make something similar yourself (or ask here for help here in the Forum).
From your post above, it sounds like you just needed a basic MIDI file to trigger something in Punch. You may be able to use something very simple, and if you can't create it yourself, explain what you need here and someone will be able to help.
Another option is to use a BlueARP preset instead.
PS I haven't seen your email; these go to John, we are far apart, and he is away right now. Exactly which MIDI file did you use?
March 30, 2021 1:30 pm
@getdunne
Now i understand i can use BluArp for that....or no.. i did not use BluArp because it has only relative note pitch. I just need one trigger note to be able to trigger Autopreview playing in a Punch using ANY key on keyboard. That is why i used simple midi and MIdiBox.
so... i need to change all 925 patches manually now? 🙂
This post was modified 3 years ago by RO-mix
March 30, 2021 1:36 pm
You didn't answer my question: Which MIDI file did you use?
If there is ever a need to make a change to multiple patches, we have tools here for that; let me know before doing manually. In this case, I doubt it will be needed.
March 30, 2021 1:40 pm
You didn't answer my question: Which MIDI file did you use?
If there is ever a need to make a change to multiple patches, we have tools here for that; let me know before doing manually. In this case, I doubt it will be needed.
My own recorded single midi note 🙂 Which was saved in another library (i`m not sure, midi box does not show location). But the same file is in midi folder inside a lib.
March 30, 2021 1:43 pm
I'll ask John to send me your patches, and fix any path issues.
Could you please zip and attach just one patch here (that uses your MIDI file), so I can have a look?
March 30, 2021 1:46 pm
UPD: i removed other midi sources temporarily. Unify loads patches with MidiBox file normally.
March 30, 2021 1:50 pm
Punch 2 patch example
https://mega.nz/file/2D4G1R7L#AhsQvw_1EKJMHV5o8jciJG4WHgatdtiCYF-dIWPCS-o
March 30, 2021 2:22 pm
The MIDI file path is C:/Users/user/Documents/PlugInGuru/Unify/Libraries/Unified - Punch 2/Midi/PUNCH autoplay 4bars.MID.
It looks like you tried to put the MIDI file into your new library, but you put it in a sub-folder called Midi instead of MIDI Files.
No worries -- I can fix this automatically. Please zip and attach PUNCH autoplay 4bars.MID so I can do a quick test, thanks.
March 30, 2021 3:04 pm
Here is full lib. Please, tell me when you download it. Everything is inside.
https://mega.nz/file/6DxWWJzA#DLNoA_S2yHBNbSZLqOrlMzcTcwK32aU7ZG0YjRdNzr0
This post was modified 3 years ago 2 times by RO-mix
March 30, 2021 3:55 pm
Got the download, thank you.
Updated version here: https://www.dropbox.com/s/t9qgyuyvrldia0x/Unified%20-%20Punch%202.zip?dl=0
March 30, 2021 6:25 pm
Is it possible to batch set Gain Level on INST1 layer in this lib to -3.50? I found it is much more appropriate?
This post was modified 3 years ago 3 times by RO-mix
March 30, 2021 6:40 pm
Pretty much anything is possible in batch processing. Make a list of changes you need and I'll do them all at once.
I do have Punch 2, by grace of Rob Papen, who provided the whole suite for our testing. The looping issue you found may be related to another problem which relates to "full-length" notes. In the converted library I sent to you, I had already shortened the note in your MIDI file by one tick. Do you still have the issue with that file?
Please identify one or two patches which have the problem you mention. I'm not about to hunt through the whole library.
RO-mix reacted
March 30, 2021 7:29 pm
@getdunne
I wrote to support. It has deal with Punch 2 "sync to host" function. Being set to "Off" - this problem is gone. Same happens in Reaper also.
I`ll work with library and list changes.
Also i found some hint. If we have loop of 4 bars, one note. When "not off" is sent - sequencer in Punch restarts after 4 bars. But when i set same midi file to play just for 2 bars - whole sequencer plays and correctly stopped when triggering note sends "note off"
This post was modified 3 years ago 3 times by RO-mix
getdunne reacted
February 5, 2022 5:02 pm
Hi guys, i don't know if i'm at the right place but, i'm a bit confuse cause i dont find the info anyware.
I try to find a way to tune Unify in 432hz instead of 440Hz....
I can do it in Omnisphere (it's call Master Tune option) but don't find it in Unify Vst.
Can you help me with that?
than you
February 5, 2022 5:18 pm
I try to find a way to tune Unify in 432hz instead of 440Hz....
You can't "re-tune" Unify itself, because Unify is a plug-in host, not an instrument.
February 5, 2022 5:41 pm
@getdunne ok so can I re-tune the instruments loaded in in unify?
like a cello patch?
thank you for your help
February 5, 2022 6:06 pm
because Unify is a plug-in host, not an instrument.
It's more like a Multi-Instrument to me. And it has a keys.
I would try to permanently pitch everything down using "pitch bend" message. A calculation is needed to find out the exact amount..
.. and then, somehow, create an offset for the pitch wheel itself.
February 5, 2022 6:30 pm
@getdunne ok so can I re-tune the instruments loaded in in unify?
Individual instrument plug-ins may support some kind of master-tuning option (many do not), but this is not something that a host like Unify can control. You have to do it in each plug-in individually.
Unify's built-in Guru Sampler instrument does not have a master-tuning feature. We may add one in future.
February 5, 2022 6:36 pm
I would try to permanently pitch everything down using "pitch bend" message. A calculation is needed to find out the exact amount..
.. and then, somehow, create an offset for the pitch wheel itself.
Check out Fluid Pitch by Pitch Innovations and MicroToner by Taqsim. Note that every single instrument plug-in must also be set to the same pitch-bend range (e.g. plus or minus 2 semitones) for such tricks to work.
Robert.P reacted
February 5, 2022 10:48 pm
Just came to mine mind, that in 1976 J.M.Jarre was using Sellotape to make his drum machine play two rhythms at the same time. The tape can also be used to lock the pitch wheel position.
February 6, 2022 1:15 am
If we are looking for cost-free and tape-free solution, we can try to use our MIDIBox: The MIDI file should contain a note at the beginning and at the end of the sequence to define its length (No. of Bars) and the pitch bend message in form of the straight line. Once looped, it should (theoretically) apply the pitch to all notes.
