Tuning RPNs - Revision history

Xenwolf: transformed into regular redirect with category added

2020-09-26T11:31:26Z

transformed into regular redirect with category added

← Older revision		Revision as of 11:31, 26 September 2020
Line 1:		Line 1:
	~~'''This page has been replaced with this one:~~ [[~~New_Tuning_Method\|~~New Tuning Method]]~~'''~~ [[Category:~~midi~~]]		#REDIRECT [[New Tuning Method]]

			[[Category:Midi]]

Wikispaces>FREEZE at 00:00, 17 July 2018

2018-07-17T00:00:00Z

← Older revision		Revision as of 00:00, 17 July 2018
Line 1:		Line 1:
	~~<h2>IMPORTED REVISION FROM WIKISPACES</h2>~~		'''This page has been replaced with this one: [[New_Tuning_Method\|New Tuning Method]]''' [[Category:midi]]
	~~This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>~~
	~~: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-12-16 00:20:12 UTC</tt>.<br>~~
	~~: The original revision id was <tt>477681302</tt>.<br>~~
	~~: The revision comment was: <tt></tt><br>~~
	~~The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>~~
	~~<h4>Original Wikitext content:</h4>~~
	<div style="width:100%; max-height:400pt; overflow:auto; background-color:#f8f9fa; border: 1px solid #eaecf0; padding:0em"><pre style="margin:0px;border:none;background:none;word-wrap:break-word;white-space: pre-wrap ! important" class="old-revision-html">This page has been replaced with this one: [[New Tuning Method]]</pre></div>
	~~<h4>Original HTML content~~:~~</h4>~~
	<div style="width:100%; max-height:400pt; overflow:auto; background-color:#f8f9fa; border: 1px solid #eaecf0; padding:0em"><pre style="margin:0px;border:none;background:none;word-wrap:break-word;width:200%;white-space: pre-wrap ! important" class="old-revision-html"><html><head><title>Tuning RPNs</title></head><body><strong>This page has been replaced with this one: <a class="wiki_link" href="/New%20Tuning%20Method">New Tuning Method</a></strong></body></html></pre></div>

Wikispaces>TallKite: Imported revision 477681302 - Original comment:

2013-12-16T00:20:12Z

**Imported revision 477681302 - Original comment: **

Show changes

Wikispaces>TallKite: Imported revision 458245122 - Original comment:

2013-10-09T12:30:06Z

**Imported revision 458245122 - Original comment: **

← Older revision		Revision as of 12:30, 9 October 2013
Line 1:		Line 1:
	<h2>IMPORTED REVISION FROM WIKISPACES</h2>		<h2>IMPORTED REVISION FROM WIKISPACES</h2>
	This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>		This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>
	: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09~~-22 16~~:57:53 UTC</tt>.<br>		: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-10-09 12:30:06 UTC</tt>.<br>
	: The original revision id was <tt>~~453184460~~</tt>.<br>		: The original revision id was <tt>458245122</tt>.<br>
	: The revision comment was: <tt></tt><br>		: The revision comment was: <tt></tt><br>
	The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>		The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>
	<h4>Original Wikitext content:</h4>		<h4>Original Wikitext content:</h4>
	<div style="width:100%; max-height:400pt; overflow:auto; background-color:#f8f9fa; border: 1px solid #eaecf0; padding:0em"><pre style="margin:0px;border:none;background:none;word-wrap:break-word;white-space: pre-wrap ! important" class="old-revision-html">An open letter to tuning software developers and synth developers:		<div style="width:100%; max-height:400pt; overflow:auto; background-color:#f8f9fa; border: 1px solid #eaecf0; padding:0em"><pre style="margin:0px;border:none;background:none;word-wrap:break-word;white-space: pre-wrap ! important" class="old-revision-html">This page has been replaced with this one: [[New Tuning Method]]


			An open letter to tuning software developers and synth developers:

	__Background__:		__Background__:
Line 134:		Line 137:
	Would it be possible to quickly implement RPN microtuning in Abelton with scripts?</pre></div>		Would it be possible to quickly implement RPN microtuning in Abelton with scripts?</pre></div>
	<h4>Original HTML content:</h4>		<h4>Original HTML content:</h4>
	<div style="width:100%; max-height:400pt; overflow:auto; background-color:#f8f9fa; border: 1px solid #eaecf0; padding:0em"><pre style="margin:0px;border:none;background:none;word-wrap:break-word;width:200%;white-space: pre-wrap ! important" class="old-revision-html"><html><head><title>Tuning RPNs</title></head><body><strong>An open letter to tuning software developers and synth developers:</strong><br />		<div style="width:100%; max-height:400pt; overflow:auto; background-color:#f8f9fa; border: 1px solid #eaecf0; padding:0em"><pre style="margin:0px;border:none;background:none;word-wrap:break-word;width:200%;white-space: pre-wrap ! important" class="old-revision-html"><html><head><title>Tuning RPNs</title></head><body><strong>This page has been replaced with this one: <a class="wiki_link" href="/New%20Tuning%20Method">New Tuning Method</a></strong><br />
			<br />
			<br />
			<strong>An open letter to tuning software developers and synth developers:</strong><br />
	<br />		<br />
	<strong><u>Background</u>:</strong><br />		<strong><u>Background</u>:</strong><br />

Wikispaces>TallKite: Imported revision 453184460 - Original comment:

2013-09-22T16:57:53Z

**Imported revision 453184460 - Original comment: **

Wikispaces>TallKite: Imported revision 453093570 - Original comment:

2013-09-22T08:24:26Z

**Imported revision 453093570 - Original comment: **

Wikispaces>TallKite: Imported revision 453092914 - Original comment:

2013-09-22T08:17:30Z

**Imported revision 453092914 - Original comment: **

← Older revision		Revision as of 08:17, 22 September 2013
Line 1:		Line 1:
	<h2>IMPORTED REVISION FROM WIKISPACES</h2>		<h2>IMPORTED REVISION FROM WIKISPACES</h2>
	This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>		This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>
	: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09-22 08:13:36 UTC</tt>.<br>		: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09-22 08:17:30 UTC</tt>.<br>
	: The original revision id was <tt>~~453092522~~</tt>.<br>		: The original revision id was <tt>453092914</tt>.<br>
	: The revision comment was: <tt></tt><br>		: The revision comment was: <tt></tt><br>
	The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>		The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>
Line 24:		Line 24:
	frequency = 440 * 2 ^ [ (outputNote - 69) / 12 + (pitchBend / 8192 - 1) / 6 ]		frequency = 440 * 2 ^ [ (outputNote - 69) / 12 + (pitchBend / 8192 - 1) / 6 ]

	The pitch bend range is "hard-wired" to 2 semitones, one sixth of an octave, hence the 6 at the end of the equation. If the physical pitch bend wheel is moved, that bend would be added onto the tuning bend. The physical pitch bend wheel is not hard-wired to 200¢ and is governed by the usual pitch bend range.		The pitch bend range is "hard-wired" to 2 semitones, one sixth of an octave, hence the 6 at the end of the equation. (//This may be changed from 2 semitones to 50¢ - Ed.//) If the physical pitch bend wheel is moved, that bend would be added onto the tuning bend. The physical pitch bend wheel is not hard-wired to 200¢ and is governed by the usual pitch bend range.

	Because microtonalists use array keyboards, there may be a full 128 keys in use. Any input key can be mapped to any output frequency. Because alternate tunings can have more than 12 notes per octave, more than one input note may be be mapped to the same output note. Therefore the pitch bend is associated with the input note, not the output note. Specifying an output note is optional. If none is specified, the output note is understood to be the same as the input note.		Because microtonalists use array keyboards, there may be a full 128 keys in use. Any input key can be mapped to any output frequency. Because alternate tunings can have more than 12 notes per octave, more than one input note may be be mapped to the same output note. Therefore the pitch bend is associated with the input note, not the output note. Specifying an output note is optional. If none is specified, the output note is understood to be the same as the input note.
Line 45:		Line 45:
	E9 note-on: 9c FC yy (coarse bend, optional)		E9 note-on: 9c FC yy (coarse bend, optional)
	D#9 note-on: 9c FB zz (fine bend, required)		D#9 note-on: 9c FB zz (fine bend, required)

			(//There may be an additional "ultra-fine bend" message added - Ed.//)

	These messages are always sent in this order. If the F#9 message is omitted, additional output note and bend messages continue to affect the current input note, overwriting previous output note and bend messages. The output note message is optional and would generally be omitted for 12-notes-per-octave tunings. The coarse bend could be omitted for slight pitch bends that don't change the MSB of the pitch bend. The required fine bend message functions as an "end of tuning message" marker and the synth waits until receiving this message to actually apply the new tuning. In general, the retuning software will limit the pitch bends to +/- 50¢. The midi stream for pitch glides will be reduced to mostly fine bends, with coarse bends whenever the MSB boundary is crossed, and output note messages whenever the note boundary is crossed.		These messages are always sent in this order. If the F#9 message is omitted, additional output note and bend messages continue to affect the current input note, overwriting previous output note and bend messages. The output note message is optional and would generally be omitted for 12-notes-per-octave tunings. The coarse bend could be omitted for slight pitch bends that don't change the MSB of the pitch bend. The required fine bend message functions as an "end of tuning message" marker and the synth waits until receiving this message to actually apply the new tuning. In general, the retuning software will limit the pitch bends to +/- 50¢. The midi stream for pitch glides will be reduced to mostly fine bends, with coarse bends whenever the MSB boundary is crossed, and output note messages whenever the note boundary is crossed.
Line 150:		Line 152:
	frequency = 440 * 2 ^ [ (outputNote - 69) / 12 + (pitchBend / 8192 - 1) / 6 ]<br />		frequency = 440 * 2 ^ [ (outputNote - 69) / 12 + (pitchBend / 8192 - 1) / 6 ]<br />
	<br />		<br />
	The pitch bend range is &quot;hard-wired&quot; to 2 semitones, one sixth of an octave, hence the 6 at the end of the equation. If the physical pitch bend wheel is moved, that bend would be added onto the tuning bend. The physical pitch bend wheel is not hard-wired to 200¢ and is governed by the usual pitch bend range.<br />		The pitch bend range is &quot;hard-wired&quot; to 2 semitones, one sixth of an octave, hence the 6 at the end of the equation. (<em>This may be changed from 2 semitones to 50¢ - Ed.</em>) If the physical pitch bend wheel is moved, that bend would be added onto the tuning bend. The physical pitch bend wheel is not hard-wired to 200¢ and is governed by the usual pitch bend range.<br />
	<br />		<br />
	Because microtonalists use array keyboards, there may be a full 128 keys in use. Any input key can be mapped to any output frequency. Because alternate tunings can have more than 12 notes per octave, more than one input note may be be mapped to the same output note. Therefore the pitch bend is associated with the input note, not the output note. Specifying an output note is optional. If none is specified, the output note is understood to be the same as the input note.<br />		Because microtonalists use array keyboards, there may be a full 128 keys in use. Any input key can be mapped to any output frequency. Because alternate tunings can have more than 12 notes per octave, more than one input note may be be mapped to the same output note. Therefore the pitch bend is associated with the input note, not the output note. Specifying an output note is optional. If none is specified, the output note is understood to be the same as the input note.<br />
Line 171:		Line 173:
	E9 note-on: 9c FC yy (coarse bend, optional)<br />		E9 note-on: 9c FC yy (coarse bend, optional)<br />
	D#9 note-on: 9c FB zz (fine bend, required)<br />		D#9 note-on: 9c FB zz (fine bend, required)<br />
			<br />
			(<em>There may be an additional &quot;ultra-fine bend&quot; message added - Ed.</em>)<br />
	<br />		<br />
	These messages are always sent in this order. If the F#9 message is omitted, additional output note and bend messages continue to affect the current input note, overwriting previous output note and bend messages. The output note message is optional and would generally be omitted for 12-notes-per-octave tunings. The coarse bend could be omitted for slight pitch bends that don't change the MSB of the pitch bend. The required fine bend message functions as an &quot;end of tuning message&quot; marker and the synth waits until receiving this message to actually apply the new tuning. In general, the retuning software will limit the pitch bends to +/- 50¢. The midi stream for pitch glides will be reduced to mostly fine bends, with coarse bends whenever the MSB boundary is crossed, and output note messages whenever the note boundary is crossed.<br />		These messages are always sent in this order. If the F#9 message is omitted, additional output note and bend messages continue to affect the current input note, overwriting previous output note and bend messages. The output note message is optional and would generally be omitted for 12-notes-per-octave tunings. The coarse bend could be omitted for slight pitch bends that don't change the MSB of the pitch bend. The required fine bend message functions as an &quot;end of tuning message&quot; marker and the synth waits until receiving this message to actually apply the new tuning. In general, the retuning software will limit the pitch bends to +/- 50¢. The midi stream for pitch glides will be reduced to mostly fine bends, with coarse bends whenever the MSB boundary is crossed, and output note messages whenever the note boundary is crossed.<br />

Wikispaces>TallKite: Imported revision 453092522 - Original comment:

2013-09-22T08:13:36Z

**Imported revision 453092522 - Original comment: **

Show changes

Wikispaces>TallKite: Imported revision 452875632 - Original comment:

2013-09-20T22:27:21Z

**Imported revision 452875632 - Original comment: **

Show changes

Wikispaces>TallKite: Imported revision 452369772 - Original comment:

2013-09-19T04:59:40Z

**Imported revision 452369772 - Original comment: **

← Older revision		Revision as of 04:59, 19 September 2013
Line 1:		Line 1:
	<h2>IMPORTED REVISION FROM WIKISPACES</h2>		<h2>IMPORTED REVISION FROM WIKISPACES</h2>
	This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>		This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>
	: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09-19 04:38:49 UTC</tt>.<br>		: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09-19 04:59:40 UTC</tt>.<br>
	: The original revision id was <tt>~~452367366~~</tt>.<br>		: The original revision id was <tt>452369772</tt>.<br>
	: The revision comment was: <tt></tt><br>		: The revision comment was: <tt></tt><br>
	The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>		The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>
Line 31:		Line 31:

	Multi-timbral synths should be able to handle as many as 16 of these keyboards at once, one per channel. (To be decided: Tuning messages must only affect their own channel, so that a pitch glide on one keyboard won't affect the tuning of another keyboard. OR Tuning messages must affect all channels at once, to reduce the volume of the midi traffic. If one keyboard is sending pitch glides, the synth developer can assume that that musician is using a separate instance of the synth.)		Multi-timbral synths should be able to handle as many as 16 of these keyboards at once, one per channel. (To be decided: Tuning messages must only affect their own channel, so that a pitch glide on one keyboard won't affect the tuning of another keyboard. OR Tuning messages must affect all channels at once, to reduce the volume of the midi traffic. If one keyboard is sending pitch glides, the synth developer can assume that that musician is using a separate instance of the synth.)

			__Implementation__:

	The new method uses RPNs (Registered Parameter Numbers). The technical details: There are about 16,000 possible RPN parameters, and only about a dozen are in use. We can use a block of 128 RPNs, one for each input note number, for retuning. Data MSB and LSB messages for these RPNs contain the cents to retune by, in the exact same format as the standard midi pitch bend message. The retuning is immediate (real-time), just like the standard pitch bend. This makes it easier for the synth developer or designer, because he has already written code that deals with physical pitch bend wheel movement, and can just reuse it to deal with tuning RPNs. We use another block of 128 RPNs to define the output note. The RPN LSB is again the input note number. The data MSB is the output note number, and the data LSB is not used. If this RPN MSB is 100 = 64 hexadecimal, and the first RPN MSB is 101 = 65 hexadecimal, then to bend note nn on channel c to note mm with bend of yyzz would take up to 6 midi CC (Controller Change) messages. In hexadecimal the midi looks like this:		The new method uses RPNs (Registered Parameter Numbers). The technical details: There are about 16,000 possible RPN parameters, and only about a dozen are in use. We can use a block of 128 RPNs, one for each input note number, for retuning. Data MSB and LSB messages for these RPNs contain the cents to retune by, in the exact same format as the standard midi pitch bend message. The retuning is immediate (real-time), just like the standard pitch bend. This makes it easier for the synth developer or designer, because he has already written code that deals with physical pitch bend wheel movement, and can just reuse it to deal with tuning RPNs. We use another block of 128 RPNs to define the output note. The RPN LSB is again the input note number. The data MSB is the output note number, and the data LSB is not used. If this RPN MSB is 100 = 64 hexadecimal, and the first RPN MSB is 101 = 65 hexadecimal, then to bend note nn on channel c to note mm with bend of yyzz would take up to 6 midi CC (Controller Change) messages. In hexadecimal the midi looks like this:
Line 109:		Line 111:
	<br />		<br />
	Multi-timbral synths should be able to handle as many as 16 of these keyboards at once, one per channel. (To be decided: Tuning messages must only affect their own channel, so that a pitch glide on one keyboard won't affect the tuning of another keyboard. <strong>OR</strong> Tuning messages must affect all channels at once, to reduce the volume of the midi traffic. If one keyboard is sending pitch glides, the synth developer can assume that that musician is using a separate instance of the synth.)<br />		Multi-timbral synths should be able to handle as many as 16 of these keyboards at once, one per channel. (To be decided: Tuning messages must only affect their own channel, so that a pitch glide on one keyboard won't affect the tuning of another keyboard. <strong>OR</strong> Tuning messages must affect all channels at once, to reduce the volume of the midi traffic. If one keyboard is sending pitch glides, the synth developer can assume that that musician is using a separate instance of the synth.)<br />
			<br />
			<strong><u>Implementation</u>:</strong><br />
	<br />		<br />
	The new method uses RPNs (Registered Parameter Numbers). The technical details: There are about 16,000 possible RPN parameters, and only about a dozen are in use. We can use a block of 128 RPNs, one for each input note number, for retuning. Data MSB and LSB messages for these RPNs contain the cents to retune by, in the exact same format as the standard midi pitch bend message. The retuning is immediate (real-time), just like the standard pitch bend. This makes it easier for the synth developer or designer, because he has already written code that deals with physical pitch bend wheel movement, and can just reuse it to deal with tuning RPNs. We use another block of 128 RPNs to define the output note. The RPN LSB is again the input note number. The data MSB is the output note number, and the data LSB is not used. If this RPN MSB is 100 = 64 hexadecimal, and the first RPN MSB is 101 = 65 hexadecimal, then to bend note nn on channel c to note mm with bend of yyzz would take up to 6 midi CC (Controller Change) messages. In hexadecimal the midi looks like this:<br />		The new method uses RPNs (Registered Parameter Numbers). The technical details: There are about 16,000 possible RPN parameters, and only about a dozen are in use. We can use a block of 128 RPNs, one for each input note number, for retuning. Data MSB and LSB messages for these RPNs contain the cents to retune by, in the exact same format as the standard midi pitch bend message. The retuning is immediate (real-time), just like the standard pitch bend. This makes it easier for the synth developer or designer, because he has already written code that deals with physical pitch bend wheel movement, and can just reuse it to deal with tuning RPNs. We use another block of 128 RPNs to define the output note. The RPN LSB is again the input note number. The data MSB is the output note number, and the data LSB is not used. If this RPN MSB is 100 = 64 hexadecimal, and the first RPN MSB is 101 = 65 hexadecimal, then to bend note nn on channel c to note mm with bend of yyzz would take up to 6 midi CC (Controller Change) messages. In hexadecimal the midi looks like this:<br />

← Older revision		Revision as of 16:57, 22 September 2013
Line 1:		Line 1:
	<h2>IMPORTED REVISION FROM WIKISPACES</h2>		<h2>IMPORTED REVISION FROM WIKISPACES</h2>
	This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>		This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>
	: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09-22 08:24:26 UTC</tt>.<br>		: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09-22 16:57:53 UTC</tt>.<br>
	: The original revision id was <tt>~~453093570~~</tt>.<br>		: The original revision id was <tt>453184460</tt>.<br>
	: The revision comment was: <tt></tt><br>		: The revision comment was: <tt></tt><br>
	The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>		The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>
Line 12:		Line 12:
	As we're all painfully aware, the midi spec isn't very microtonal-friendly. The powers that be decided that pitch bend would affect the whole channel, not individual notes, so retuning most synths requires dividing the midi stream among multiple channels. That increases setup time for the user and reduces polyphony, and generally just makes things complicated and difficult. The powers that be threw us a crumb in the form of MTS sysexes, [[@http://www.midi.org/techspecs/midituning.php]], which haven't been widely adopted.		As we're all painfully aware, the midi spec isn't very microtonal-friendly. The powers that be decided that pitch bend would affect the whole channel, not individual notes, so retuning most synths requires dividing the midi stream among multiple channels. That increases setup time for the user and reduces polyphony, and generally just makes things complicated and difficult. The powers that be threw us a crumb in the form of MTS sysexes, [[@http://www.midi.org/techspecs/midituning.php]], which haven't been widely adopted.

	The problem with MTS lies in convincing the developers of VSTi's and other softsynths, as well as the designers of hardware sound modules and keyboards, who generally have no personal interest in microtonalism, to invest their time and energy in understanding these sysexes and implementing them. And they're hard to understand. They ~~use checksums, they~~ use tuning banks~~, they use channel bitmaps~~, they use a different format for pitch bends than the usual midi pitch bend command, ~~etc~~. Plus there are problems with sysex in general. One, Abelton Live and perhaps FL Studio actually filter out sysexes and keep them from reaching any VSTi's they host. Two, a synth developer or designer may have to write additional code to read sysexes, as they are a variable-length message. So sysexes are problematic and there's a real disincentive to work with them.		The problem with MTS lies in convincing the developers of VSTi's and other softsynths, as well as the designers of hardware sound modules and keyboards, who generally have no personal interest in microtonalism, to invest their time and energy in understanding these sysexes and implementing them. And they're hard to understand. They use tuning banks and programs, they use a different format for pitch bends than the usual midi pitch bend command, and the application of different tunings to different channels is not obvious. Plus there are problems with sysex in general. One, Abelton Live and perhaps FL Studio actually filter out sysexes and keep them from reaching any VSTi's they host. Two, a synth developer or designer may have to write additional code to read sysexes, as they are a variable-length message. So sysexes are problematic and there's a real disincentive to work with them.

	So it would be great if there was a simpler, non-sysex way of tuning individual notes. A few of us have cooked up a daring plan. The powers that be will probably never give us what we want, so we'll just __take__ it! We can commandeer an obscure and underused part of the midi spec and use it for our own microtonal purposes. We can simply create a new unofficial microtuning method. By "we" I mean the authors of midi tuning software, aka "retuners". If we all include this new method in alt-tuner, Fractal Tune Smithy, Custom Scale Editor, Scala, LMSO, etc. we will have a more enticing sales pitch for synth developers and designers: Add this simple easy method of retuning and you will sell more synths to microtonalists.		So it would be great if there was a simpler, non-sysex way of tuning individual notes. A few of us have cooked up a daring plan. The powers that be will probably never give us what we want, so we'll just __take__ it! We can commandeer an obscure and underused part of the midi spec and use it for our own microtonal purposes. We can simply create a new unofficial microtuning method. By "we" I mean the authors of midi tuning software, aka "retuners". If we all include this new method in alt-tuner, Fractal Tune Smithy, Custom Scale Editor, Scala, LMSO, etc. we will have a more enticing sales pitch for synth developers and designers: Add this simple easy method of retuning and you will sell more synths to microtonalists.
Line 140:		Line 140:
	As we're all painfully aware, the midi spec isn't very microtonal-friendly. The powers that be decided that pitch bend would affect the whole channel, not individual notes, so retuning most synths requires dividing the midi stream among multiple channels. That increases setup time for the user and reduces polyphony, and generally just makes things complicated and difficult. The powers that be threw us a crumb in the form of MTS sysexes, <a class="wiki_link_ext" href="http://www.midi.org/techspecs/midituning.php" rel="nofollow" target="_blank">http://www.midi.org/techspecs/midituning.php</a>, which haven't been widely adopted.<br />		As we're all painfully aware, the midi spec isn't very microtonal-friendly. The powers that be decided that pitch bend would affect the whole channel, not individual notes, so retuning most synths requires dividing the midi stream among multiple channels. That increases setup time for the user and reduces polyphony, and generally just makes things complicated and difficult. The powers that be threw us a crumb in the form of MTS sysexes, <a class="wiki_link_ext" href="http://www.midi.org/techspecs/midituning.php" rel="nofollow" target="_blank">http://www.midi.org/techspecs/midituning.php</a>, which haven't been widely adopted.<br />
	<br />		<br />
	The problem with MTS lies in convincing the developers of VSTi's and other softsynths, as well as the designers of hardware sound modules and keyboards, who generally have no personal interest in microtonalism, to invest their time and energy in understanding these sysexes and implementing them. And they're hard to understand. They ~~use checksums, they~~ use tuning banks~~, they use channel bitmaps~~, they use a different format for pitch bends than the usual midi pitch bend command, ~~etc~~. Plus there are problems with sysex in general. One, Abelton Live and perhaps FL Studio actually filter out sysexes and keep them from reaching any VSTi's they host. Two, a synth developer or designer may have to write additional code to read sysexes, as they are a variable-length message. So sysexes are problematic and there's a real disincentive to work with them.<br />		The problem with MTS lies in convincing the developers of VSTi's and other softsynths, as well as the designers of hardware sound modules and keyboards, who generally have no personal interest in microtonalism, to invest their time and energy in understanding these sysexes and implementing them. And they're hard to understand. They use tuning banks and programs, they use a different format for pitch bends than the usual midi pitch bend command, and the application of different tunings to different channels is not obvious. Plus there are problems with sysex in general. One, Abelton Live and perhaps FL Studio actually filter out sysexes and keep them from reaching any VSTi's they host. Two, a synth developer or designer may have to write additional code to read sysexes, as they are a variable-length message. So sysexes are problematic and there's a real disincentive to work with them.<br />
	<br />		<br />
	So it would be great if there was a simpler, non-sysex way of tuning individual notes. A few of us have cooked up a daring plan. The powers that be will probably never give us what we want, so we'll just <u>take</u> it! We can commandeer an obscure and underused part of the midi spec and use it for our own microtonal purposes. We can simply create a new unofficial microtuning method. By &quot;we&quot; I mean the authors of midi tuning software, aka &quot;retuners&quot;. If we all include this new method in alt-tuner, Fractal Tune Smithy, Custom Scale Editor, Scala, LMSO, etc. we will have a more enticing sales pitch for synth developers and designers: Add this simple easy method of retuning and you will sell more synths to microtonalists.<br />		So it would be great if there was a simpler, non-sysex way of tuning individual notes. A few of us have cooked up a daring plan. The powers that be will probably never give us what we want, so we'll just <u>take</u> it! We can commandeer an obscure and underused part of the midi spec and use it for our own microtonal purposes. We can simply create a new unofficial microtuning method. By &quot;we&quot; I mean the authors of midi tuning software, aka &quot;retuners&quot;. If we all include this new method in alt-tuner, Fractal Tune Smithy, Custom Scale Editor, Scala, LMSO, etc. we will have a more enticing sales pitch for synth developers and designers: Add this simple easy method of retuning and you will sell more synths to microtonalists.<br />

← Older revision		Revision as of 08:24, 22 September 2013
Line 1:		Line 1:
	<h2>IMPORTED REVISION FROM WIKISPACES</h2>		<h2>IMPORTED REVISION FROM WIKISPACES</h2>
	This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>		This is an imported revision from Wikispaces. The revision metadata is included below for reference:<br>
	: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09-22 08:17:30 UTC</tt>.<br>		: This revision was by author [[User:TallKite\|TallKite]] and made on <tt>2013-09-22 08:24:26 UTC</tt>.<br>
	: The original revision id was <tt>~~453092914~~</tt>.<br>		: The original revision id was <tt>453093570</tt>.<br>
	: The revision comment was: <tt></tt><br>		: The revision comment was: <tt></tt><br>
	The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>		The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.<br>
Line 24:		Line 24:
	frequency = 440 * 2 ^ [ (outputNote - 69) / 12 + (pitchBend / 8192 - 1) / 6 ]		frequency = 440 * 2 ^ [ (outputNote - 69) / 12 + (pitchBend / 8192 - 1) / 6 ]

	The pitch bend range is "hard-wired" to 2 semitones, one sixth of an octave, hence the 6 at the end of the equation. (//This may be changed from 2 semitones to 50¢ - Ed.//) If the physical pitch bend wheel is moved, that bend would be added onto the tuning bend. The physical pitch bend wheel is not hard-wired to ~~200¢~~ and is governed by the usual pitch bend range.		The pitch bend range is "hard-wired" to 2 semitones, one sixth of an octave, hence the 6 at the end of the equation. (//This may be changed from 2 semitones to 50¢ - Ed.//) If the physical pitch bend wheel is moved, that bend would be added onto the tuning bend. The physical pitch bend wheel is not hard-wired to 2 semitones and is governed by the usual pitch bend range.

	Because microtonalists use array keyboards, there may be a full 128 keys in use. Any input key can be mapped to any output frequency. Because alternate tunings can have more than 12 notes per octave, more than one input note may be be mapped to the same output note. Therefore the pitch bend is associated with the input note, not the output note. Specifying an output note is optional. If none is specified, the output note is understood to be the same as the input note.		Because microtonalists use array keyboards, there may be a full 128 keys in use. Any input key can be mapped to any output frequency. Because alternate tunings can have more than 12 notes per octave, more than one input note may be be mapped to the same output note. Therefore the pitch bend is associated with the input note, not the output note. Specifying an output note is optional. If none is specified, the output note is understood to be the same as the input note.
Line 152:		Line 152:
	frequency = 440 * 2 ^ [ (outputNote - 69) / 12 + (pitchBend / 8192 - 1) / 6 ]<br />		frequency = 440 * 2 ^ [ (outputNote - 69) / 12 + (pitchBend / 8192 - 1) / 6 ]<br />
	<br />		<br />
	The pitch bend range is &quot;hard-wired&quot; to 2 semitones, one sixth of an octave, hence the 6 at the end of the equation. (<em>This may be changed from 2 semitones to 50¢ - Ed.</em>) If the physical pitch bend wheel is moved, that bend would be added onto the tuning bend. The physical pitch bend wheel is not hard-wired to ~~200¢~~ and is governed by the usual pitch bend range.<br />		The pitch bend range is &quot;hard-wired&quot; to 2 semitones, one sixth of an octave, hence the 6 at the end of the equation. (<em>This may be changed from 2 semitones to 50¢ - Ed.</em>) If the physical pitch bend wheel is moved, that bend would be added onto the tuning bend. The physical pitch bend wheel is not hard-wired to 2 semitones and is governed by the usual pitch bend range.<br />
	<br />		<br />
	Because microtonalists use array keyboards, there may be a full 128 keys in use. Any input key can be mapped to any output frequency. Because alternate tunings can have more than 12 notes per octave, more than one input note may be be mapped to the same output note. Therefore the pitch bend is associated with the input note, not the output note. Specifying an output note is optional. If none is specified, the output note is understood to be the same as the input note.<br />		Because microtonalists use array keyboards, there may be a full 128 keys in use. Any input key can be mapped to any output frequency. Because alternate tunings can have more than 12 notes per octave, more than one input note may be be mapped to the same output note. Therefore the pitch bend is associated with the input note, not the output note. Specifying an output note is optional. If none is specified, the output note is understood to be the same as the input note.<br />

Tuning RPNs - Revision history

Xenwolf: transformed into regular redirect with category added

Wikispaces>FREEZE at 00:00, 17 July 2018

Wikispaces>TallKite: **Imported revision 477681302 - Original comment: **

Wikispaces>TallKite: **Imported revision 458245122 - Original comment: **

Wikispaces>TallKite: **Imported revision 453184460 - Original comment: **

Wikispaces>TallKite: **Imported revision 453093570 - Original comment: **

Wikispaces>TallKite: **Imported revision 453092914 - Original comment: **

Wikispaces>TallKite: **Imported revision 453092522 - Original comment: **

Wikispaces>TallKite: **Imported revision 452875632 - Original comment: **

Wikispaces>TallKite: **Imported revision 452369772 - Original comment: **

Wikispaces>TallKite: Imported revision 477681302 - Original comment:

Wikispaces>TallKite: Imported revision 458245122 - Original comment:

Wikispaces>TallKite: Imported revision 453184460 - Original comment:

Wikispaces>TallKite: Imported revision 453093570 - Original comment:

Wikispaces>TallKite: Imported revision 453092914 - Original comment:

Wikispaces>TallKite: Imported revision 453092522 - Original comment:

Wikispaces>TallKite: Imported revision 452875632 - Original comment:

Wikispaces>TallKite: Imported revision 452369772 - Original comment: