I think the solution point here is a non-MIDI interface between GMPI and plugins, and an optional MIDI aspect of the host API library, to translate from any MIDI channel or system message in the host to GMPI for the plugin. In other words, I think we agree that the GMPI libraries are not only for use by plugins, but also by hosts. I agree that having more than one wire protocol for plugins would be a disaster, and I also assert that MIDI has inadequate semantics to represent real music. For years now I have been yapping away about extending MIDI with (a) higher bandwidth and (b) floating-point data fields in channel messages. These would take care of 2/3 of the required semantics. Adding (c) sample-frame timestamps, (d) note IDs, and (e) user-extensible opcodes would take care of the rest. The only "adapter" required for most existing drivers and plugins is type casting. Original Message: ----------------- From: Ron Kuper RonKuper@xxxxxxxxxxxx Date: Tue, 15 Jun 2004 12:17:52 -0400 To: gmpi@xxxxxxxxxxxxx Subject: [gmpi] Re: 3.15 MIDI Let's not forget that this is an MMA working group. *MIDI* Manufacturer's Association. Belonging to the MMA is going to help achieve broad acceptance of this effort, help in marketing, add a sense of overall legitamacy to our effort. If GMPI comes out of the gate with an design that treats MIDI like an ugly stepchild, we won't win the hearts and minds of the major instrument vendors whose business is built on MIDI. I can be happy with code that converts MIDI byte streams into GMPI control signals. But this code needs to be standard part of the GMPI developer kit, so that any plugin vendor who wants to "think" in GMPI, but "listen" in MIDI. Conversely, there are going to be vendors who want to "think" in MIDI. Perhaps they have legacy plugins that are built around MIDI byte streams, and they want to port them to MIDI. For these reason we need some way for a GMPI plugin to receive raw MIDI messages. Maybe we define "MIDI bytes" as a control signal data type? Someone, "No MIDI. We're done." If we have no MIDI, we are done. Literally. -----Original Message----- From: gmpi-bounce@xxxxxxxxxxxxx [mailto:gmpi-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Hockin Sent: Tuesday, June 15, 2004 11:16 AM To: gmpi@xxxxxxxxxxxxx Subject: [gmpi] Re: 3.15 MIDI On Tue, Jun 15, 2004 at 02:46:08PM +0100, Martijn Sipkema wrote: > supported by GMPI to allow these use cases. What I do mean to say is: > should a successor to MIDI be decided here? Why not have a seperate > open discussion on the problems that MIDI might have and how these can > be resolved? If you want to work up a successor to MIDI< that would be fine. But when it comes down to designing a software architecture, any system which has more than ONE and ONLY ONE control mechanism for plugins is broken. If my plugin needs to handle GMPI and MIDI, then the GMPI API is braindead. Period. You eliminate the complexity for everyone, in one swell foop. That's what a good API does. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . ---------------------------------------------------------------------- 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