[Openal] EAX4.0 and OpenAL

[Garin Hiebert]

> Question 1:
> On the latest source code  of OpenAl I have downloaded using cvs
> (windows version), you have added in the ALlistener and ALsource
> structure EAX2.0 parameters which belong the "Extension". Which means
> that each someone wants to add a new extension he needs to add new
> parameters to these structures? These structures are going to be very
> big with a lot of unused parameters.

Source-local copies of all the EAX parameters are kept to improve
performance (at the expense of sacrificing some memory).  When you do a
"get" on one of these values, the driver doesn't need to be queried.  When
you do a "set," the driver only needs to be set when the value actually
changes.

Speaking of the more general case, if you are implementing an extension
you can do what you want -- keep extension data local to extension code,
store stuff with the sources -- whatever works.

> Question 2:
> When do you plan to release the source code of OpenAL with EAX4.0
> extension and EAXunified ?

Due to preparations for GDC (Game Developer's Conference) at the end of
March, the next major update to the Windows codebase will probably be in
April or May (performance increases, good Ogg Vorbis support, etc.). 
There will probably be a few small bug fixes integrated before then, but
nothing big.


Garin