User:Mousemambo/Workbench: Difference between revisions

Line 40:

== Outline for a Tuning Methods page ==

Last updated 2023-Aug-02. Note that although much of the info will be in the Tuning Methods page itself, some other info might best be split out into its own page (e.g. there is already an [[Anamark tuning file format]] page). Also, any how-to [[:Category:Guides]] pages would be separate, and links could be provided to existing outside how-to instructions that have text or video format (urgh...link maintenance sucks).

Last updated 2023-Aug-03.

I'm inventing a distinction between "Tuning plugins" and "Retuners" even though tuning plugins have been understood as a subset of retuners. People are calling them "tuning plugins" and not using the term ~~returners~~ so this makes sense to me.

Note that although much of the info will be in the Tuning Methods page itself, some other info might best be split out into its own page (e.g. there is already an [[Anamark tuning file format]] page). Also, any how-to [[:Category:Guides]] pages would be separate, and links could be provided to existing outside how-to instructions that have text or video format (urgh...link maintenance sucks).

This writing needs to use descriptions that apply to both hardware (integrated synth & component systems) and software (standalone and plugin) instruments. Because this would probably grow unwieldy if the writing went into to much depth about *how* the provided information applies to each those types of instruments, it would be wiser to split out into separate pages any how-to details or implementation-specific info, beyond very general ones (e.g. that there is a drop-down menu selector or the ability to load an outside file). Those additional pages might be instrument-specific (e.g. how to implement the various tuning methods in the Kontakt sampler system) or method-specific (how to use SCL/KBM files in several popular electronic or virtual instruments. I defer deciding which of those two is preferable.

I'm inventing a distinction between "Tuning plugins" (operate within a plugin chain) and "Retuners" (are standalone apps) even though tuning plugins have been understood as a subset of retuners. People are calling them "tuning plugins" and not using the term retuners so this makes sense to me.

The description of each component that has an alternative, e.g. tuning files vs. direct tuning, Kontakt scripts vs. Scala tuning, needs to state the advantages and disadvantages of that component compared to the common alternatives.

* Intro

** Why? We need to tell electronic and software musical instruments what tuning system to use when they receive controller input or MIDI data.

** 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.

** ~~How~~? ~~Direct~~ tuning ~~info~~, or a tuning file ~~sometimes with a~~ mechanism ~~to tell~~ the instrument to use ~~that tuning (~~and sometimes also how to use it).

** What? Either the instrument itself, or an intermediary component dedicated to tuning, needs 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 instruments have ~~their own input~~ system for tuning information, via dropdown menu selection or custom tuning settings. 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: 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.

** 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 that 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 that method. This writing is intended to ensure that when you read that manual, you understand what it's saying and can make informed decisions.

* Direct tuning information. Some musical instruments have a built-in system for tuning information, via dropdown menu selection or custom tuning settings. Note: I don't like the expression "direct tuning" but can't think of something better right now.

** Kontakt "microtuning" built-in script. Because Kontakt is so important, this needs to be stated explicitly, and a how-to link provided.

** Other instruments (e.g. <list of example instruments>)

* Tuning files

** Intro. What are tuning files?

** Intro

*** 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.

*** What are the important features of tuning files? They may establish intervals, frequency assignment, controller data mapping, and more.

** Anamark (.TUN) tuning files

** Kontakt scripts

Line 57:

Line 67:

*** Scala tuning files (.SCL)

*** Scala keyboard mapping files (.KBM)

* Retuners ~~and~~ tuning plugins

* Retuners or tuning plugins

** 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.

** 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 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??).

** 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

** ~~Retuners~~. Software running standalone (independent from a DAW or plugin host), operating between a controller and software or hardware instrument.

** 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 and for CV-controlled modular synths, independent of an all-purpose computer (PC, tablet, phone).

* Other tuning methods

** MIDI Tuning Specification (MTS)

** Other SysEx-based tuning methods?

** Other SysEx-based tuning methods (?)

* Deprecated and obsolete tuning methods

** RPN tuning

==Indian music==

Existing pages addressing microtonality in Indian music:

Existing pages addressing microtonality in various branches of Indian music (e.g. Hindustani classical, Carnatic classical, Sikh, etc.):

*[[Indian]]

@@ Line 40: / Line 40: @@
 == Outline for a Tuning Methods page ==
-Last updated 2023-Aug-02. Note that although much of the info will be in the Tuning Methods page itself, some other info might best be split out into its own page (e.g. there is already an [[Anamark tuning file format]] page). Also, any how-to [[:Category:Guides]] pages would be separate, and links could be provided to existing outside how-to instructions that have text or video format (urgh...link maintenance sucks).
+Last updated 2023-Aug-03.
-I'm inventing a distinction between "Tuning plugins" and "Retuners" even though tuning plugins have been understood as a subset of retuners. People are calling them "tuning plugins" and not using the term returners so this makes sense to me.
+Note that although much of the info will be in the Tuning Methods page itself, some other info might best be split out into its own page (e.g. there is already an [[Anamark tuning file format]] page). Also, any how-to [[:Category:Guides]] pages would be separate, and links could be provided to existing outside how-to instructions that have text or video format (urgh...link maintenance sucks).
+This writing needs to use descriptions that apply to both hardware (integrated synth & component systems) and software (standalone and plugin) instruments. Because this would probably grow unwieldy if the writing went into to much depth about *how* the provided information applies to each those types of instruments, it would be wiser to split out into separate pages any how-to details or implementation-specific info, beyond very general ones (e.g. that there is a drop-down menu selector or the ability to load an outside file). Those additional pages might be instrument-specific (e.g. how to implement the various tuning methods in the Kontakt sampler system) or method-specific (how to use SCL/KBM files in several popular electronic or virtual instruments. I defer deciding which of those two is preferable.
+I'm inventing a distinction between "Tuning plugins" (operate within a plugin chain) and "Retuners" (are standalone apps) even though tuning plugins have been understood as a subset of retuners. People are calling them "tuning plugins" and not using the term retuners so this makes sense to me.
+The description of each component that has an alternative, e.g. tuning files vs. direct tuning, Kontakt scripts vs. Scala tuning, needs to state the advantages and disadvantages of that component compared to the common alternatives.
 * Intro
-** Why? We need to tell electronic and software musical instruments what tuning system to use when they receive controller input or MIDI data.
+** 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.
-** How? Direct tuning info, or a tuning file sometimes with a mechanism to tell the instrument to use that tuning (and sometimes also how to use it).
+** What? Either the instrument itself, or an intermediary component dedicated to tuning, needs 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 instruments have their own input system for tuning information, via dropdown menu selection or custom tuning settings. 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: 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.
+** 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 that 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 that method. This writing is intended to ensure that when you read that manual, you understand what it's saying and can make informed decisions.
+* Direct tuning information. Some musical instruments have a built-in system for tuning information, via dropdown menu selection or custom tuning settings. Note: I don't like the expression "direct tuning" but can't think of something better right now.
 ** Kontakt "microtuning" built-in script. Because Kontakt is so important, this needs to be stated explicitly, and a how-to link provided.
 ** Other instruments (e.g. <list of example instruments>)
 * Tuning files
-** Intro. What are tuning files?
+** Intro
+*** 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.
+*** What are the important features of tuning files? They may establish intervals, frequency assignment, controller data mapping, and more.
 ** Anamark (.TUN) tuning files
 ** Kontakt scripts
@@ Line 57: / Line 67: @@
 *** Scala tuning files (.SCL)
 *** Scala keyboard mapping files (.KBM)
-* Retuners and tuning plugins
+* Retuners or tuning plugins
-** 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.
+** 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 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??).
 ** 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
-** Retuners. Software running standalone (independent from a DAW or plugin host), operating between a controller and software or hardware instrument.
+** 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 and for CV-controlled modular synths, independent of an all-purpose computer (PC, tablet, phone).
 * Other tuning methods
 ** MIDI Tuning Specification (MTS)
-** Other SysEx-based tuning methods?
+** Other SysEx-based tuning methods (?)
 * Deprecated and obsolete tuning methods
 ** RPN tuning
 ==Indian music==
-Existing pages addressing microtonality in Indian music:
+Existing pages addressing microtonality in various branches of Indian music (e.g. Hindustani classical, Carnatic classical, Sikh, etc.):
 *[[Indian]]