Hans;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The methods are similar, but the cause different: Scala needs a lot of MIDI channels for the microtonality (and by default uses all but one). So when playing on the layout I gave, one uses several different channels (or so is my impression).<div>
<div></div><div class="h5"><br>
</div></div></blockquote><div><br>Ah, I get it. In this case though we are dealing with input from the computer keyboard which we send internally to a set of voices in ChucK so we aren&#39;t limited by MIDI&#39;s rather out-dated concepts.<br>
<br>What we do need is some way to translate key numbers to pitches. I&#39;d do that with a simple array of floats mapping key-numbers to pitches. I&#39;d likely deal with pitchbend using some sort of scaling on those values, if I needed pitchbend, that could then get rid of any issues arising from non-equal spacing between notes.<br>
<br>To clarify; what is interesting about the polyphonic examples in the MIDI dir is how they deal with polyphony, not the MIDI as such.<br></div></div><br>From your other mail;<br><br>&gt; It strikes me that Chuck may not be good for mixing key numbers with
the translated &quot;AsCII&quot; numbers. Ir seems one has to make choice of what
to use. When mixing, one may want to pick up the event first and
looking at both the key and the (eventual) Unicode number.<br><br>Well, both methods can be used in a single set of keyboard parsing rules though that would mean that we&#39;d need to make sure we0re not mixing up all the numbers that will be flying around. We might, for example, look at the key number only when there is no character associated with the key that was pressed, for example. Many other strategies are possible.<br>
<br>ChucK may be build on decades of knowledge about sound and computation but sadly we are also stuck with decades of legacy and semi-standards that occasionally make our life more annoying than it would ideally be. Personally I hate writing tens if not hundreds of lines parsing the keyboard because it&#39;s so boring and there are so many nearly random numbers yet it all needs to be exactly right. I&#39;m terribly sorry but I don&#39;t think there is anything I can do for you there aside from showing understanding.<br>
<br>Yours,<br>Kas.<br>