[Openal-devel] Faster buffer model, and more random stuff

[Chris Robinson]

On Tuesday 26 February 2008 01:57:36 pm Jason Daly wrote:
> On the positive side, Creative tries to sell OpenAL to game developers
> at every opportunity, which is why major titles like UT3 and Mass Effect
> are OpenAL titles.  If we want OpenAL to go anywhere, we need Creative
> in the loop.

Of course, I'm not saying we should cut them out or anything. But I think as 
much as we need to keep up with them, they could try keep up with us. With 
constantly leaving us in the dark WRT new additions, not only does it leave 
development one-sided, but it also creates problems with other 
implementations trying to keep up. Their additions become difficult to 
implement on our side, and our additions don't filter through to them.. might 
as well end up being two different APIs.

> I met with Dan Peacock at GDC and trust me, there plans in the works.
> Dan wants to announce them publicly and get feedback, but they're
> keeping it under wraps for now.

Plans with OpenAL itself, or with the development model (or both)?

> I'm not saying don't discuss it (please do!), I'm just saying that it
> would be a good idea to wait and see what Creative is bringing to the
> table before committing to writing anything concrete.

It just leaves me feeling a little put-out when things we bring to the table 
don't even merit much discussion with them (not even a "good idea, we might 
support that" or "that's a terrible idea.."). I can understand company 
politics and that it's not really the fault of any one person and all, but 
I'd think an open API's development would be a bit more... open.