Notifications
Clear all

How To Unify VSTs with AutoHotKey Scripts

168 Posts
12 Users
61 Likes
14 K Views
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
 

@tony10000

That should save some time for anyone not wanting to get into AHK. Thanks. 


   
ReplyQuote
(@tony10000)
Member
Joined: 4 years ago
Posts: 195
 

@zinct Of course, it is not an ideal solution for Unifying huge libraries but it is perfect for Unifying your favorite patches and custom sounds.  There are other macro recorder options out there that may also work well:

https://techdentro.com/best-macro-recorders/

 


   
ReplyQuote
(@tony10000)
Member
Joined: 4 years ago
Posts: 195
 

@zinct @getdunne Here is something more exciting.  I have been playing with another free macro recording tool called Pulover's Macro Creator this AM and it also works well. 

https://www.macrocreator.com/

Here is the project on GitHub:

https://github.com/Pulover/PuloversMacroCreator

It has the added advantage of being able to create AHK scripts. 

This may be a game changer! 

 

Here is a simple script I created with this tool. (Revised again and all of the mouse moves are gone.)  It is made to be used with the standalone version with the screen maximized:

 

; This script was created using Pulover's Macro Creator
; www.macrocreator.com

#NoEnv
SetWorkingDir %A_ScriptDir%
CoordMode, Mouse, Window
SendMode Input
#SingleInstance Force
SetTitleMatchMode 2
#WinActivateForce
SetControlDelay 1
SetWinDelay 0
SetKeyDelay -1
SetMouseDelay -1
SetBatchLines -1

F3::
Macro1:
WinActivate, Unify ahk_class JUCE_17aca449b7f
Sleep, 333
Sleep, 2172
Click, 1454, 136 Left, Down
Sleep, 172
Click, 1454, 136 Left, Up
Sleep, 1422
WinActivate, Preset Metadata ahk_class JUCE_17aca449b7f
Click, 279, 56 Left, Down
Sleep, 219
Click, 279, 56 Left, Up
Sleep, 14187
Click, 443, 502 Left, Down
Sleep, 266
Click, 443, 502 Left, Up
Sleep, 1828
WinActivate, Save new Unify preset file ahk_class #32770
Send, {Enter}
Return

This post was modified 3 years ago 4 times by tony10000

   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 330
 

@tony10000

Unfortunately the macro creator generates an abundance of script commands (i.e.mousemove), but it is very good to get the grips with AHK.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
JeremyH reacted
ReplyQuote
(@tony10000)
Member
Joined: 4 years ago
Posts: 195
 

@zinct @getdunne I was also able to create an executable of the script and it works fine...


   
ReplyQuote
(@tony10000)
Member
Joined: 4 years ago
Posts: 195
 

@thsve You can edit the script afterwards and remove any unwanted actions.  I just redid it and created an EXE so that I can easily run it when Unifying patches.  Very handy!  I can comfortably do 2-3 patches per minute including typing in names.

This post was modified 3 years ago by tony10000

   
JeremyH and getdunne reacted
ReplyQuote
(@tony10000)
Member
Joined: 4 years ago
Posts: 195
 

@thsve @zinct @getdunne I figured out how to turn off all of the mouse movements and it generates a much more compact script.  See revised version above.


   
JeremyH reacted
ReplyQuote
(@tony10000)
Member
Joined: 4 years ago
Posts: 195
 

I found this resource if anyone is interested: https://www.youtube.com/watch?v=hZRggm8RkhM


   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 330
 

@tony10000

I haven’t watch this one, but there is an abundance of tutorials on AHK out there. Good luck scripting!

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
(@tony10000)
Member
Joined: 4 years ago
Posts: 195
 

@thsve I picked up a Udemy course last night…thanks!


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
 

I'm on Mac and want to try to unify a couple free synths like Full Bucket Music's awesome FB7999 for example (DW8000 emu).

Its not at all clear to me how I should go about doing that.  I realize every plugin is a little different in terms of programming something like AutoKey to build up a unify library, but some kind of high level tutorial on how we should go about doing one would be very helpful.  I would have to use Keyboard Maestro on Mac anyway...but a few examples of something that has already been done, or at least a high level guide would be very helpful, right now I have absolutely no idea how to even get started other then painfully and slowly doing it by hand...which after  few minutes I realized would be too much work to be worth it.

 


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
 

also wondering if actual VST bank files can be converted somehow automatically, I would be willing to write a program to do so if that is something that would be possible to do...but I don't know if it is possible or not...and of course categorizing everything is another challenge I think?

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@dewdman42

There's a whole GitHub repo of code for creating Unify patches programmatically: https://github.com/pluginguru/unify-batch . Be warned, though: it tends to be a tedious reverse-engineering process which is plug-in specific.

For FullBucket plug-ins specifically, Björn Arlt has been very helpful and receptive when I have contacted him in the past. I bet he'd be willing to offer helpful suggestions if you ask him!


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
 

I'm not able to access unify-batch repo.  Is it marked private?

I like some of your other repos, I can learn a few jUCE tricks there.  😉

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

@dewdman42 Sorry, that was an outdated link. I've fixed it above, as https://github.com/pluginguru/unify-batch.


   
ReplyQuote
(@craigr68)
Member
Joined: 3 years ago
Posts: 204
Topic starter  
Posted by: @dewdman42

I realize every plugin is a little different in terms of programming something like AutoKey to build up a unify library, but some kind of high level tutorial on how we should go about doing one would be very helpful.

Not entirely sure what you mean by high level tutorial, but on page 3 of this thread, thsve posted several youtube tutorials that takes you step-by-step thru the Autohotkey process. The videos show the general procedure of how many of the VSTs were unified.


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
 
Posted by: @getdunne

@dewdman42 Sorry, that was an outdated link. I've fixed it above, as https://github.com/pluginguru/unify-batch

Still doesn't work


   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 330
 

The link has a dot at the end. If you remove it it should work.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 
Posted by: @thsve

The link has a dot at the end. If you remove it it should work.

Thanks for spotting that! I keep forgetting that the software powering this forum treats a period after a URL as part of the URL.

@dewdman42 try the link now. I edited my posts above.


   
ReplyQuote
(@dewdman42)
Trusted Member
Joined: 2 years ago
Posts: 49
 

cool that works.  I'll check that out.


   
ReplyQuote
(@jason_za)
Estimable Member
Joined: 4 years ago
Posts: 65
 

Hi @thsve. I've been using your Unify Patch Editor, which is an excellent tool for editing the names of my patches, since many different packs have different naming conventions, e.g. Lead, LD, etc., so it is very useful, to neaten everything up. I noticed however that when I try changing the Library name, e.g. [SERUM] to [Serum], it shows as being changed in the Unify Patch Editor but still shows as [SERUM] in Unify itself, which is rather odd. Have you made any further updates to the Unify Patch Editor since May 2021? I'd really appreciate a copy, if you have. Thanks a lot for this very useful tool.


   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 330
 

@jason_za 

Hi, I’m glad that it is useful. Didn’t know anybody still used it. Yes, I’ve probably made changes since then since I tinker with it all the time. Unfortunately Change Management isn’t my top priority 😎 .

Even the version you have shouldn’t behave like that, never experience it. I’m not able to look at it right now, but will as soon as possible. Do I understand you right that the only change in the name are to lower case. Are the ”[]” part of the library name?

Can you share the library that are problematic somImcan have a look, I have Serum?

Also beware that changing the library name doesn’t change the name of the directory in the Unify library folder structure. Also, changing library is quite complicatet in som circumstanses and might make the patches not work as expected. It is described in the ”manual” (if that was included in ”your” version).

I’ll check the program later today (it is early morning here in Sweden) and come back to you.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 330
 

@jason_za 

Did a quick test and you have to do a full db rebuild (alt+click the "flash") to make it show in Unify. The latest version of the patch editor is 3. I will post a download limk a little later, just have to update the "manual". 

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
(@jason_za)
Estimable Member
Joined: 4 years ago
Posts: 65
 

Thanks so much, @thsve. I really appreciate it a lot. I have never experienced the kindness and helpfulness as is evident in the pluginguru community with any other music production software company - not even close. pluginguru and its community are really something special and I'm grateful to be part of it.


   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 330
 

@jason_za 

Thank you for the kind words.

Did you try to rebuild the Unify database and did that solve your problem?

Anyway, here is version 3 of the Patch Editor with several additions and changes: Edit: Link removed

 

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
RedRose68 reacted
ReplyQuote
(@jason_za)
Estimable Member
Joined: 4 years ago
Posts: 65
 

Hi @thsve. I'm busy running a full reset of the Unify database. Will check if this fixes the renaming. Thanks again for the great tool and prompt response. I'm running Unify Patch Editor v2.1.


   
ReplyQuote
(@jason_za)
Estimable Member
Joined: 4 years ago
Posts: 65
 

Thanks so much @thsve. The full reset is running but will take a very long time, as there are loads of presets to process. I named each preset pack I purchased and 'Unified' starting with the name of the synth, rompler, instrument name, e.g. [Serum] Echo Sound Works - Roses, [Serum] Echo Sound Works - Vivid, etc., to make it easier to group in Unify, now that one can do so, since the previous update (1.7). I then create separate groups for all my preset packs, based on the synth, instrument, etc. 


   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 330
 

@jason_za 

 A little trick I usually use when editing patches since a full rebuild can take a very long time when you have many patches.

I have created a folder e.g. ”Libraries_out”, to wich I move all libraries I’m not working with at the moment. Then the rebuild of the remaining libraries will go much faster.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
RedRose68 reacted
ReplyQuote
(@courtjestr)
Eminent Member
Joined: 2 years ago
Posts: 17
 
Posted by: @thsve

@jason_za 

Thank you for the kind words.

Did you try to rebuild the Unify database and did that solve your problem?

Anyway, here is version 3 of the Patch Editor with several additions and changes: Edit: Link removed

 

Hi @thsve. Is there anyway to get a copy of your patch editor? I am wondering why the link was removed in the above post.


   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 330
 

@courtjestr 

Had to make room in my dropbox. Edit: Link removed

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
(@courtjestr)
Eminent Member
Joined: 2 years ago
Posts: 17
 
Posted by: @thsve

@courtjestr 

Had to make room in my dropbox. It is back now: https://www.dropbox.com/s/wkvp5mfymbcqtn1/UNIFY%20Patch%20Editor%203.zip?dl=0  

@thsve

Thanks for posting this again. Looks like it will be very useful.

I am wondering if it might be useful to have a dedicated space for these tools. I could see having your patch editor up there as well as Shane's batch tools. I would also like to see a section where AHK scripts used for Unifying various libraries could be shared. Even though they may not be needed to produce factory libraries that are already officially available, they could be useful for generating other libraries for personal use. They also could be modified and used for Unifying other factory libraries that are not yet done.

Doug.


   
ReplyQuote
(@jason_za)
Estimable Member
Joined: 4 years ago
Posts: 65
 

@thsve Yes, rebuilding the patch database sorted out the issue. Thanks for the advice. Apologies for the delay - must have missed the reply email.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4367
 

Unify 1.8's ability to auto-update INST layer titles with the patch name (at least for many VST plug-ins) can be exploited as a quick way to get patch names onto the clipboard in AHK scripts, provided (a) the plug-in supports this, and (b) you allow enough time for the layer-title to update.

Attached is a (zipped) AHK script I used to unify Cherry Audio's new Dreamsynth DS-1, one patch-category at a time. Lines 14-17 capture the INST1 title to the clipboard. Lines 23-28 paste it into the Unify patch-save dialog, lines 29-31 prepend the current category-prefix, and lines 33-34 (commented out) show how to delete an unwanted common suffix.

The mouse coordinates for clicks on Unify's GUI will need to be updated for your monitor, but the ones for Dreamsynth should be fine.


   
ReplyQuote
Page 4 / 4
Share: