User:Mousemambo/Document draft: Difference between revisions

Mousemambo (talk | contribs)
No edit summary
Mousemambo (talk | contribs)
continued development; moved some things into Appendix sections
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 alternative methods for making music set in microtonal or other alternative tuning systems with 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 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.
This guide describes some common methods for making music set in microtonal or other alternative tuning systems with 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 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 playing? You can skip ahead 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]]."
Just want to start making non-standard tuning music in your DAW? You can skip ahead 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]].
Line 16: Line 16:


This tutorial's instructions assume you have Surge XT and Reaper 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 other keyboards are supported by these instructions.
This tutorial's instructions assume you have Surge XT and Reaper 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 other keyboards are supported by these instructions.
However, Surge XT can also run in standalone mode, without any DAW. A significant drawback to that configuration is you won't be able to record your playing as MIDI notes, unless you have some additional component doing the recording. The common use cases for running Surge XT in standalone mode are for live performance where you don't want the extra complexity of running a DAW, or when you're just playing casually and don't need to record MIDI. In standalone mode, Method 1 or Method 2 given below can be used to re-tune Surge XT.


==Methods for setting a tuning | Use cases | Scenarios | Configurations==
==Methods for setting a tuning | Use cases | Scenarios | Configurations==
Line 27: Line 25:


=== Method 1: Set a tuning directly in Surge XT itself ===
=== Method 1: Set a tuning directly in Surge XT itself ===
[Briefly: What is a 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 complexity. Can be easy for simple tunings you're already familiar with. Disadvantages: Can be time consuming compared to using a tuning file. Needs to be redone for each new instance. Tuning can't be quickly applied to other instruments.]
[Briefly: What is a 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 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 ====
...
 
==== Advantages ====
...
 
==== Disadvantages ====
...
 
==== Procedure ====
...


===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.]
[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]]".]


====Scenarios====
====Scenarios====
Line 43: Line 53:
==== Procedure====
==== Procedure====


#Create a [[User:Mousemambo/Document draft#Create an instrument track in the Reaper DAW|new instrument track in Reaper]].
#Launch the Reaper application, create a [[User:Mousemambo/Document draft#Create an instrument track in the Reaper DAW|new instrument track in Reaper]], and add Surge XT as a plugin on that instrument track. Note: If you are not using a DAW, and [[User:Mousemambo/Document draft#Tuning Surge XT without a DAW in standalone mode|using Surge XT in standalone mode]] instead, replace this step with: Launch the Surge XT standalone application.
#Add Surge XT as a plugin on that instrument track.
#Load a [[User:Mousemambo/Scala tuning file|Scala tuning file]] (.scl) into Surge XT as follows:
#Load a Scala tuning file (.scl) into Surge XT as follows:
## In Surge XT's Menu (found in the bottom right corner) select the Tuning option, then choose "Load .scl tuning..."
## In Surge XT's Menu (found in the bottom right corner) select the Tuning option, then choose "Load .scl tuning..."
##Use the resulting file selection popup to choose one of the [ideally 12-tone for keyboard mapping simplicity] Scala tuning files that come with Surge XT, e.g. [something beginners might have read about and would recognize,] like just intonation's Ptolemy_intense_diatonic.scl or meantone's WerckmeisterIII_equal_beating.scl, or instead choose [something named in condensed code like] ED3-12.scl.
##Use the resulting file selection popup to choose one of the [ideally 12-tone for keyboard mapping simplicity] Scala tuning files that come with Surge XT, e.g. [something beginners might have read about and would recognize,] like just intonation's Ptolemy_intense_diatonic.scl or meantone's WerckmeisterIII_equal_beating.scl, or instead choose [something named in condensed code like] ED3-12.scl. {I realize Scala XT at this moment only comes with two tuning files beginners will recognize by name, and one is 12-EDO.]
##* [Say something about tuning files and what they do, along with that they use various methods of establishing tunings.]
##* [Say something about tuning files and what they do, along with that they use various methods of establishing tunings.]
##* [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 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, Surge XT might 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 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.
#*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.
#Optionally, test the tuning to ensure it is correct.
#Optionally, test the tuning to ensure it's correct.


====Notes====
====Notes====
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.


Scala does not support Anamark format (.tun) tuning files, which some other synths do support. However, if you have only an Anamark file for your tuning, there are several 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.]
Surge XT doesn't directly support Anamark tuning files (.tun), which are an alternative to using the Scala two-file tuning system, as [[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 66: Line 75:
There is no convincing case for using this tuning method with Surge XT, AFAIK. If you want to set a custom tuning, or load a tuning file, or respond to an MTS-ESP tuning source, you can do all those in Surge XT without any need for an additional plugin to provide those functionalities.
There is no convincing case for using this tuning method with Surge XT, AFAIK. If you want to set a custom tuning, or load a tuning file, or respond to an MTS-ESP tuning source, you can do all those in Surge XT without any need for an additional plugin to provide those functionalities.


[Rather than provide instructions for using a tuning plugin here, I could instead do that in a different Guide for using a synth that requires it like Vital, which can load a Scala tuning file but not a keyboard mapping file, and supports MPE tuning. If I expand this doc to include another synth, I might need to split this Method into 3a ... using MPE, and 3b ... using pitch bend. For more about tuning plugins, see the [[User:Mousemambo/Tuning methods#Tuning plugins and retuners|Tuning methods]] article.]
[Rather than provide instructions for using a tuning plugin here, I could instead do that in a different Guide for using a synth that requires it like Vital, which can load a Scala tuning file but not a keyboard mapping file, and supports MPE tuning. If I expand this doc to include another synth, I probably will need to split this Method into 3a ... using MPE, and 3b ... using pitch bend. For more about tuning plugins, see the [[User:Mousemambo/Tuning methods#Tuning plugins and retuners|Tuning methods]] article.]
 
==== Scenarios ====
...
 
==== Advantages ====
...
 
==== Disadvantages ====
...
 
==== Procedure ====
...


===Method 4: Set a tuning using MTS-ESP===
===Method 4: Set a tuning using MTS-ESP===
[Briefly: Add an MTS-ESP tuning source plugin on one track, and Surge XT on another. Load a tuning file into the MTS-ESP source plugin. Set Surge XT to listen to MTS-ESP. Confirm that the MTS-ESP source has connected. Note that, unlike Surge XT, most available electronic instruments at this time (August 2023) don't support MTS-ESP tuning although some do. Note that if I choose to expand by mentioning other synths, I need to say that some of those can be re-tuned by adding a tuning plugin that **does** support MTS-ESP... Method 4a: using a tuning plugin. Other ways to structure this are possible and will be considered.]
[Briefly: Add an MTS-ESP tuning source plugin on one track, and Surge XT on another. Load a tuning file into the MTS-ESP source plugin. Set Surge XT to listen to MTS-ESP. Confirm that the MTS-ESP source has connected. Note that, unlike Surge XT, most available electronic instruments at this time (August 2023) don't support MTS-ESP tuning although some do. Note that if I choose to expand by mentioning other synths, I need to say that some of those can be re-tuned by adding a tuning plugin that **does** support MTS-ESP... Method 4a: using a tuning plugin. Other ways to structure this are possible and will be considered.]
==== Scenarios ====
...
==== Advantages ====
...
==== Disadvantages ====
...
==== Procedure ====
...


==How to test the tuning==
==How to test the tuning==
Line 77: Line 110:


===Create an instrument track in the Reaper DAW===
===Create an instrument track in the Reaper DAW===
[How to create an instrument track in Reaper. How to use it... load a VST virtual instrument.]
[How to create an instrument track in Reaper. And how to use it... load a VST virtual instrument.]
 
=== Tuning Surge XT without a DAW in standalone mode ===
Surge XT can also run in standalone mode, without any DAW. A significant drawback to that configuration is you won't be able to record your playing as MIDI notes, unless you have some additional component doing the recording. The common use cases for running Surge XT in standalone mode are for live performance where you don't want the extra complexity of running a DAW, or when you're just playing casually and don't need to record MIDI. In standalone mode, only [[User:Mousemambo/Document draft#Method 1: Set a tuning directly in Surge XT itself|Method 1]] or [[User:Mousemambo/Document draft#Method 2: Set a tuning using a Scala tuning file and keyboard mapping file|Method 2]] given above can be used to re-tune Surge XT.
 
=== Anamark tuning files ===
Scala does not support Anamark format (.tun) tuning files, which some other synths do support. However, if you have only an [[Anamark tuning file format|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.]


==See also==
==See also==