Tuning per channel: Difference between revisions

Fredg999 category edits (talk | contribs)
m Removing from Category:Resources using Cat-a-lot
 
(2 intermediate revisions by 2 users not shown)
Line 4: Line 4:


== Octave per channel ==
== Octave per channel ==
Octave per channel is a recommendable form of this software tuning scheme, where each subsequent channel increments the pitches by an [[octave]]. Each channel, in turn, should cover at least the entirety of an octave. For [[edo]]s, that implies up to 128edo with a range of 16 octaves. One probably does not need that range but even finer edos. The solution is to make each channel cover half an octave instead, with a range of 8 octaves. One way to do it is to make a channel cover every other edostep, and make another channel increment its pitches by a single edostep; repeat that pattern for each octave. How the channels are arranged is up to the user. For example, one may make channels 1–8 differ by octaves and channels 9–16 increment them by an edostep, or may make odd channels differ by octaves and even channels increment them by an edostep. A maximum of 256edo can be used, but it is particularly beneficial to hemicomma-size edos, where a common comma (such as the syntonic comma or the septimal comma) is tuned to two edosteps.  
Octave per channel is one possible form of this software tuning scheme, where each subsequent channel increments the pitches by an [[octave]]. Each channel, in turn, should cover at least the entirety of an octave. For [[edo]]s, that implies up to 128edo with a pitch range of 16 octaves, if the channels are not used for other purposes.  
 
One probably does not need that pitch range, but one might want even finer edos. The solution is to make each channel cover half an octave instead, with a pitch range of 8 octaves. One way to do it is to make a channel cover every other edostep, and make another channel increment its pitches by a single edostep; repeat that pattern for each octave. How the channels are arranged is up to the user. For example, one may make channels 1–8 differ by octaves and channels 9–16 increment them by an edostep, or may make odd channels differ by octaves and even channels increment them by an edostep. A maximum of 256edo can be used, but it is particularly suitable for hemicomma-size edos, where a common comma (such as the syntonic comma or the septimal comma) is tuned to two edosteps.
 
The disadvantage of this form is that it messes up the key switches and key modulations of some samples and/or synthesisers.
 
== Edostep per channel ==
Edostep per channel is another option. To do it, each octave should be tuned to a dodecatonic scale, typically the [[chromatic]] scale. Each subsequent channel increments or decrements the pitches by an edostep.
 
Edos available in this form depends on its [[sharpness]]. Up to sharp-16 (e.g. [[171edo]]) can be used, if the channels are not used for other purposes.
 
This form preserves the rough positions of all the pitches, thus better keeps the functionality of key switches and key modulations. The available edo range is smaller than the above method since the full 10+½-octave pitch range is always covered as in standard [[12edo]] tuning.  


== Software support ==
== Software support ==
As of January 2022, not many plugins support this tuning scheme. For one, ''Surge'' notably supports it by enabling ''Use MIDI channel for octave shift''<ref>See the [https://surge-synthesizer.github.io/manual-xt/#microtuning Manual]. </ref>. Otherwise, it is possible to achieve it by setting up the circuit in the [[Wikipedia: Digital audio workstation|DAW]] without support of the plugin itself. The figure below shows an example of using the ''Patcher'' plugin in ''FL Studio''. It is, essentially, multiple instances of the same plugin, so it unfortunately takes up a huge amount of memory.  
As of January 2022, not many plugins support this tuning scheme. For one, ''Surge'' notably supports octave per channel by enabling ''Use MIDI channel for octave shift''<ref>See the [https://surge-synthesizer.github.io/manual-xt/#microtuning Manual]. </ref>. Otherwise, it is possible to achieve it by setting up the circuit in the [[Wikipedia: Digital audio workstation|DAW]] without support of the plugin itself. The figure below shows an example of using the ''Patcher'' plugin in ''FL Studio''. It is, essentially, multiple instances of the same plugin, so it unfortunately takes up a huge amount of memory.  


[[File:Tuning_per_Channel_with_Patcher_in_FL_Studio.png|thumb|Tuning per channel with ''Patcher'' in ''FL Studio'']]
[[File:Tuning_per_Channel_with_Patcher_in_FL_Studio.png|thumb|Tuning per channel with ''Patcher'' in ''FL Studio'']]
== Notes ==


[[Category:Software]]
[[Category:Software]]
[[Category:Practical help]]