User:Mousemambo/Document 2 draft: Difference between revisions
Mousemambo (talk | contribs) Create initial draft of article with tentative title "Tuning base, tuning center, and tonic" |
Mousemambo (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
'''DRAFT''' ==== Proposed page title: '''<big>Tuning base, tuning center, and tonic</big>''' ==== '''DRAFT''' | '''DRAFT''' ==== Proposed page title: '''<big>Tuning base, tuning center, and tonic</big>''' ==== '''DRAFT''' | ||
''[see "Development notes" below.]'' | ''['''Parts of this writing are confused''', I know. Also see "Development notes" below.]'' | ||
In the context of defining a tuning, the terms "tuning base," "tuning center," and "tonic" are at the center of a great deal of confusion. Much of the problem comes from not recognizing when we are making assumptions based on early indoctrination into Western classical music theory, which contemporary music theory has grown past. The other major source of confusion is the common use of wrong terminology that blurs the lines between meanings, which the establishment of specific terminology is supposed to prevent. These both create serious obstacles to clear understanding and communication, which in a world of diverse cultural musics and expanded tunings are worth trying to overcome. | In the context of defining a tuning, the terms "tuning base," "tuning center," and "tonic" are at the center of a great deal of confusion. Much of the problem comes from not recognizing when we are making assumptions based on early indoctrination into Western classical music theory, which contemporary music theory has grown past. The other major source of confusion is the common use of wrong terminology that blurs the lines between meanings, which the establishment of specific terminology is supposed to prevent. These both create serious obstacles to clear understanding and communication, which in a world of diverse cultural musics and expanded tunings are worth trying to overcome. | ||
| Line 14: | Line 14: | ||
When defining a tuning using a tuning file or files, there are three questions that must be answered. | When defining a tuning using a tuning file or files, there are three questions that must be answered. | ||
*What notes are in the tuning and what are the intervals between them, regardless of their | *What notes are in the tuning and what are the intervals between them, regardless of their absolute pitch frequency? | ||
*What | *What absolute pitch frequencies are those notes? | ||
*Which specific controller keys, buttons, switches etc. should be assigned to each note? | *Which specific controller keys, buttons, switches etc. should be assigned to each note? | ||
If all you wish to know is what a tuning file or set of tuning files do, then now you know. You're done. If you want to know how a specific tuning file system solves those problems, things get more complicated. The journey is not brief, but many will find it rewarding. It's described here as a sequence of conceptual steps to make it easier to understand, but the actual software may follow a different path. | |||
==What does the Scala scale file do?== | ==What does the Scala scale file do?== | ||
| Line 25: | Line 25: | ||
The Scala scale file (.scl) establishes what notes are in the tuning and what are the intervals between them, without setting their absolute pitch. It also establishes one of those notes as the tuning base, by defining all the other notes by their relative frequency relationship (in cents or by frequency ratio) to that tuning base. Establishing a tuning base is the mechanism that will allow the other questions to be answered in the technical scheme that is the Scala tuning system. | The Scala scale file (.scl) establishes what notes are in the tuning and what are the intervals between them, without setting their absolute pitch. It also establishes one of those notes as the tuning base, by defining all the other notes by their relative frequency relationship (in cents or by frequency ratio) to that tuning base. Establishing a tuning base is the mechanism that will allow the other questions to be answered in the technical scheme that is the Scala tuning system. | ||
The conceptual tool that is a tuning base does not directly appear in Western classical music theory. It's related to the concepts of tonic and key in a confusing way that will be described later. But the tuning base is just a technical tool that operates in the context of needing to attach a tuning system to a musical instrument controller. | The tuning base can also be correctly referred to as the tuning base note, base note (easily confused with bass note), reference note (which is vague), 1/1 (referring to its intervallic relationship with itself), or (least clearly) the "middle note" which is how it's named in the [https://www.huygens-fokker.org/scala/help.htm#mappings Scala keyboard mapping file (.kbm) specification]. It is incorrect to refer to the tuning base as the tonic, root or key. The conceptual tool that is a tuning base does not directly appear in Western classical music theory. It's related to the concepts of tonic and key in a confusing way that will be described later. But the tuning base is just a technical tool that operates in the context of needing to attach a tuning system to a musical instrument controller. | ||
It is critical to recognize that the Scala scale file does not assign any pitch frequencies. All the Scala scale file does is declare the notes of the scale and their relative frequency relationships, then set one as the tuning base. That intervallic (also spelled intervalic) network can be slid to any location along the frequency spectrum, and any location within the controller field (e.g. keyboard span). The tuning base sets one of the notes as the anchor or handle of that network, which the Scala keyboard mapping file will use for the practical solution of establishing fixed pitch frequencies and fixed controller associations. | |||
==What does the Scala mapping file do?== | |||
How does the Scala keyboard mapping file answer our second two questions? How does it fix the tuning's intervallic network to the pitch frequency spectrum and the controller controls? The keyboard mapping file does this with four sections, two for each function. It's worth recognizing here that a "note" in the Scala tuning system always refers to a [[MIDI]] note. MIDI notes have conventional default 12-EDO concert pitch assignments, but retuning takes advantage of their freedom to be assigned to any pitch or sound. | |||
[The two sections below need work, and some things in them are definitely confused.] | |||
===Fix the tuning base defined by the scale file to a specific pitch frequency=== | ===Fix the tuning base defined by the scale file to a specific pitch frequency=== | ||
The first step performed by the Scale mapping file to establish fixed pitches, is to assign a pitch frequency to one of the notes within the tuning. That note is then defined as the tuning center | The first step performed by the Scale mapping file to establish fixed pitches, is to assign a pitch frequency to one of the notes within the tuning. That note is then defined as the reference note in the [https://www.huygens-fokker.org/scala/help.htm#mappings Scala keyboard mapping file specification], and is analogous to the tuning center in multi-stringed musical instruments. The pitch to which it's set is the reference pitch, pitch reference, pitch standard, or diapason. A tuning center is the note (or string) to which all the others are tuned. Once the tuning center and its pitch frequency is established, the intervallic network defined in the scale file infers the pitch frequency assignments of all the other notes in the tuning. It's important to be aware, though, that in the Scala mapping file system any note in the tuning can be chosen as the tuning center, not just the tuning base. | ||
For simplicity, many people creating Scala keyboard mapping files assign the tuning center to the same note as the tuning base and then specify its pitch frequency. The main reason people chose to assign the tuning center to a different note is because the ISO 16:1975 tuning standard defines the note concert A4 as 440.0 Hz precisely. In 12-EDO tuning that means the frequency of concert C4 (middle C) | For simplicity, many people creating Scala keyboard mapping files assign the tuning center to the same note as the tuning base and then specify its pitch frequency. The main reason people chose to assign the tuning center to a different note is because the ISO 16:1975 tuning standard defines the note concert A4 as 440.0 Hz precisely. In 12-EDO tuning that means the frequency of concert C4 (middle C) is calculated to be 440.0 * (the twelfth root of 2, raised to the negative ninth power) giving 261.625566... and the digits continue. That's not so tidy as 440 exact. So unless your tuning base is A4, placing your tuning precisely according to the ISO standard requires defining A4 as the tuning center and giving it a pitch frequency of 440.0 Hz exactly, regardless of what note is the tuning base. In practice, many people define C4 as 261.63 Hz exactly and ignore the error. | ||
So why not always assign C4 as tuning base and tuning center, equal to 261.63 Hz, and call it done? Because this only works for EDO tunings, since in non-EDO tunings the unequal intervals mean that it matters greatly which notes gets assigned to what pitch and what control on the controller. This will be examined more when we explore how the concept of a tonic fits into all this. | |||
===Attach the tuning base defined by the scale file to a control on the controller=== | ===Attach the tuning base defined by the scale file to a control on the controller=== | ||
To establish fixed pitches for the scale's notes, the mapping file | To establish fixed pitches for the scale's notes, the mapping file defines to what "note" (MIDI number) on the controller the tuning base must be attached. Musical instrument controllers, which are designed to be used for music with notes as it's generally produced by humans to date, need to be able to send discrete note-like data signals even though the frequency spectrum is continuous. This is clearly visualized on a standard piano keyboard, where the tuning base can be understood as being attached to one specific control: a keyboard key. In more complex controllers, the tuning base might be assigned to multiple duplicate controls but the idea is the same. | ||
===Establish to what controller controls all the other notes will be assigned=== | ===Establish to what controller controls all the other notes will be assigned=== | ||