This text is aligned to version 2023-07.001.

XeTune is a visualiser and basic editor for multiple microtonal tunings.

You can use it at https://johnvalentine.co.uk/app/xetune/app.html, or run it from your computer without a web server.

With XeTune, you can:

• Create new tunings:
  • Equal division tunings within any ratio.
  • Ratios within integer limits.
  • Compose from selected notes in other tunings.
• View many tunings together, over a range of up to four octaves, including an octave of subharmonics.
  • Edit the name and description of tunings.
  • Duplicate tunings.
  • Promote a tuning as reference.
  • Remove tunings.
  • Select notes among tunings, and:
    • View their intervals, as cents and relative errors to ratios.
    • Copy notes into a new tuning.
    • Remove notes from tunings.
  • Edit the configuration as JSON (we don't recommend this, but you can).
• View properties for the last-selected note.
• Drag-and-drop .scl (Scala format) files.
• Download tunings as .scl files.

Feature requests and feedback

I'm open to feature requests, and most of the backlog is in issues.

Dependencies and data use

XeTune is a client-side web browser app, which has no external code dependencies other than standard browser APIs, no server dependency.

It has the ability to read files that you drop in, interpreting them as .scl (Scala) files, and can export .scl files as downloads.

The XeTune app does not transmit nor collect your data, but it stores configuration data to localStorage, which can include user-entered data in tunings. Be aware that proprietary browsers, and browser plugins/extensions might read or transmit this data.

For developers

I structured this prototype project as a monolith closure with published UI methods. Internally, code is grouped by functionalies like reference data, utilities, rendering, tuning calculations, and UI events. Concerns are not as separated as they should be, and I'm aware that there are better ways to organize a project.

The project needs no preprocessing to run, so there is no build process.

The UI is composed using render functions, and is often rendered wholesale to reflect updated state. So far, this is efficient enough to be responsive to large and small changes.