It took me some time to find where you had asked that question.
Sorry, Shane, I thought your post was a direct answer to my post two posts above so I thought it was clear and I did not bother to link ...
The way John and I have been thinking about macro parameter linkage is:
- Linking parameters to macro knobs is a "finalizing" step, to be performed after you have the basic sound correct.
- Once parameters are linked to knobs, it's better to consider them "off limits", to be adjusted only via the macro knob.
OK - I see, this approach is perfect when creating new patches.
But for creating Unified-libraries where you want to supply useful macros this is very unsatisfying.
@ssquared had the same problems with it in this post.
As discussed there, setting the macro knobs to parameter values at the time of patch loading (1st parameter, linear curve) would be nice IMO.
Thanks & regards
Rob
My response is the same here as here: I have put this on the to-do list, but it's not a quick fix and there are implications which must be studied carefully, so it may not appear right away.
Hey everyone,
I'm starting to Unify the factory patches from my AIR Music Tech synths, starting with Vacuum Pro (following the naming conventions as best I can). A couple of questions:
1) Do Unified libraries like this always have the master effects chain: Flex Eq - Enforcer - LoudMax?
2) Is anyone else working on doing this?
As always, massive thanks to John, Shane and Taylor for the hard work 🙂
1) Do Unified libraries like this always have the master effects chain: Flex Eq - Enforcer - LoudMax?
Not all do, but we recommend it, especially LoudMax because it ensures that output levels don't exceed 0 dB.
@getdunne Great, thank you. I'll add it to the patches 🙂
Note that Shane's unify-batch tools, specifically PatchReformer in this case are excellent to doing mass updates to patches to make them consistent. Check it out here if you haven't already:
Hey everyone,
I'm starting to Unify the factory patches from my AIR Music Tech synths, starting with Vacuum Pro (following the naming conventions as best I can). A couple of questions:
2) Is anyone else working on doing this?
I don't think Vacuum Pro has been done yet. Hybrid and Loom II have been though.
I went to the link you provided above and was going to download PatchReformer but didn't find any .exe file to download. I see the source there but no download for that either. Would anyone please clue me in on what I'm missing? Is there a Windows compiled version?
Update: Ok, I figured out you can download the zip file of all the unify-batch programs - so I now have the source. But I still don't have an exe version. I can compile it if need be.
Update2: OK NEVERMIND: I found the exe version from another posting at https://www.dropbox.com/s/o5kzt3pea8ah9n4/Unify%20Batch%20Tools%20Win64.zip?dl=0
Awesome! Thank you @courtjestr and @craigr68
I've checked the Unified library list and there's no entry for Hybrid or Loom2, does anyone know where I can get them?
Also, super helpful about the batch editor. Will bear that in mind when I find I've missed something 😣
Update2: OK NEVERMIND: I found the exe version from another posting at https://www.dropbox.com/s/o5kzt3pea8ah9n4/Unify%20Batch%20Tools%20Win64.zip?dl=0
Sorry for my ignorance but can someone point me to the mac-OSX-executables of Shane's unify-batch tools ?
Shane posted the links in https://forums.pluginguru.com/unify-patchbook/arturia-arp-20600-v3-unified/#post-10476. I found it by searching for "patchreformer".
Awesome! Thank you @courtjestr and @craigr68
I've checked the Unified library list and there's no entry for Hybrid or Loom2, does anyone know where I can get them?
Also, super helpful about the batch editor. Will bear that in mind when I find I've missed something 😣
I know I've seen postings where Hybrid was done. Try using search at the top. Below is one for Hybrid and one for Loom. There may be more. I guess it was never finalized and hosted at Pluginguru site. With Hybrid, I did my own version of it with Autohotkey. I had so many patches that I just did a select few categories.
https://forums.pluginguru.com/unify-share/vst-hybrid/#post-6411
https://www.dropbox.com/s/9tix55uj2db5qqw/Unified%20-%20Loom%20II.guru?dl=0 .
Awesome! Thank you @courtjestr and @craigr68
I've checked the Unified library list and there's no entry for Hybrid or Loom2, does anyone know where I can get them?
Also, super helpful about the batch editor. Will bear that in mind when I find I've missed something 😣
I know I've seen postings where Hybrid was done. Try using search at the top. Below is one for Hybrid and one for Loom. There may be more. I guess it was never finalized and hosted at Pluginguru site. With Hybrid, I did my own version of it with Autohotkey. I had so many patches that I just did a select few categories.
https://forums.pluginguru.com/unify-share/vst-hybrid/#post-6411
https://www.dropbox.com/s/9tix55uj2db5qqw/Unified%20-%20Loom%20II.guru?dl=0 .
Yes, this is where I found them as well. Thanks @craigr68 for going the extra mile to track them down. I am not sure why, but these two have not made it into the official list of Unified libraries. It may be that they were not submitted to John for inclusion, or they were not tagged and categorized properly, or the developer did not give permission to include the library in the official list.
I went to the link you provided above and was going to download PatchReformer but didn't find any .exe file to download. I see the source there but no download for that either. Would anyone please clue me in on what I'm missing? Is there a Windows compiled version?
Update: Ok, I figured out you can download the zip file of all the unify-batch programs - so I now have the source. But I still don't have an exe version. I can compile it if need be.
Update2: OK NEVERMIND: I found the exe version from another posting at https://www.dropbox.com/s/o5kzt3pea8ah9n4/Unify%20Batch%20Tools%20Win64.zip?dl=0
Glad you found the exes. I compiled the sources myself. They are an excellent suite of tools for doing mass changes to a Unified library.
Glad you found the exes. I compiled the sources myself. They are an excellent suite of tools for doing mass changes to a Unified library.
Yes. I used the patchreformer tool today to alter the master layer on several libraries. What would have taken hours with Autohotkey, instead took me just minutes. I'll be using it occasionally for sure.
I ran into one surprising thing about patchreformer. It worked great for several libraries where every patch in each library had the same vst. However, I have this one library, that I call Mine, which consists of patches with a variety of INST1 layer vsts. Even though the targeted patches have only 1 INST1 layer, it gets replaced by the reference INST1 vst. I thought it was supposed to retain whatever was in the targeted INST1 vst.
Macintosh: https://www.dropbox.com/s/28vp7tj4u59f184/Unify%20Batch%20Tools%20Mac.zip?dl=0
Thank you very much !!!!
I ran into one surprising thing about patchreformer. It worked great for several libraries where every patch in each library had the same vst. However, I have this one library, that I call Mine, which consists of patches with a variety of INST1 layer vsts. Even though the targeted patches have only 1 INST1 layer, it gets replaced by the reference INST1 vst. I thought it was supposed to retain whatever was in the targeted INST1 vst.
Patch Reformer retains only the instrument plug-in on the INST1 layer, from the reference patch. It does NOT retain the INST1 layer from the input patches.
I have some other tools here, which are not generic and user-friendly like Patch Reformer (I have to modify the source code for every case) which I use for other batch-processing tasks. If you can specify exactly what you need done, I may be able to help you, but I can't afford to put a lot of time into it.
Patch Reformer retains only the instrument plug-in on the INST1 layer, from the reference patch. It does NOT retain the INST1 layer from the input patches.
That explains what I was seeing. Thanks for the offer, but for what little else I'm doing, I don't need anything else. I guess I would prefer it retain the INST1 layer instead, or have an option to.
I have one other library (self-made with Autohotkey), OBXd (not the built-in version), where on the surface it looked to be working. But when I opened up the OBXd vst after running PatchReformer, I would find the patch name wasn't correct. I retested this a couple of times. This whole thing I'm doing isn't important. I'll just set up an Autohotkey script to finish up. I was just changing the Master Layer effects for that library.