Re: openal soft loopback query

Hi Chris,

On 08/02/12 00:34, Chris Robinson wrote:
> Hi.
> The idea with the loopback device is that the device would be processed at a
> rate similar to everything else. That is, the faster you render samples, the
> faster you check and update your sources and everything. Working synchronously
> would be simplest, so for example you'd do:
...

> As long as you don't render too many samples at once, or have short buffer
> queues, this should keep up just fine and get everything out ASAP.
>
> If you were to render samples asynchronously, then you would need to
> artificially limit how fast it renders samples so the main app (what's calling
> "CheckAndUpdateSources") can keep up. In such a case, the main app could
> probably use a semaphore or something to tell the async thread when it's okay
> to render. For example:
Hmm, yes I had more of a think about this last night, and I was thinking 
of all sorts of horrible asynchronous stuff: but I just realised my code 
is all synchronous and pull-based, so there's no reason to get so 
complicated.  Even if I want to do threaded rendering of the source 
material I can put that behind a synchronous interface easily.

Thanks for the ideas.

Cheers,
  Michael

_______________________________________________
Openal mailing list
[email protected]
http://opensource.creative.com/mailman/listinfo/openal