If you are going to use this to build ini files, please also explore the other features - which is really what this script is all about - and why it is called Control2Tempo. This was made for making tempo-maps to live recordings.
It also stores project track orders.
When you make your ini files, consider how much time this would take (many of you already know) to do by hand. I can assure you it was nothing next to writing this utility - and that feature. If you do pro-level mixing, perhaps you'd like to reciprocate by doing a mix for me.
EDIT3: removed previous edits - non-issue.
Last edited by jmh on Mon May 25, 2026 6:19 am, edited 1 time in total.
Installation Instructions:
Install autohotkey V2 - this can be found at: autohotkey.com
Run SSC2T_Setup.exe
You will be prompted to enter a letter.
The C2T (Control2Tempo) icon will be placed on the desktop.
Instructions for loading the script:
Open SAWStudio (or SAWStudio64-V2 for INI building)
(Note: If you are one of the initial testers of INI_Builder or just want to practice, install
a test version of SAWStudio64 V2 in another folder, and run that version of studio.)
Run "Control2Tempo.ahk" by pressing Ctrl+Alt+TheKeyYouChose - or clicking on it.
(If you want to look over the script beforehand, find it in ProgramFiles\SSC2T)
The functions will now be ready to be called from within SAWStudio.
Note: The entire script will be cleaned, reorganized, and the related functions split into
separate files. This should make it easier to maintain, or if someone wants to add additional
functionality, it can be done in a more organized way. This is going to be a while because
about half of the script is disabled until that functionality is reworked. At the moment I
have to get back to writing songs. So for now, it is this beta version. Enjoy...
________________________________________________________________________________________
(This section is only applicable to SAWStudio64 v2 or newer - as it regards vst3 plugins.)
To run INI_Builder, hold down the chord consisting of ` and x
Note that this is the backtick key, NOT a single quote.
Select OK.
You will have made several ini files. If you have waves plugins installed, studio will close then
re-open. It will then open the WaveShell to discover the plugins. Since those dlls are enormous
it may take many seconds - don't touch the mouse or keys.
Note for waves users:
(There is 30 second timeout that may display an error message. if that occurs, just hit
backtick r to reload the script, then backtick x - it will probably work the second
time as now the waveshell or waves-server will be in memory and initialized.)
You will now have a new sub-directory:
"C:\SAWStudio64\VST_PlugIns\INI_BUILDER"
(if you have a test SAWStudio folder - it will instead be in that path).
Within you should note a few files:
"C:\SAWStudio64\VST_PlugIns\INI_BUILDER\CONFIGS\VST3_filter.sample"
...and
"C:\SAWStudio64\VST_PlugIns\INI_BUILDER\CONFIGS\INI_BUILDER.ini"
...here is my version if that file:
The first time you run the INI_Builder function
"C:\SAWStudio64\VST_PlugIns\INI_BUILDER\CONFIGS\VST3_filter.SAWStudio64"
...will also be created. This is where you determine what INIs will
built and what their names will be.
You may also copy VST3_filter.sample to VST3_filter.SAC64 to set up plugins.
These INIs may consist of entirely different plugins than studio's and are
define only the INIs created for SAC64.
Here is an example of a filter:
"C:\SAWStudio64\VST_PlugIns\INI_BUILDER\CONFIGS\VST3_filter.SAWStudio64"
It makes a total of 7 INIs.
This renames all waves plugins to the form:
w_PlugInName
# This is a filter file for Control2Tempo.ahk on 2026-01-29.
#
# Its intent is to aid in the creation and maintenance of vst3 ini files - which are used to make that
# type of plugin available to use in studio.
#
# The syntax of the vst3_generation.filter is as follows:
#
# PrimaryKeyword=value
#
# PrimaryKeyword=value , SecondaryKeyword=value
#
# # PrimaryKeyword=value
#
# There are 3 primary-keywords, and 2 secondary-keywords. There are 2 special characters; pound-sign, and comma. The
# comma is only used prior to a secondary-keyword. Spaces are also permitted to aid in reading - but are not special.
#
# The syntax's most powerful character is the '#' pound-sign. This serves twofold. It initiates a comment - but
# with the exception being when a single # is followed by a primary-keyword:
#
# A pound sign preceeding plugin_name= disables the building of an .ini file for that plugin only.
# A pound sign preceeding group= disables all following plugin_name entries until the next group= or vendor= entry.
# A pound sign preceeding vendor= disables all following plugin_name entries until the next vendor= entry.
#
# vendor= [, prefix='PrefixName_' (This secondary keyword's value prepends name.ini files.)]
# group= [, prefix='PrefixName_' (...works as in vendor - but supercedes it. Superceded by alias=)]
# plugin_name='NAME' [, alias='ReplacementName' (overrides normal naming. File becomes - ReplacementName.ini )]
#
#
# plugin_name= is the most important keyword. An .ini file will only be generated if described here. Also the value
# must be identical to the NAME of an installed .vst3 for an ini to be generated - regardless of this file's content.
#
#--------------------------------------------------------------------------------------------------------------------#
#
# The initial setup of this file was created with:
# C:\SSC2T\Control2Tempo.ahk
# ...C:\SAWStudio64\VST_PlugIns\INI_BUILDER\CONFIGS\VST3_filter.sample is re-generated each time INI_BUILDER
# in Control2Tempo.ahk is run. If you have new plugins, or want to change your naming convention
# copy that file to either, VST3_filter.SAWStudio64, or VST3_filter.SAC64
#
# The installation behavior can be adjusted in C:\SAWStudio64\VST_PlugIns\INI_BUILDER\CONFIGS\INI_BUILDER.ini
# For ini to be generated, a filter must exist. To be installed, values for the following two keys must be set:
# INI_Dest_Dir = ( and the directory must already exist )
# install_INIs = ( must equal either 1 to install the file - or 0, which leaves new inis in the queue )
# Note, if either of these is set to 1 - AND its destination exists, a zip file backups up its previous INIs.
#
# This file needs to be maintained to contain any newly acquired plugins. This is the 'work' that must be done
# prior to running the SawStudio64-vst3-manager.
#
# A word of warning: This utility makes it very easy to change the names of plugins. You must bear this in mind if
# choosing to change a plugin name, as any existing edl that depends upon it could be subject to difficulties. Aliases
# should be used with care - and chosen with consistancy and future operability in mind.
# Note that running INI_Builder places a log in the clipboard (erasing the previous contents).
#
# The manager has been written by jmh - December 2025 -> January.
#
# (The space at the beginning of this line begins parsing of this config file.)
However, I have come across a hiccup while using this.
It did not get all my plugins "made" into .ini's.
I reran and it came back with the same few plugins short compared to what I own.
I reran a few more times and watched what it was doing.
For some unknown reason, one of my shells (in layman's terms) is empty.
The function stops at this empty shell and does not proceed to the remaining shells to get the rest of the plugins.
When I do a manual highlight in FX Choices and try add the "empty" shell in SS v2.4 to "see" the plugins within, it does not show any plugins in the list.
When I continue to the next shell they are there and I was able to make my own .ini's of the missing plugins.
WaveShell1-VST3 14.12_x64 (shows plugins fine, added all automatically)
WaveShell1-VST3 14.19_x64 (shows plugins fine, added all automatically)
WaveShell1-VST3 14.21_x64 (empty... function stops here)
WaveShell1-VST3 14.25_x64 (shows plugins fine, manually added, did not make .ini's)
WaveShell1-VST3 15.5_x64 (shows plugins fine, manually added, did not make .ini's)
*I did double check the WaveShell1-VST3 14.21_x64.ini that your helpful gadget made and it is properly pointing to
C:\Program Files\Common Files\VST3\WaveShell1-VST3 14.21_x64.vst3s
So, is it probably just me, yeah.
Is it maybe 14.21 only has bug fixes and no plugins UI, yeah.
But just in case there is a modification you can do, here's the information I was able to see.
To everyone else, double check your Waves plugins and make sure you got them all "made".
I'm working on a different project now - but if I revisit SSC2T, I'll take a look (the timeouts were a bit of guesswork, so if the waves-server takes a long time, it can crap out).
I also just saw: 'For some unknown reason, one of my shells (in layman's terms) is empty.'
My guess is it may be some helper dll that one or some of the plugins contained in another waveshell calls.
The script has no provision to handle this situation. For now, if anyone encounters this, I'd just move the file to another folder (not in the C:\Program Files\Common Files\VST3\ tree) and then move it back again after you build the inis.
__________________________________________
A side note is that I 'upgraded' waves to V16 on win11 - and the audio channels got mixed up (if you can believe that). I contacted Bob and he tested 16 on a win10 machine and his were working fine. Searches suggested it was bug in waves (on win11 - or my particular setup), and since SS isn't one of the 'supported daws' I didn't try their support, just not using waves. Anyway, for now, you may want to avoid v16.
