<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [CM] Grace MIDI import / multiple message types</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>>> i think maybe what ill should do is allow specs like<BR>
>> ((time key) (time clt1 ctl2) ...)<BR>
<BR>
Yes -- I think that would work. The trick seems to be returning a list that allows one to tell the different message types apart. So, in this example, we might get something like (?):<BR>
<BR>
(<BR>
((0.0 60) ()) ;; a note at time 0<BR>
((1.2 62) ()) ;; a note at time 1.2<BR>
(() (1.5 1 64)) ;; controller 1, value 64, at time 1.5<BR>
((1.8 64) (1.8 1 68)) ;; note at time 1.8, controller at time 1.8 <BR>
;; (or one could have two distinct entries for each event)<BR>
)<BR>
<BR>
This format could also be helpful because one could order the spec based on the time-priority logic one needs. That is, if I have events simultaneous in time but logic-wise need to process (say) controller values 1st, I would just place the controller first in the spec.<BR>
<BR>
It is interesting that the Grace MIDI file import can import the meta messages. Does that mean there is an undocumented keyword already that allows one to import meta messages via midifile-import? ('meta' doesn't do it ;)<BR>
<BR>
Thanks,<BR>
-=Bret</FONT>
</P>
</BODY>
</HTML>