On Thu, Jun 24, 2004 at 12:18:51PM +0200, Koen Tanghe wrote: > I realize we could see this as a compromise, but it still seems strange to > me, and I really hope that we won't get the same old thing again from this: > in GMPI compliant host X you won't be able to chain GMPI plugin Y after GMPI > plugin Z in a successful way because Z uses the MIDI bytes only, and Y doess > it the right way using the GMPI messages, without generating MIDI bytes. I > really hope this won't be a problem and people won't start saying: "well, > plugin Z doesn't support MIDI, and that's way our plugin Y can't work the > way it should"... This is exactly what will happen, unless we do a proper job of educating people on the merits of converting their pure-MIDI plugins to be GMPI. > But if everyone feels good enough about the stapled MIDI bytes being there, I don't think anyone in NMiG feels GOOD about the stapled MIDI bytes, but I think we can leave it alone for now, and come spec time, we will revisit all the details of everything. This is, after all, requirements. We've already been FAR too techincal on a lot of reqs, and I think a second pass of the reqs doc will have to weed out some of the technical decisions we're making prematurely. So that said, how about feedback on those reqs...? :P ---------------------------------------------------------------------- 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