[Openal-devel] alProcessFlags commands

J. Valenzuela valenzuela at treyarch.com
Tue Jan 27 07:50:26 PST 2004


On Jan 25, 2004, at 3:36 PM, Manuel Jander wrote:

> Hi,
>
> I need some design inside to the function _alProcessFlags( void )
>
> Its description states that its job is to handle commands that have 
> been
> posted to a mixsource node.
>
> My question is, what exactly are mixsource nodes ?

_alMixSource nodes are those items processed by _alMixSources.
al_mspool.h contains the definition.

> Does it means nodes
> in the mixing mesh ? That would be very odd since shouldn't processing
> be done in hardware ? I would like to handle mixing in hardware, 
> because
> i wouldn't like to waste a 32 input channel hardware mixer.

The GNU/Lunix implementation's first responsibility is as a faithful
software renderer.  But it's probably overdue to add mixing in hardware,
at the very least as a bullet point.
>

> What kind of command are meant to be processed ? It sounds like i could
> define new commands to program hardware parameters, but is this the 
> kind
> of command meant in this case ?

Bookkeeping stuff for mixsource nodes.  Sounds analogous.  You might 
have
some luck sneaking something in there.

> Excerpt of al_mixer.c:
>
>  * _alProcessFlags( void )
>  *
>  * The mixing function (_alMixSources), in the course of it's job marks
> the
>  * mixsource nodes with commands that need to be executed after the
> completion
>  * of the mixsource's iteration through the loop.  This is the function
> where
>  * such things are done.
>  *

I can't believe I used an apostrophe with the third person possessive.
I'm going to go cry.

--
jv




More information about the Openal-devel mailing list