Paul said:
>I see the questions as the following. Q's 1-4 collect the data, 5makes a decision, 6 & 7 cover how we address the decision outcome (I think we could just as well have asked 1-5 for the multichannel audio formats too).
i think this is a good list, with one caveat.
(more or less) everybody on this list knows that there is a gap, sometimes sizeable and sometimes smaller, between "requirements" driven by marketing concerns and "requirements" driven by technological considerations.
my interest in the GMPI process will be greatly diminished if our "requirements" end up including stuff that is truthfully associated with marketing rather than technology. a plugin API that permits developers to make some particular claim about their code as a way to differentiate it from that of everybody else using the same API: this is not a good outcome from my POV.
so i think that in answering these questions, we need to be very, very clear where a particular "requirement" originates. genuine technological concerns need to be addressed; marketing hype should not, i hope, play much of a role in our discussions. this means, in very down to earth terms, that issues with hardware capabilities, verifiable performance cost/benefit analyses, and so forth should be very much central to the answers, whereas hand waving claims about specific attributes of particular data types should not.
i hope that sounds agnostic enough.
--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
