User:Mousemambo/Document draft: Difference between revisions
Mousemambo (talk | contribs) continued development and refinement |
Mousemambo (talk | contribs) No edit summary |
||
Line 37: | Line 37: | ||
* No additional component complexity. | * No additional component complexity. | ||
* Can be quick and easy for simple tunings you're very familiar with. | * Can be quick and easy to set up for simple tunings you're very familiar with. | ||
* May include a [[User:Mousemambo/Document draft#Tuning system explorer|tuning development environment]] to assist with developing new tunings. | |||
'''Disadvantages''' | '''Disadvantages''' | ||
* Very few synths include a tuning editor. | |||
* Can be time consuming with an unfamiliar or complex tuning, compared to using a tuning file. | * Can be time consuming with an unfamiliar or complex tuning, compared to using a tuning file. | ||
* Needs to be redone for each new instrument instance. | * Needs to be redone for each new instrument instance. | ||
Line 65: | Line 67: | ||
'''Advantages''' | '''Advantages''' | ||
* Quickly apply a tuning to your musical instrument. | * Quickly apply a prepared tuning to your musical instrument. | ||
* .... | * .... | ||
'''Disadvantages''' | '''Disadvantages''' | ||
* | * Not supported by most software synths. | ||
* Requires finding a Scala scale file and keyboard mapping file for your desired tuning, else... | |||
* Requires development of a Scala scale file and keyboard mapping file(s), and learning how to prepare them. | |||
* Generally doesn't include a [[User:Mousemambo/Document draft#Tuning development environment|tuning development environment]]. | |||
'''Instructions''' | '''Instructions''' | ||
Line 113: | Line 118: | ||
===Method 3: Set a tuning using a tuning plugin=== | ===Method 3: Set a tuning using a tuning plugin=== | ||
[What is a tuning plugin, also called a re-tuning plugin?] | [What is a tuning plugin, also called a re-tuning plugin?] [What different mechanisms do tuning plugins use to control a musical instrument?] | ||
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. 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 | [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 one. If I expand this doc to include another synth, I probably will need to split this Method into 3a ... using a tuning plugin with MPE, and 3b ... using a tuning plugin with multichannel pitch bend (and there are more possibilities). That seems like a lot! I think that a separate article "[[User:Mousemambo/Guide to using tuning plugins|Guide to using tuning plugins]]" is almost certainly the way to go, with sections for MPE, monophonic pitch bend, polyphonic pitch bend (through multichannel), etc. using a few different tuning plugins (e.g. select from [https://oddsound.com/mtsespsuite.php MTS-ESP Suite], [https://entonal.studio/ Entonal Studio], [https://wilsonic.co/ Wilsonic MTS-ESP], [https://infinitone.com/ InfinitoneDMT], or [https://www.pitchinnovations.com/products/fluid-pitch/ Fluid Pitch]).] | ||
* '''Scenarios''' | * '''Scenarios''' | ||
** ... | ** ... | ||
* '''Advantages''' | * '''Advantages''' | ||
** Support for many synths that can't be re-tuned any other way. | |||
** May include a [[User:Mousemambo/Document draft#Tuning system explorer|tuning development environment]] to assist with developing new tunings. | |||
** ... | ** ... | ||
* '''Disadvantages''' | * '''Disadvantages''' | ||
** Added complexity. | |||
** ... | ** ... | ||
Line 135: | Line 143: | ||
===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 | [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 MTS-ESP, Method 4b: using an MTS-ESP tuning plugin. Other ways to structure this are possible and will be considered.] | ||
'''Scenarios''' | '''Scenarios''' | ||
... | * ... | ||
'''Advantages''' | '''Advantages''' | ||
... | * MPE-ESP source plugin may include a [[User:Mousemambo/Document draft#Tuning development environment|tuning development environment]] to assist with developing new tunings. | ||
* ... | |||
'''Disadvantages''' | '''Disadvantages''' | ||
... | * Supported by relatively few software synths. | ||
* ... | |||
'''Instructions''' | '''Instructions''' | ||
Line 170: | Line 180: | ||
=== Tuning Surge XT without a DAW in standalone mode === | === 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 the synth 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. | 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 the synth 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. | ||
=== Tuning development environment === | |||
[What is a tuning explorer or tuning development environment? E.g. Scala, Entonal Studio, MTS-ESP Suite.] | |||
=== Anamark tuning files === | === Anamark tuning files === |