Hi Jay,<div><br></div><div>While the MIDI format doesn't care about matching ONs and OFFs, there's a good chance that the player tidies up (by sending an "all notes off" message to the hardware) once it's done playing a file. So this could end up working in some platforms, but not in others...</div> <div><br></div><div>I guess we won't know until we try.</div><div><br></div><div>Cheers,</div><div>Alex</div><div><br></div><div><div class="gmail_quote">On Thu, Apr 22, 2010 at 6:16 PM, Jay Hardesty <span dir="ltr"><<a href="mailto:jay.hardesty@gmail.com">jay.hardesty@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">>Second byte contains pitch and velocity<br> </div>CORRECTION: meant second and third bytes contain pitch and velocity<br> <div><div></div><div class="h5"><br> <br> >The real question is : Do you know if midi players allow a note to<br> >be started in one file and ended in another? This would allow<br> >key-down and key-up events to come in real time from the keyboard. I<br> >would make this work if the answer is yes.<br> ><br> >Thanks<br> > - Dan<br> <br> <br> As far as I know a MIDI player does not care where (or from which<br> file) a MIDI ON, or subsequent MIDI OFF message comes from.<br> Each is just a pair of bytes arriving from wherever.<br> <br> (That is, the first byte MIDI ON event is 144 for channel 1, 145 for<br> channel 2. etc. up to 159 for channel 16. Second byte contains pitch<br> and velocity. MIDI OFF events have first byte set to 128 for channel 1<br> up to 143 for channel 16 etc)<br> _______________________________________________<br> lively-kernel mailing list<br> <a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br> <a href="http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel" target="_blank">http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel</a><br> </div></div></blockquote></div><br></div>