User:Mousemambo/Tuning methods: Difference between revisions

Mousemambo (talk | contribs)
removed the intro from this main page onto its Discussion page and inserted a notice pointing to it
Mousemambo (talk | contribs)
created an Appendix section
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Mbox|type=notice|text=Please use this page's [[User_talk:Mousemambo/Tuning_methods|Discussion page]] for comments and suggestions. This developing page is initially just an outline, but will be further developed into a proper page.}}
{{Mbox|type=notice|text=Please use this page's [[User_talk:Mousemambo/Tuning_methods|Discussion page]] for comments and suggestions. A summary of my thinking and my own comments are there too. Or you can join the discussion in the #wiki channel of the Xenharmonic Alliance's [https://discord.com/invite/FSF5JFT Discord server]. This developing page is initially just an outline, but will be expanded into a proper page. I use square brackets to set apart my document development notes, which will all be removed before the final document version.}}'''Brief article summary''' goes here....
*'''Introduction'''
 
**Why? We need to tell hardware (electronic) and software (virtual) musical instruments what tuning system to use when they receive controller input or MIDI data.
== Overview ==
**What? Either the instrument itself, or an intermediary component dedicated to tuning, may need to be provided either with direct tuning data entry or a data loaded from a tuning file. You may need to specify what tuning mechanism(s) the instrument supports or should use, and sometimes also additional information about how to use that tuning data.
'''Temporary Outline'''
**How? Components of a tuning system. At the time of this writing, there are three general components of tuning systems that you'll encounter in modern instruments: direct tuning information, tuning files, and tuning plugins or retuners. These are in addition, of course, to a controller (e.g. keyboard) and a musical instrument, which may be integrated in a hardware synth for example. Because legacy electronic instruments that support retuning have been preserved and are popular, but use outdated tuning mechanisms, those old mechanisms also need some consideration.
*Why? We need to tell hardware (electronic) and software (virtual) musical instruments what tuning system to use when they receive controller input or MIDI data.
**Addressing the complexity. There are many different types of hardware and software musical instruments, each of which will have a specific method or set of methods for tuning which it supports. This page will summarize what methods are being or have been used, and the advantages and disadvantages of alternatives. But you'll need to consult the manual for the specific instrument you are using to learn what tuning method (or methods) it actually supports, and you may need to choose components able to implement a method. These writings are intended to ensure that when you read that manual, you understand what it's saying and can make informed decisions.
*What? Either the instrument itself, or an intermediary component dedicated to tuning, may need to be provided either with direct tuning data entry or a data loaded from a tuning file. You may need to specify what tuning mechanism(s) the instrument supports or should use, and sometimes also additional information about how to use that tuning data.
*'''Direct tuning information'''. Some musical instruments have a built-in system for setting their tuning, via drop-down menu selection or user-customized tuning settings. Note: I don't like the expression "direct tuning" but can't think of something better right now.
*How? Components of a tuning system. At the time of this writing, there are three general components of tuning systems that you'll encounter in modern instruments: direct tuning information, tuning files, and tuning plugins or retuners. These are in addition, of course, to a controller (e.g. keyboard) and a musical instrument, which may be integrated in a hardware synth for example. Because legacy electronic instruments that support retuning have been preserved and are popular, but use outdated tuning mechanisms, those old mechanisms also need some consideration.
**Kontakt "microtuner" built-in script. Because Kontakt is so important, this needs to be stated explicitly, and a how-to link provided.
*Addressing the complexity. There are many different types of hardware and software musical instruments, each of which will have a specific method or set of methods for tuning which it supports. This page will summarize what methods are being or have been used, and the advantages and disadvantages of alternatives. But you'll need to consult the manual for the specific instrument you are using to learn what tuning method (or methods) it actually supports, and you may need to choose components able to implement a method. These writings are intended to ensure that when you read that manual, you understand what it's saying and can make informed decisions.
**Other instruments (e.g. <list of example instruments>)
*Some example configurations could be briefly described here in general forms.
*'''Tuning files'''
'''Main body of this section''' goes here....
**''This whole section should probably be split out into a separate article, leaving just a summary in the main "Tuning methods" article.''
 
** Intro
== Direct tuning ==
***What are tuning files? They provide, in an outside file that needs to be loaded, the information necessary to tell a musical instrument (or software that in turn tells an instrument) how to implement a specific tuning system.
'''Temporary Outline'''
***What are the important features of tuning files? They may establish intervals, frequency assignment, controller data mapping, and more.
*'''Intro'''. Some musical instruments have a built-in system for setting their tuning, via drop-down menu selection or user-customized tuning settings. Note: I don't like the expression "direct tuning" but can't think of something better right now.
**Instrument-specific tuning files
*Kontakt "microtuner" built-in script. Because Kontakt is so important within the musician community, this needs to be stated explicitly, and a how-to link provided ([[User:Mousemambo/Guide to tuning the Kontakt sampler system|Guide to tuning the Kontakt sampler system]]).
**Anamark (.TUN) tuning files
*Other instruments (e.g. <list of example instruments>)
** Kontakt scripts
'''Main body of this section''' goes here....
** Scala (.SCL/.KBM) tuning
 
***Scala tuning files (.SCL)
== Tuning files ==
***Scala keyboard mapping files (.KBM)
''This whole "Tuning files" section should probably be split out into a separate "[[User:Mousemambo/Tuning file|Tuning file]]" article, leaving just a summary in the main "Tuning methods" article.''
*'''Retuners and tuning plugins'''
 
**''This whole section should probably be split out into a separate article, leaving just a summary in the main "Tuning methods" article.''
'''Temporary Outline'''
**Intro
*Intro
*** What are retuners and tuning plugins? They take a tuning file as input (or direct tuning info), and appropriately modify the data going to an instrument. They interpret a tuning file to map controller data into the format the instrument can use. There are both software and hardware implementations, depending on specific musical system (e.g. all software, modular synth system, etc.).
**What are tuning files? In an outside file that needs to be loaded, they provide the information necessary to tell a musical instrument (or software that in turn tells an instrument) how to implement a specific tuning system.
***What are the important features of retuners and tuning plugins? They modify incoming data as it happens, so they need to be fast. Also, they may implement this function either by altering the note-on data of a MIDI stream, or by providing dynamic (continuous control) tuning info while a note is playing (or both??).
**What are some important features of tuning files? Features may include establishing intervals, frequency assignment, controller data mapping, full-keyboard microtuning support, and more.
**Tuning plugins (e.g. VST/AU inserted into a DAW or VST-host plugin chain ahead of a software or hardware-interface instrument)
*Instrument and manufacturer-specific tuning files
***MTS-ESP tuning
**Kontakt scripts
***MIDI Polyphonic Expression (MPE) tuning
**Harmor Pitch Map (.FNV)
***Pitch bend-based tuning
**Max/MSP coll (.TXT)
**Software retuners. Software running standalone (independent from a DAW or plugin host), operating between a controller and a software or hardware instrument.
**PureData text (.TXT)
***alt-tuner
**Soniccouture tuning file (.NKA)
**Hardware retuners. Hardware modules for integrated hardware synths or for CV-controlled modular synths, independent of an all-purpose computer (PC, tablet, phone).
**Sytrus Pitch Map (.FNV)
*'''Other tuning methods'''
**Korg Sound Librarian Scale/Octave (.mnlgtuns/.mnlgtuno)
**MIDI Tuning Specification (MTS)
*[[Anamark tuning file format|Anamark (.TUN) tuning files]]
** Legacy manufacturer-specific and instrument-specific tuning methods
* [[User:Mousemambo/Scala tuning system|Scala (.SCL/.KBM) tuning system]]
**RPN tuning
**Scala tuning files (.SCL)
**Other SysEx-based tuning methods
**Scala keyboard mapping files (.KBM)
'''Main body of this section''' goes here....
 
== Tuning plugins and retuners ==
''This whole "Tuning plugins and retuners" section should probably be split out into a separate "[[User:Mousemambo/Tuning plugin or retuner|Tuning plugin or retuner]]" article, leaving just a summary in the main "Tuning methods" article. I need a better article title than "Tuning plugin or retuner" though.''
 
'''Temporary Outline'''
*Intro
** What are retuners and tuning plugins? They take a tuning file as input (or direct tuning info), and appropriately modify the data going to an instrument. They interpret a tuning file to map controller data into the format the instrument can use. There are both software and hardware implementations, depending on specific musical system (e.g. all software, modular synth system, etc.).
**What are some important features of retuners and tuning plugins? They modify incoming data as it happens, so they need to be fast. They may implement this function either by altering the note-on data of a MIDI stream, or by providing dynamic (continuous control) tuning info while a note is playing (or both??). Do they support full-keyboard microtuning?
*Tuning plugins (e.g. VST/AU inserted into a DAW or VST-host plugin chain ahead of a software or hardware-interface instrument)
**MTS-ESP tuning
**MIDI Polyphonic Expression (MPE) tuning
**Pitch bend-based tuning
*Software retuners. Software running standalone (independent from a DAW or plugin host), operating between a controller and a software or hardware instrument.
**alt-tuner
*Hardware retuners. Hardware modules for integrated hardware synths or for CV-controlled modular synths, independent of an all-purpose computer (PC, tablet, phone).
'''Main body of this section''' goes here....
 
== Other tuning methods ==
'''Temporary Outline'''
*MIDI Tuning Standard (MTS)
* Legacy manufacturer-specific and instrument-specific tuning methods
*RPN tuning
*Other SysEx-based tuning methods
'''Main body of this section''' goes here....
 
== Appendix ==
 
=== Base note, pitch center and tonic ===
[Terminology and inter-relationship between base note, pitch center, tonic, diapason, reference pitch, and other related terms.]
 
=== Look-up Table vs MIDI stream mechanisms ===
[Note-on re-tuning vs. dynamic pitch bending.]
 
== See also ==
 
* [[List of microtonal software plugins]]
* [[Scala#File formats|Scala § File formats]]
* [[DAWs#Approaches to Microtonal Composition in a DAW|DAWs § Approaches to Microtonal Composition in a DAW]]
* [[Anamark tuning file format]]
* [[New Tuning Method]] (mostly outdated)
 
== External links ==
 
* [https://www.midi.org/midi-articles/microtuning-and-alternative-intonation-systems Microtuning and Alternative Intonation Systems], by [[Jacky Ligon]]. Sep 2020. MIDI.org.
* [https://producelikeapro.com/blog/getting-started-making-microtonal-music/ Making Microtonal Music is Easier Than You’d Think], by Michael W. Dean (aka SyntheticThought). July 1, 2021. Produce Like a Pro. (also archived at the Xenharmonic Wiki, as [[Making Microtonal Music is Easier Than You’d Think|Part 1]] and [[Making Microtonal Music is Easier Than You’d Think, Part 2|Part 2]])
* [https://newmusicusa.org/nmbx/essential-tools-for-xenharmonic-music/ Essential Tools for Xenharmonic Music]. 2017. Newmusic USA.
* [[wikipedia:MIDI_tuning_standard|MIDI tuning standard]]. Wikipedia.
* [https://www.huygens-fokker.org/scala/scl_format.html Scala scale file (.SCL) format specification]. Huygens-Fokker Foundation.
* [https://www.huygens-fokker.org/scala/help.htm#mappings Scala keyboard mapping file (.KBM) format specification]. Huygens-Fokker Foundation.
* [https://sevish.com/music-resources/#tuning-files Resources for Microtonal Music § Tuning Files]. Sevish Music.
* [https://github.com/xenharmonic-devs/scale-workshop/wiki/Import-export-tunings Scale Workshop manual: Import Export Tunings]. Scale Workshop.
*[https://www.mizzan.de/anamark-format Anamark tuning file (.TUN) format]. Mizzen Microtonal Piano.
* Tutorial for creating TUN files with Scala. 2003. Huygens-Fokker Foundation. ([https://www.huygens-fokker.org/scala/Scala_TUN_Tutorial.pdf PDF])