Common tuning methods for software plugins: Difference between revisions
kontakt |
mNo edit summary |
||
| Line 3: | Line 3: | ||
== File import == | == File import == | ||
Probably the most common method, typically for this method you would need to download a file such as from [https://scaleworkshop.plainsound.org/ 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. | Probably the most common method, typically for this method you would need to download a file such as from [https://scaleworkshop.plainsound.org/ 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. | ||
This will usually have to be done individually for each plugin instance. | |||
=== .scl/.kbm file === | === .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 [https://www.huygens-fokker.org/scala/downloads.html#scales Scala scale archive] and the software of the same name. | The Scala file format (.scl) is currently the most popular and supported microtonal file format. In addition, it is the format used by the [https://www.huygens-fokker.org/scala/downloads.html#scales Scala scale archive] and the software of the same name. | ||
Details of the Scala file format can be found here: https://www.huygens-fokker.org/scala/scl_format.html | Details of the Scala file format can be found here: 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 | Sometimes, you may also want a .kbm file to map an accompany .scl file to start on a specific MIDI note or frequency, so you may want to choose a plugin that supports both formats. | ||
=== .tun file === | === .tun file === | ||
.tun files are known as the Anamark tuning format. | .tun files are known as the Anamark tuning format. | ||
| Line 42: | Line 41: | ||
== MTS-ESP == | == MTS-ESP == | ||
MTS-ESP is also a common way of microtuning plugins. Typically you will have to open and retune a MTS-ESP source/master, | MTS-ESP is also a common way of microtuning plugins. Typically you will have to open and retune a MTS-ESP source/master (how you do so is dependent on the specific one), and it will automatically retune other plugins that are open and support MTS-ESP. | ||
A list of MTS-ESP sources and clients can be found here: https://surge-synthesizer.github.io/tuning-guide/#mts-esp | |||
== Other == | == Other == | ||
For more description on DAW-specific tuning methods, see [[Software#DAWs]]. | |||
=== MPE === | === MPE === | ||
Revision as of 05:30, 11 December 2025
This page aims to explain a basis of 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 and the software of the same name.
Details of the Scala file format can be found here: 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 MIDI note or frequency, so you may want to choose a plugin that supports both formats.
.tun file
.tun files are known as the Anamark tuning format.
Kontakt Script
Kontakt (and NOT Kontakt Player) has its own separate method for microtuning, and that is through its script editor accessible through Edit Mode. 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. Beware however, the effectiveness of Kontakt's microtuning varies by the library, and not all libraries allow you to access Edit Mode.
To access Edit Mode, load in an instrument in Kontakt, and check the top left corner for a wrench icon.
If instead, you find a cogs icon, that means the library you are using does not allow you to use Edit Mode and thus this method cannot be used. Rarely some of these libraries have built-in tuning capabilities, but they are usually very limited. (eg. Kontakt Factory Library 2)
Once you are in Edit Mode, click the Script Editor button and then click the first tab that says <empty>.
You can choose whether you want to use one of the default presets (via Preset -> Factory -> Tuning) or import your own. Clicking Edit will open up a large text box. If you downloaded a Kontakt Script from Scale Workshop, you will have plaintext that you can copy and then paste into the script editor by clicking Apply from... -> ... Clipboard and then clicking Apply.
From there on you should test your instrument to see whether it works with microtuning, as some libraries break or do not tune correctly.
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/master (how you do so is dependent on the specific one), and it will automatically retune other plugins that are open and support MTS-ESP.
A list of MTS-ESP sources and clients can be found here: https://surge-synthesizer.github.io/tuning-guide/#mts-esp
Other
For more description on DAW-specific tuning methods, see Software#DAWs.
