User:Mousemambo/Document draft: Difference between revisions

Line 23:

==Methods for setting a tuning==

[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 don't like the "Method 1 Scenarios" style of sub-section heading, nor "Scenarios (Method 1)" or anything other than "Scenarios" -- but then I can't make them link targets because there would be multiple occurrences of a "Scenarios" sub-section heading. Need to ponder more.]

[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 don't like the "Method 1 Scenarios" style of sub-section heading, nor "Scenarios (Method 1)" or anything other than "Scenarios" — but then I can't make them link targets because there would be multiple occurrences of a "Scenarios" sub-section heading. Need to ponder more.]

Four common instrument-DAW configurations for alternative tunings, here called "methods," are presented below. There are advantages and disadvantages to each, given the scenarios described. There are also other less common methods that might be appropriate or necessary for other instruments and DAWs and for special cases. If none of the offered scenarios describe your own situation, then you're invited to review the extensive "[[User:Mousemambo/Tuning methods|Tuning methods]]" article to explore more possibilities.

Line 58:

'''''Direct tuning in Kontakt'''''

* If you are using a Kontakt sampler system instrument that is not locked, and whose operation will not be disrupted by the needed script changes (e.g. like some legato patches), there are two easy methods that may work to create certain tunings in Kontakt. Note that as of August 2023 the Kontakt 7 Factory library is locked, although the Kontakt 6 Factory library was is/was not.

* If you are using a Kontakt sampler system instrument that is not locked, and whose operation will not be disrupted by the needed script changes (e.g. like some legato patches will be), there are two easy methods that may work to create certain tunings in Kontakt. Note that as of August 2023 the Kontakt 7 Factory library instruments are all locked, although the Kontakt 6 Factory library was is/was not.

* Kontakt offers a simple microtuning script for ~~re-tuning~~ 12-notes per octave tunings. [Find an online illustration.] In brief: Wrench > Script editor > Preset > Factory > Tuning > Microtuning > Adjust each slider.

*# Kontakt offers a simple microtuning script for creating 12-notes per octave tunings. [Find an online illustration.] In brief: Wrench > Script editor > Preset > Factory > Tuning > Microtuning > Adjust each slider to an offset in cents from 12-EDO tuning.

* You can ~~also~~ quickly set an [[EDO]] of any size, as illustrated in this [https://chrisvaisvil.com/how-to-adjust-kontakt-4-instruments-to-any-edo/ page by Chris Vaisvil]. In brief: Wrench > Script editor > Preset > Factory > Tuning > Notes per Octave > Notes~~. More complex tunings in Kontakt require a custom script, as described in~~ the ~~[[User:Mousemambo/Guide to tuning the Kontakt sampler system|Guide to tuning the Kontakt sampler system]]~~. Unfortunately, Kontakt does not offer easy custom keyboard mapping for your custom EDO -- [https://sevish.com/2017/mapping-microtonal-scales-keyboard-scala/ linear keyboard mapping] will apply.

*# You can quickly set an [[EDO]] of any size, as illustrated on this [https://chrisvaisvil.com/how-to-adjust-kontakt-4-instruments-to-any-edo/ page by Chris Vaisvil]. In brief: Wrench > Script editor > Preset > Factory > Tuning > Notes per Octave > Notes > Set the number of notes. Unfortunately, Kontakt does not offer easy custom keyboard mapping for your custom EDO — [https://sevish.com/2017/mapping-microtonal-scales-keyboard-scala/ linear keyboard mapping] will apply.

* More complex tunings or keyboard mapping in Kontakt require a custom script, as described in the [to be written] [[User:Mousemambo/Guide to tuning the Kontakt sampler system|Guide to tuning the Kontakt sampler system]].

===Method 2: Set a tuning using a Scala scale file and keyboard mapping file===

Line 94:

Line 95:

'''Notes'''

[This whole section needs extensive review with regard to what should be moved out to the [[User:Mousemambo/Document draft#Appendix|Appendix on this page]], or the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article, what belongs in the [[User:Mousemambo/Scala tuning system|Scala tuning system]] article, or perhaps is best rendered in duplicate for reading simplicity. I am removing as much as possible from the Instructions section, but to where? For example, the complexity of the relationship between the Scala scale file's base note, the tuning's tuning center, and the music's tonic (if it has one) makes this a very difficult topic for beginners but it's critical for JI so something needs to be said in this article. But this doesn't seem to be the right place to explain it in great detail -- the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article is a better choice.]

[This whole section needs extensive review with regard to what should be moved out to the [[User:Mousemambo/Document draft#Appendix|Appendix on this page]], or the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article, what belongs in the [[User:Mousemambo/Scala tuning system|Scala tuning system]] article, or perhaps is best rendered in duplicate for reading simplicity. I am removing as much as possible from the Instructions section, but to where? For example, the complexity of the relationship between the Scala scale file's base note, the tuning's tuning center, and the music's tonic (if it has one) makes this a very difficult topic for beginners but it's critical for JI so something needs to be said in this article. But this doesn't seem to be the right place to explain it in great detail — the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article is a better choice.]

'''''More about Surge XT'''''

@@ Line 23: / Line 23: @@
 ==Methods for setting a tuning==
-[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 don't like the "Method 1 Scenarios" style of sub-section heading, nor "Scenarios (Method 1)" or anything other than "Scenarios" -- but then I can't make them link targets because there would be multiple occurrences of a "Scenarios" sub-section heading. Need to ponder more.]
+[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 don't like the "Method 1 Scenarios" style of sub-section heading, nor "Scenarios (Method 1)" or anything other than "Scenarios" — but then I can't make them link targets because there would be multiple occurrences of a "Scenarios" sub-section heading. Need to ponder more.]
 Four common instrument-DAW configurations for alternative tunings, here called "methods," are presented below. There are advantages and disadvantages to each, given the scenarios described. There are also other less common methods that might be appropriate or necessary for other instruments and DAWs and for special cases. If none of the offered scenarios describe your own situation, then you're invited to review the extensive "[[User:Mousemambo/Tuning methods|Tuning methods]]" article to explore more possibilities.
@@ Line 58: / Line 58: @@
 '''''Direct tuning in Kontakt'''''
-* If you are using a Kontakt sampler system instrument that is not locked, and whose operation will not be disrupted by the needed script changes (e.g. like some legato patches), there are two easy methods that may work to create certain tunings in Kontakt. Note that as of August 2023 the Kontakt 7 Factory library is locked, although the Kontakt 6 Factory library was is/was not.
+* If you are using a Kontakt sampler system instrument that is not locked, and whose operation will not be disrupted by the needed script changes (e.g. like some legato patches will be), there are two easy methods that may work to create certain tunings in Kontakt. Note that as of August 2023 the Kontakt 7 Factory library instruments are all locked, although the Kontakt 6 Factory library was is/was not.
-* Kontakt offers a simple microtuning script for re-tuning 12-notes per octave tunings. [Find an online illustration.] In brief: Wrench > Script editor > Preset > Factory > Tuning > Microtuning > Adjust each slider.
+*# Kontakt offers a simple microtuning script for creating 12-notes per octave tunings. [Find an online illustration.] In brief: Wrench > Script editor > Preset > Factory > Tuning > Microtuning > Adjust each slider to an offset in cents from 12-EDO tuning.
-* You can also quickly set an [[EDO]] of any size, as illustrated in this [https://chrisvaisvil.com/how-to-adjust-kontakt-4-instruments-to-any-edo/ page by Chris Vaisvil]. In brief: Wrench > Script editor > Preset > Factory > Tuning > Notes per Octave > Notes. More complex tunings in Kontakt require a custom script, as described in the [[User:Mousemambo/Guide to tuning the Kontakt sampler system|Guide to tuning the Kontakt sampler system]]. Unfortunately, Kontakt does not offer easy custom keyboard mapping for your custom EDO -- [https://sevish.com/2017/mapping-microtonal-scales-keyboard-scala/ linear keyboard mapping] will apply.
+*# You can quickly set an [[EDO]] of any size, as illustrated on this [https://chrisvaisvil.com/how-to-adjust-kontakt-4-instruments-to-any-edo/ page by Chris Vaisvil]. In brief: Wrench > Script editor > Preset > Factory > Tuning > Notes per Octave > Notes > Set the number of notes. Unfortunately, Kontakt does not offer easy custom keyboard mapping for your custom EDO — [https://sevish.com/2017/mapping-microtonal-scales-keyboard-scala/ linear keyboard mapping] will apply.
+* More complex tunings or keyboard mapping in Kontakt require a custom script, as described in the [to be written] [[User:Mousemambo/Guide to tuning the Kontakt sampler system|Guide to tuning the Kontakt sampler system]].
 ===Method 2: Set a tuning using a Scala scale file and keyboard mapping file===
@@ Line 94: / Line 95: @@
 '''Notes'''
-[This whole section needs extensive review with regard to what should be moved out to the [[User:Mousemambo/Document draft#Appendix|Appendix on this page]], or the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article, what belongs in the [[User:Mousemambo/Scala tuning system|Scala tuning system]] article, or perhaps is best rendered in duplicate for reading simplicity. I am removing as much as possible from the Instructions section, but to where? For example, the complexity of the relationship between the Scala scale file's base note, the tuning's tuning center, and the music's tonic (if it has one) makes this a very difficult topic for beginners but it's critical for JI so something needs to be said in this article. But this doesn't seem to be the right place to explain it in great detail -- the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article is a better choice.]
+[This whole section needs extensive review with regard to what should be moved out to the [[User:Mousemambo/Document draft#Appendix|Appendix on this page]], or the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article, what belongs in the [[User:Mousemambo/Scala tuning system|Scala tuning system]] article, or perhaps is best rendered in duplicate for reading simplicity. I am removing as much as possible from the Instructions section, but to where? For example, the complexity of the relationship between the Scala scale file's base note, the tuning's tuning center, and the music's tonic (if it has one) makes this a very difficult topic for beginners but it's critical for JI so something needs to be said in this article. But this doesn't seem to be the right place to explain it in great detail — the [[User:Mousemambo/Tuning methods#Tuning files|Tuning methods]] article is a better choice.]
 '''''More about Surge XT'''''