On Wed, Jun 23, 2004 at 03:28:30PM +0100, Martijn Sipkema wrote: > > > [...] > > > > > This re-packaging allows the host to track all MIDI messages equally > > > > > > > > instead of saying MIDI, say "external". The goal is not to ghetto-ize > > > > MIDI messgaes, but to make ANY external message become GMPI internally. > > > > OSC, HID, MIDI, etc. > > > > > > You only change the encoding. A plugin that wants to support both MIDI and > > > OSC will still have to support both these protocols in the new encoding. > > > I really > > > don't see what this gains... > > > > That wasnt my understanding of the proposal. Maybe I mesread it, but my > > reading is that they would just have to handle the one format. > > Either all MIDI commands are supported and work as they do in MIDI, or > they are not all supported or work differently. In the first case seperate > commands for OSC (or some other protocol) will have to be added. The > other option means losing MIDI compatibility. The strawman message format as a superset of MIDI, so MIDI->GMPI would be fine GMPI->MIDI might be fine. I dont see how we have any choice on that, MIDI does not cover the requirements. - Steve ---------------------------------------------------------------------- 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