> > (I'm strongly opposed to using wrapped MIDI messages for several=20 > > reasons. Ask if you want the full list. ;-) > > What exactly do you mean with wrapped MIDI messages? passing > struct { unsigned char[3] }? Another paradigm for representation that is not based directly on the obtuse, bit-stingy data that flows between MIDI cables. ;) In other words, let it be the host's (or maybe even internally part of the API's) responsibility to parse MIDI events, if they are supported, and convert them into a more intelligible format for the plugins. This (a) makes things easier for plugs and makes it so that there isn't as much redundant MIDI parsing code written and (b) allows the interfaces musical representation system to exceed the limitations of MIDI, while still being able to work with MIDI data. Marc ---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission. Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe