Adaptuner - getting started

Installing the program

Follow the instructions for your platform:

Setting up your piano/synthesizer

The adaptuner is a MIDI-to-MIDI program. So, in order to hear any sound, you’ll have to use some kind of synthesizer.

Instead of using the MIDI tuning standard (which would be perfectly suited to this application, but isn’t implemented by most hardware and software instruments), adaptuner uses MIDI pitch bend messages. This entails some assumptions about the settings of the synthesizer:

Using with an e-piano

This is the intended use case: The piano should sound and play “as normal”, while delegating the on-the-fly tuning to adaptuner. In order for this to work, I make the following assumptions:

Exploring the default configuration

Upon startup, the adaptuner will first show you a window that allows you to set up MIDI connections to input and output devices. Once you’ve done that and closed the window (you can always return to it later), you’ll notice the hamburger menu at the top left of the screen. Click on it, and a side panel will become visible that shows all settings and options:

adaptuner side panel  

There are several sections in this side panel:

Loading and saving custom configurations

Let’s say you’ve played around with one of the default configurations and reached something that you like. The “save configuration” button will allow you to save the current configuration. The “load configuration” button will allow you to load any previously saved configurations.

There’s also a small, but growing, collection of example configurations here. Note that these configurations always apply to the latest version of adaptuner only.

It is possible, but not advisable, to edit configuration files manually. The adaptuner checks many of invariants a configuration file must satisfy, but not all of them. Manually edited configuration files may violate some invariants and lead to unexpected behaviour or crashes. Configuration files created by using the “save configuration” button will be correct (assuming there are no bugs…).

back to top-level documentation