I am in total agreement with Chris Gregg here. I think we should either drop int, or simplify the profile idea as much as possible while still making GMPI attractive to int platform developers. ============================================ Michael Gogins gogins at pipeline period com Irreducible Productions CsoundVST, an extended version of Csound for programming music and sound Available at http://sourceforge.net/projects/csound/ ============================================ ----- Original Message ----- From: "Chris Grigg" <gmpi-public@xxxxxxxxxxxxxx> To: <gmpi@xxxxxxxxxxxxx> Sent: Friday, December 12, 2003 12:40 AM Subject: [gmpi] Re: Reqs 3.8 > Let me chime in for just a second on this. (BTW, I give the > following line of reasoning no more than about a 35% chance of > convincing the group.) I fully understand the no-integer/fixed-point > POV. But: > > - I think the case that there are interesting places where integer & > fixed-point audio is used has been well made, so will just repeat > that my sw company, Beatnik, works only on these platforms yet does a > very nice business. No disrespect to DAW and MI people intended when > I say: mobile platforms mean big, big business, and even more so in > the future, so ignore this market at your own risk going forward. > > - I think there has to be a rule that profiles can only be considered > OK if they don't involve any actual runtime performance hit (I mean > in process()) for any given plug, I mean zero. On the other hand, > profiles will of course make plug authoring (and architecture & API > design) at least a little more complex and time consuming, maybe a > lot if not well designed. So, can I suggest that the important > question for this group at this point might be: Is that complexity > and time expense worth the benefits, for enough of the group members > (however we define 'worth' and 'enough')? > > To help reckon the good/bad of that: > > - If the group doesn't want to support integer & fixed-point > platforms now, in GMPI 1.0, then I wouldn't count to heavily on > creating a derivative format just for integer platforms later. You > have no idea how hard it is to get a major standards effort together, > it'll probably never happen even if GMPI becomes very successful for > music production. So I would suggest: Do, or do not, but decide now. > > - Forked specs bad, harmonized specs good. So the proposed 'integer > derivative' of GMPI is likely to be fragile and susceptible to just > major, major sync issues with 'real GMPI', compromising its > long-range chances for reliability and therefore success. > > - If profiles are made a part of GMPI 1.0, then there probably won't > be a need for a GMPI 2.0 as soon. > > - If profiles are made a part of GMPI 1.0, then defining the actual > profiles for the integer & fixed-point platforms can come any time > later, we don't have to do that part now. > > - New markets to sell into > > - C'mon, running your plugs on Playstation 2 & Xbox & N-Gages, how > cool is that? > > -- Chris G. > > > ---------------------------------------------------------------------- > 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