Common tuning methods for software plugins
This page aims to explain the different common tuning methods you may encounter when using software plugins in a DAW, so you can be more informed of the differences between them. This page is currently a work in progress.
File import
Probably the most common method, typically for this method you would need to download a file such as from Scale Workshop (a great resource for creating these tuning files), and there would be a setting in your chosen plugin where you would be able to import the file. This will usually have to be done individually for each plugin instance.
.scl/.kbm file
The Scala file format (.scl) is currently the most popular and supported microtonal file format. In addition, it is the format used by the Scala scale archive.
too lazy 2 do this rn so https://www.huygens-fokker.org/scala/scl_format.html
Sometimes, you may also want a .kbm file to map an accompany .scl file to start on a specific note or frequency; so you may want to choose a plugin that supports both formats.
The .kbm file format
[insert stuff here]
.tun file
.tun files are known as the Anamark tuning format.
Kontakt Script
Kontakt has its own separate method for microtuning, and that is through its script editor. To use it for microtuning, you either have to import a Kontakt script, or use one of the preset Kontakt microtuning scripts and choose the settings of your liking.
While Kontakt Scripts typically come in the .nkp format, downloading a Kontakt Script from Scale Workshop will give you plain text, which you can copy and paste into the script editor.
Beware, the effectiveness of Kontakt's microtuning varies by the library, and not all libraries allow you to access the script editor.
Other tuning file formats
todo: table of plugin / etc specific tuning files and etc
MTS-ESP
MTS-ESP is also a common way of microtuning plugins. Typically you will have to open and retune a MTS-ESP source, which will automatically retune other plugins that are open and support MTS-ESP.
