New Tuning Method: Difference between revisions

Line 1:

<h2>IMPORTED REVISION FROM WIKISPACES</h2>

This is an imported revision from Wikispaces. The revision metadata is included below for reference:

: This revision was by author [[User:~~TallKite~~|~~TallKite~~]] and made on <tt>~~2014~~-01-~~18 22~~:07:59 UTC</tt>.

: This revision was by author [[User:xenjacob|xenjacob]] and made on <tt>2016-06-09 00:11:31 UTC</tt>.

: The original revision id was <tt>~~483791856~~</tt>.

: The original revision id was <tt>585078583</tt>.

: The revision comment was: <tt></tt>

The revision contents are below, presented both in the original Wikispaces Wikitext format, and in HTML exactly as Wikispaces rendered it.

Line 53:

**__Implementation__:**

The new method uses keyswitches for the 5 highest keys, 123-127. If middle C is C4, these are notes D#9 to G9. These keyswitches are generated by software, not played by the musician. The velocity of the keyswitches is not actually a velocity, but 1 byte of tuning information. Keyswitch F#9's velocity is actually the input note, keyswitch F9's velocity is the output note, and keyswitches E9 and D#9's velocities are the pitch bend, in the exact same format as the 2 7-bit data bytes of the standard midi pitch bend message. This makes it easier for the synth developer or designer, because he has already written code that handles physical pitch bend wheel movement, and can just reuse it to handle tuning keyswitches. Because the keyswitch bend range is fixed at 50¢, the tuning resolution is 0.0061¢. Thus 00 00 = -50¢, 40 00 = 0¢, and 7F FF = +49.9939¢.

The new method uses keyswitches for the 5 highest keys, 123-127. If middle C is C4, these are notes D#9 to G9. These keyswitches are generated by software, not played by the musician. The velocity of the keyswitches is not actually a velocity, but 1 byte of tuning information. Keyswitch F#9's velocity is actually the input note, keyswitch F9's velocity is the output note, and keyswitches E9 and D#9's velocities are the pitch bend, in the exact same format as the 2 7-bit data bytes of the standard midi pitch bend message. This makes it easier for the synth developer or designer, because he has already written code that handles physical pitch bend wheel movement, and can just reuse it to handle tuning keyswitches. Because the keyswitch bend range is fixed at 50¢, the tuning resolution is 0.0061¢. Thus 00 00 = -50¢, 40 00 = 0¢, and 7F 7F = +49.9939¢.

Each keyswitch note-on needs to have a matching note-off, to avoid being misinterpreted and possibly blocked by the DAW or other environment. To this end, a zero-velocity note-on follows immediately. To bend note nn on channel x to note mm with bend of yyzz would take up to 4 note-on messages and 4 note-off messages. In hexadecimal the midi looks like this:

Line 199:

Implementation:

The new method uses keyswitches for the 5 highest keys, 123-127. If middle C is C4, these are notes D#9 to G9. These keyswitches are generated by software, not played by the musician. The velocity of the keyswitches is not actually a velocity, but 1 byte of tuning information. Keyswitch F#9's velocity is actually the input note, keyswitch F9's velocity is the output note, and keyswitches E9 and D#9's velocities are the pitch bend, in the exact same format as the 2 7-bit data bytes of the standard midi pitch bend message. This makes it easier for the synth developer or designer, because he has already written code that handles physical pitch bend wheel movement, and can just reuse it to handle tuning keyswitches. Because the keyswitch bend range is fixed at 50¢, the tuning resolution is 0.0061¢. Thus 00 00 = -50¢, 40 00 = 0¢, and 7F FF = +49.9939¢.

The new method uses keyswitches for the 5 highest keys, 123-127. If middle C is C4, these are notes D#9 to G9. These keyswitches are generated by software, not played by the musician. The velocity of the keyswitches is not actually a velocity, but 1 byte of tuning information. Keyswitch F#9's velocity is actually the input note, keyswitch F9's velocity is the output note, and keyswitches E9 and D#9's velocities are the pitch bend, in the exact same format as the 2 7-bit data bytes of the standard midi pitch bend message. This makes it easier for the synth developer or designer, because he has already written code that handles physical pitch bend wheel movement, and can just reuse it to handle tuning keyswitches. Because the keyswitch bend range is fixed at 50¢, the tuning resolution is 0.0061¢. Thus 00 00 = -50¢, 40 00 = 0¢, and 7F 7F = +49.9939¢.

Each keyswitch note-on needs to have a matching note-off, to avoid being misinterpreted and possibly blocked by the DAW or other environment. To this end, a zero-velocity note-on follows immediately. To bend note nn on channel x to note mm with bend of yyzz would take up to 4 note-on messages and 4 note-off messages. In hexadecimal the midi looks like this:

@@ Line 1: / Line 1: @@
 <h2>IMPORTED REVISION FROM WIKISPACES</h2>
 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>2014-01-18 22:07:59 UTC</tt>.<br>
+: This revision was by author [[User:xenjacob|xenjacob]] and made on <tt>2016-06-09 00:11:31 UTC</tt>.<br>
-: The original revision id was <tt>483791856</tt>.<br>
+: The original revision id was <tt>585078583</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>
@@ Line 53: / Line 53: @@
 **__Implementation__:**
-The new method uses keyswitches for the 5 highest keys, 123-127. If middle C is C4, these are notes D#9 to G9. These keyswitches are generated by software, not played by the musician. The velocity of the keyswitches is not actually a velocity, but 1 byte of tuning information. Keyswitch F#9's velocity is actually the input note, keyswitch F9's velocity is the output note, and keyswitches E9 and D#9's velocities are the pitch bend, in the exact same format as the 2 7-bit data bytes of the standard midi pitch bend message. This makes it easier for the synth developer or designer, because he has already written code that handles physical pitch bend wheel movement, and can just reuse it to handle tuning keyswitches. Because the keyswitch bend range is fixed at 50¢, the tuning resolution is 0.0061¢. Thus 00 00 = -50¢, 40 00 = 0¢, and 7F FF = +49.9939¢.
+The new method uses keyswitches for the 5 highest keys, 123-127. If middle C is C4, these are notes D#9 to G9. These keyswitches are generated by software, not played by the musician. The velocity of the keyswitches is not actually a velocity, but 1 byte of tuning information. Keyswitch F#9's velocity is actually the input note, keyswitch F9's velocity is the output note, and keyswitches E9 and D#9's velocities are the pitch bend, in the exact same format as the 2 7-bit data bytes of the standard midi pitch bend message. This makes it easier for the synth developer or designer, because he has already written code that handles physical pitch bend wheel movement, and can just reuse it to handle tuning keyswitches. Because the keyswitch bend range is fixed at 50¢, the tuning resolution is 0.0061¢. Thus 00 00 = -50¢, 40 00 = 0¢, and 7F 7F = +49.9939¢.
 Each keyswitch note-on needs to have a matching note-off, to avoid being misinterpreted and possibly blocked by the DAW or other environment. To this end, a zero-velocity note-on follows immediately. To bend note nn on channel x to note mm with bend of yyzz would take up to 4 note-on messages and 4 note-off messages. In hexadecimal the midi looks like this:
@@ Line 199: / Line 199: @@
 &lt;strong&gt;&lt;u&gt;Implementation&lt;/u&gt;:&lt;/strong&gt;&lt;br /&gt;
 &lt;br /&gt;
-The new method uses keyswitches for the 5 highest keys, 123-127. If middle C is C4, these are notes D#9 to G9. These keyswitches are generated by software, not played by the musician. The velocity of the keyswitches is not actually a velocity, but 1 byte of tuning information. Keyswitch F#9's velocity is actually the input note, keyswitch F9's velocity is the output note, and keyswitches E9 and D#9's velocities are the pitch bend, in the exact same format as the 2 7-bit data bytes of the standard midi pitch bend message. This makes it easier for the synth developer or designer, because he has already written code that handles physical pitch bend wheel movement, and can just reuse it to handle tuning keyswitches. Because the keyswitch bend range is fixed at 50¢, the tuning resolution is 0.0061¢. Thus 00 00 = -50¢, 40 00 = 0¢, and 7F FF = +49.9939¢.&lt;br /&gt;
+The new method uses keyswitches for the 5 highest keys, 123-127. If middle C is C4, these are notes D#9 to G9. These keyswitches are generated by software, not played by the musician. The velocity of the keyswitches is not actually a velocity, but 1 byte of tuning information. Keyswitch F#9's velocity is actually the input note, keyswitch F9's velocity is the output note, and keyswitches E9 and D#9's velocities are the pitch bend, in the exact same format as the 2 7-bit data bytes of the standard midi pitch bend message. This makes it easier for the synth developer or designer, because he has already written code that handles physical pitch bend wheel movement, and can just reuse it to handle tuning keyswitches. Because the keyswitch bend range is fixed at 50¢, the tuning resolution is 0.0061¢. Thus 00 00 = -50¢, 40 00 = 0¢, and 7F 7F = +49.9939¢.&lt;br /&gt;
 &lt;br /&gt;
 Each keyswitch note-on needs to have a matching note-off, to avoid being misinterpreted and possibly blocked by the DAW or other environment. To this end, a zero-velocity note-on follows immediately. To bend note nn on channel x to note mm with bend of yyzz would take up to 4 note-on messages and 4 note-off messages. In hexadecimal the midi looks like this:&lt;br /&gt;