[gmpi] Re: using another plugin API
- From: "Vincent Burel" <vincent.burel@xxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Thu, 24 Apr 2003 09:07:34 +0200
i think it's a lazzy suggestion, completely against the GMPI purpose.
i thought that the goal was for everybody to bring their own knowledge and
experience on existing SDK (official or unofficial : some of us might have
developped private plug-in API ) in order to design the perfect GMPI. not to
select and custom an existing SDK...
your proposition sounds like a failure somewhere... anyway an openned door
to all drifts...
Vincent Burel
----- Original Message -----
From: "Marc Poirier" <marc@xxxxxxxxxxxxxxxxxxx>
To: <gmpi@xxxxxxxxxxxxx>
Sent: Wednesday, April 23, 2003 11:50 PM
Subject: [gmpi] using another plugin API
> Hello. The possibility has been brought up, early on in the GMPI
> discussions, of starting with an existing music plugin API, adopting it as
> our "standard", and then working with it from there. I would like to
> bring up this option now for more serious consideration, if that sounds
> okay with other folks.
>
> At first I was pretty into the whole idea of GMPI, and I still am in a lot
> of ways, but I'm pretty quickly losing interest in the process. The
> reason is because I'm finding it boring to work through so many details
> and concerns that have already, I feel, been adequately addressed by an
> already exising API. So far, pretty much every conclusion that we've
> reached and decision we've made is the same as what has been decided for
> the Audio Unit API. And I got the sense during the early, unfocused,
> rambling first few days of our email list discussions that a lot of the
> decisions that folks will be inclined to make in the future are also very
> much what AU already is. So what makes the GMPI process boring is that I
> feel like this work has already just recently been done, and has been done
> with a very serious effort with very good results. I think that the final
> results that we could come up with after a year or two of work will be a
> little better, but definitely not enough to warrant all of the redundant
> effort.
>
> And moreover, I think that AU is very repairable. It's pretty close to
> being I think what we really want, with just a small handful of very
> manageable shortcomings, that we as a group could easily overcome, making
> it the perfect API (or the closest possible thing to that) in very little
> time.
>
> I asked Apple's CoreAudio team about the possibility of using AU as the
> generalized, cross-platform music plugin API and about giving up control
> of it to a standards body, and the response was open. Here is the
> response from Bill Stewart (the head of the CoreAudio department):
>
>
> "I'll make some cautionary comments.
>
> "First, there is nothing inherently platform dependent about AU - in
> fact I think the way we handle data formats is inherently neutral to
> any particular data type (the specification of Float32 for linear pcm
> is a convention, not a limitation of the API)
>
> "We are not averse to this idea and are willing to entertain and discuss
> the prospect.
>
> "There is one dependancy that we believe we would require for this to
> work, and that is that CoreFoundation be available. As CF is already in
> open source this should not be a problem. CF gives us a number of
> services that are necessary for both handling data-based transactions
> between the host and the AU as well as some run time issues. The
> presence of CF as well, may also provide the ability to resolve the
> hosting aspect of this in a consistent and cross-platform manner."
>
>
> So anyway, this is my proposal: Let's adopt AU as our chosen API, refine
> it to perfection, and go with it. What do other think?
>
>
> Thanks for listening,
> Marc
>
>
> ----------------------------------------------------------------------
> 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
Other related posts:
