Ge;<br><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Indeed there is no underlying functionality to interpret a MIDI clock at<br>
the current time.&nbsp;&nbsp;If we can work it cleanly into the timing framework it<br>would certainly be worth having.&nbsp;&nbsp;It is now on the TODO list.</blockquote><div><br>Yeah, the &quot;cleanly&quot; bit might be a bit of a issue here. Compensation for latency to the MIDI clock like Live uses might not be possible in Chuck. Still, even being able to extract the time between clock pulses would be valuable for paterned effects and so on.
<br>&nbsp;</div>Very few implementations get it right. Stricktly speaking the clock is just one byte and it's one that should be able to interupt other messages, then have those continue yet not all implementations do that.<br>
<div>&nbsp;<br></div>Oh, and I have another matter;<br><br>Considder this little fragement;<br><br>if (msg.data2==60) !patern[0] =&gt; patern[0]; <br>if (msg.data2==62) !patern[1] =&gt; patern[1];<br>if (msg.data2==64) !patern[2] =&gt; patern[2];
<br>
etc.<br><br>This refers to white key midi notes toggeling bits in a array called &quot;patern&quot; which holds ones and zeros which in turn represent my steps. (So I can do &quot;if(patern[step]) 0=&gt; buf.pos;&quot; which I personally found rather elegant)
<br><br>This works perfectly fine but I couldn't find active use of the &quot;!&quot; operator documented anywhere. Checks involving it are all around but nothing like this active usage (as far as I could see) while this is quite handy. I figured it out by simply trying but it might be nice to have it documented somewhere.
<br><br>Yours,<br>Kas.<br></div>