User:Mousemambo/Document draft: Difference between revisions
Mousemambo (talk | contribs) No edit summary |
Mousemambo (talk | contribs) No edit summary |
||
| Line 11: | Line 11: | ||
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, the first two use cases below [be specific once section titles are settled] can be used to tune Surge XT. | 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, the first two use cases below [be specific once section titles are settled] can be used to tune Surge XT. | ||
== Methods | 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 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.] | ||
There are many ways to configure Surge XT to use a non-standard tuning in Reaper, listed here as "methods." But there are advantages and disadvantages to each. 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 the possibilities and be prepared for many scenarios. | There are many ways to configure Surge XT to use a non-standard tuning in Reaper, listed here as "methods." But there are advantages and disadvantages to each. 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 the possibilities and be prepared for many scenarios. | ||
=== | === Set a tuning directly in Surge XT itself === | ||
[Briefly: Use Surge's tuning editor to recreate a custom tuning, using the example of a Ptolemy's Intense Diatonic.] | [Briefly: Use Surge's tuning editor to recreate a custom tuning, using the example of a Ptolemy's Intense Diatonic.] | ||
=== | === Set a tuning with a Scala tuning file and keyboard mapping file === | ||
==== Scenarios ==== | ==== Scenarios ==== | ||
| Line 48: | Line 48: | ||
Scala does not support Anamark format (.tun) tuning files, which some other synths do support. However, if you have only a .tun 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 included 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.] | Scala does not support Anamark format (.tun) tuning files, which some other synths do support. However, if you have only a .tun 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 included 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.] | ||
=== | === Set a tuning with a tuning plugin === | ||
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 will 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.] | 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 will 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.] | ||
=== | === 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.] | [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.] | ||