User:Mousemambo/Document draft: Difference between revisions
Mousemambo (talk | contribs) continued development; moved some things into Appendix sections |
Mousemambo (talk | contribs) No edit summary |
||
| Line 5: | Line 5: | ||
'''DRAFT''' ==== Proposed page title: '''<big>Guide to Tuning a Software Synth in a DAW</big>''' ==== '''DRAFT''' | '''DRAFT''' ==== Proposed page title: '''<big>Guide to Tuning a Software Synth in a DAW</big>''' ==== '''DRAFT''' | ||
This guide describes some common methods for making music set in microtonal or other alternative tuning systems | This guide describes some common methods for making music set in microtonal or other alternative tuning systems, by using a [[List of microtonal software plugins#Instrument plugins with microtonal support|software synthesizer]] running inside a [[DAWs|digital audio workstation (DAW)]]. It describes scenarios in which each of those methods are effective, and procedures for configuring the software using that method. The examples given will use the Surge XT synth running inside the Reaper DAW, but similar procedures and reasoning will apply to other synths and DAWs. Therefore this guide will go into some detail to help give you the understanding needed to use these tuning methods with other synth-DAW combinations. | ||
Just want to start making non-standard tuning | Just want to start making music set in a non-standard tuning in your DAW? You can skip to the section "[[User:Mousemambo/Document draft#Method 2: Set a tuning using a Scala tuning file and keyboard mapping file|Set a tuning using a Scala tuning file and keyboard mapping file]]." Don't want to use a DAW? See "[[User:Mousemambo/Document draft#Tuning Surge XT without a DAW in standalone mode|Tuning Surge XT without a DAW in standalone mode]]" in the appendix. | ||
There are many other ways to create music with alternative tuning, like using [[List of music software|other software]], your voice, or a [[Instruments|physical musical instrument]]. This guide only explores one: a synth in a DAW. Don't know what "alternative tuning" means? Please visit the Xenharmonic wiki's [[Main Page|Main page]]. | There are many other ways to create music with alternative tuning, like using [[List of music software|other software]], your voice, or a [[Instruments|physical musical instrument]]. This guide only explores one: a synth in a DAW. Don't know what "alternative tuning" means? Please visit the Xenharmonic wiki's [[Main Page|Main page]]. | ||
== Introduction== | == Introduction== | ||
[TODO: Generalize this paragraph.] Surge XT | [TODO: Generalize this paragraph.] There are several methods possible for using the Surge XT synth within the Reaper DAW to create music set in microtonal or other uncommon tuning systems. Which configuration method you choose will depend on the larger context in which you're working and your specific needs, which will be explored below. Surge XT is a free but powerful software synthesizer that has extensive support for alternative tunings. Reaper is a popular and inexpensive DAW that fully supports all of Surge XT's possibilities for using alternative tuning systems. This tutorial was last verified using Surge XT version 1.2.3 and Reaper version 6.80 in August 2023. | ||
You'll find links below to sections of the Xen wiki's "[[User:Mousemambo/Tuning methods|Tuning methods]]" article [currently just a draft] that will offer you a deeper understanding of the components used here and how they work. | You'll find links below to sections of the Xen wiki's "[[User:Mousemambo/Tuning methods|Tuning methods]]" article [currently just a draft] that will offer you a deeper understanding of the components used here and how they work. | ||
This tutorial's instructions | This tutorial's instructions use Surge XT as a synth example, and Reaper as a DAW example, and assume you have them already installed on your computer. They also assume that you know how to create an instrument track in Reaper and load a plugin instrument like Surge XT onto it, but if you don't then instructions can be found below in the Appendix section "[[User:Mousemambo/Document draft#Create an instrument track in the Reaper DAW|Create an instrument track in the Reaper DAW]]." The instructions also assume you are using a standard [[Keyboard|piano keyboard]] (i.e. Halberstadt format) in virtual or physical form, although [[Isomorphic keyboard|non-standard keyboards]] are supported by these instructions. | ||
==Methods for setting a tuning | Use cases | Scenarios | Configurations== | ==Methods for setting a tuning | Use cases | Scenarios | Configurations== | ||
[I need to think further about how I want to name these use cases. I might prefer something that says more about why rather than what or how. But there can be several different "why" use cases for each the configurations named. So I might leave them as they are, call this section "Methods" and have the first section after the title and before "Advantages" be "Scenarios" for describing typical use cases for that method. I might remove the "Method N" prefix, but its useful in this doc to quickly refer people to a method by number rather than writing out the whole name.] | [I need to think further about how I want to name these use cases. I might prefer something that says more about why rather than what or how. But there can be several different "why" use cases for each the configurations named. So I might leave them as they are, call this section "Methods" and have the first section after the title and before "Advantages" be "Scenarios" for describing typical use cases for that method. I might remove the "Method N" prefix, but its useful in this doc to quickly refer people to a method by number rather than writing out the whole name.] | ||
There are many ways to configure a synth like Surge XT to use a non-standard tuning in a DAW like Reaper, | There are many ways to configure a synth like Surge XT to use a non-standard tuning in a DAW like Reaper, named here as "methods." There are advantages and disadvantages to each. There are also other less common methods that might be appropriate for special cases. If none of the scenarios given below describe your own needs, then you may have one of those special cases, and are invited to review the "[[User:Mousemambo/Tuning methods|Tuning methods]]" article to explore more possibilities and go deeper. | ||
To use this section, you might choose just to read the "Scenarios" section of each method to find something that is close to the actual scenario in which you plan to use Surge XT and Reaper. Then follow the "Procedure" for that method. Or you may want to read all the "Scenarios," "Advantages," and "Disadvantages" of every method to gain a strong understanding of all these possibilities and be prepared for many scenarios. | To use this Methods section, you might choose just to read the "Scenarios" section of each method to find something that is close to the actual scenario in which you plan to use Surge XT and Reaper. Then follow the "Procedure" for that method. Or you may want to read all the "Scenarios," "Advantages," and "Disadvantages" of every method to gain a strong understanding of all these possibilities and be prepared for many scenarios. | ||
=== Method 1: Set a tuning directly in Surge XT itself === | === Method 1: Set a tuning directly in Surge XT itself === | ||
[Briefly: What is | [Briefly: What is the tuning editor? Use Surge's tuning editor to recreate a custom tuning, perhaps using the example of Ptolemy's Intense Diatonic. Scenarios: TBD. Advantages: No additional component complexity. Can be easy for simple tunings you're already familiar with. Disadvantages: Can be time consuming compared to using a tuning file, with an unfamiliar or complex tuning. Needs to be redone for each new instrument instance. Tuning can't be quickly applied to other instruments.] | ||
==== Scenarios ==== | ==== Scenarios ==== | ||
| Line 40: | Line 40: | ||
===Method 2: Set a tuning using a Scala tuning file and keyboard mapping file=== | ===Method 2: Set a tuning using a Scala tuning file and keyboard mapping file=== | ||
[Briefly: A tuning file is.... A keyboard mapping file is.... The Scala format tuning files and keyboard mapping files together work to .... If you omit using a keyboard mapping file.... For more about Scala tuning and keyboard mapping files, see the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article. Ultimately, there should be articles that are companions to the existing "[[Anamark tuning file format]]" page (which almost certainly should be renamed "Anamark tuning file".. the existing page title should redirect to a section of the new page), named "[[User:Mousemambo/Scala tuning file|Scala tuning file]]" and "[[User:Mousemambo/Scala keyboard mapping file|Scala keyboard mapping file]]".] | [Briefly: A tuning file is.... A keyboard mapping file is.... The Scala format tuning files and keyboard mapping files together work to .... If you omit using a keyboard mapping file.... For more about Scala tuning and keyboard mapping files, see the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article. Ultimately, there should be articles that are companions to the existing "[[Anamark tuning file format]]" page (which almost certainly should be renamed "Anamark tuning file".. the existing page title should redirect to a section of the new page), named "[[User:Mousemambo/Scala tuning file|Scala tuning file]]" and "[[User:Mousemambo/Scala keyboard mapping file|Scala keyboard mapping file]]" or a single "[[User:Mousemambo/Scala tuning system|Scala tuning system]]" article might incorporate both those as sections at least initially.] | ||
====Scenarios==== | ====Scenarios==== | ||
[What circumstances would lead to this being the best (or at least a good) choice among the methods listed here? The "why that is" would be answered in the next two sections.] | [What circumstances would lead to this being the best (or at least a very good) choice among the methods listed here? The "why that is" would be answered in the next two sections.] | ||
====Advantages==== | ====Advantages==== | ||
| Line 60: | Line 60: | ||
##* [Say something here about tuning file naming standards, and they extremely terse abbreviations used for some classes of tunings.] | ##* [Say something here about tuning file naming standards, and they extremely terse abbreviations used for some classes of tunings.] | ||
#Load a [[User:Mousemambo/Scala keyboard mapping file|Scala keyboard mapping file]] (.kbm), for example the "Halberstadt 60-440-69.kbm" file [which *is* international ISO tuning standard]. [Note here that other keyboard layouts are supported by other keyboard mapping files.] | #Load a [[User:Mousemambo/Scala keyboard mapping file|Scala keyboard mapping file]] (.kbm), for example the "Halberstadt 60-440-69.kbm" file [which *is* international ISO tuning standard]. [Note here that other keyboard layouts are supported by other keyboard mapping files.] | ||
#*Note that without a Scala keyboard mapping file (.kbm) also loaded, the resulting tuning may not be what you expect. Surge XT like most synths will assume a default tonic frequency and keyboard mapping that sets the first note specified in the tuning file as MIDI Note C.60 and the reference pitch as international ISO standard pitch (MIDI A.69=440.000Hz). [Or will it? Seems undocumented. In fact, it does not. Default in Surge XT 1.2.3 is a tonic of C.60 and the reference pitch is C.60=261.626Hz, which is close but not international standard.] However, if we are using a just intonation scale and music with a tonic of F (F4, MIDI 65, 349.23 Hz), we need to use a keyboard mapping file to ensure the tuning is correct. | #*Note that without a Scala keyboard mapping file (.kbm) also loaded, the resulting tuning may not be what you expect. Surge XT like most synths will assume a default tonic frequency and keyboard mapping that sets the first note specified in the tuning file as MIDI Note C.60 and the reference pitch as international ISO standard pitch (MIDI A.69=440.000Hz). [Or will it? Seems undocumented. In fact, it does not. Default in Surge XT 1.2.3 is a tonic of C.60 and the reference pitch is C.60=261.626Hz, which is close to but not international standard.] However, if for example we are using a just intonation scale and music with a tonic of F (F4, MIDI note 65, 349.23 Hz), we need to use a keyboard mapping file to ensure the tuning is correct. | ||
#*Remember that when you load a Scala tuning file you should always load a keyboard mapping file to prevent mistuned surprises. To learn more about how to use Scala tuning and keyboard mapping files, including what to do when your instrument doesn't offer the option to load a keyboard mapping file, see [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]]. | #*Remember that when you load a Scala tuning file you should always load a keyboard mapping file to prevent mistuned surprises. To learn more about how to use Scala tuning and keyboard mapping files, including what to do when your instrument doesn't offer the option to load a keyboard mapping file, see [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]]. | ||
#Optionally, if you understand Scala tuning and mapping data, you may wish to open Surge XT's Tuning editor at this time (Menu > Tuning > Open tuning editor...) to confirm the correct data was loaded from the files. | #Optionally, if you understand Scala tuning and mapping data, you may wish to open Surge XT's Tuning editor at this time (Menu > Tuning > Open tuning editor...) to confirm the correct data was loaded from the files. | ||
| Line 68: | Line 68: | ||
Surge XT also provides a button "Tune" under the label "Status" along the top of its window. If a custom tuning has not yet been added during the current session, clicking the button will reveal the same list of options as Menu > Tuning. If a custom tuning has been loaded, the Tune button will be lit (bright not dark), and clicking it will turn that tuning off (back to the software's default [[12edo|12-EDO tuning]]) or back on. | Surge XT also provides a button "Tune" under the label "Status" along the top of its window. If a custom tuning has not yet been added during the current session, clicking the button will reveal the same list of options as Menu > Tuning. If a custom tuning has been loaded, the Tune button will be lit (bright not dark), and clicking it will turn that tuning off (back to the software's default [[12edo|12-EDO tuning]]) or back on. | ||
Surge XT doesn't directly support Anamark tuning files (.tun), which are an alternative to using the Scala two-file tuning system, | Surge XT doesn't directly support Anamark tuning files (.tun), which are an alternative to using the Scala two-file tuning system, and [[User:Mousemambo/Document draft#Anamark tuning files|described in the Appendix]]. | ||
===Method 3: Set a tuning using a tuning plugin=== | ===Method 3: Set a tuning using a tuning plugin=== | ||
| Line 116: | Line 116: | ||
=== Anamark tuning files === | === Anamark tuning files === | ||
Scala does not support Anamark format (.tun) tuning files, which some other synths do support. However, if you have only an | Scala does not support [[Anamark tuning file format|Anamark format (.tun) tuning files]], which some other synths do support. However, if you have only an Anamark format tuning file for your tuning, there are several converter tools that can seamlessly use that file to generate a tuning file in Scala format along with a keyboard mapping file if the .tun file includes the needed mapping data. [Do .tun files always include keyboard mapping data?] [Name some good converters and provide links here and below in External links.] | ||
[Briefly, describe why you might or might not prefer to use an Anamark tuning file instead of the Scala two-file re-tuning system.] | [Briefly, describe why you might or might not prefer to use an Anamark tuning file instead of the Scala two-file re-tuning system.] | ||