Re: Using converter API for a multiple streams driver
Re: Using converter API for a multiple streams driver
- Subject: Re: Using converter API for a multiple streams driver
- From: Doug Wyatt <email@hidden>
- Date: Tue, 18 Jan 2005 14:17:59 -0800
On Jan 18, 2005, at 13:41, Stéphane LETZ wrote:
On 18 janv. 05, at 19:35, Doug Wyatt wrote:
Stephane,
You'll need one converter per stream, since there's no way to
describe all of the 828's (or similar device's) streams with a single
AudioStreamBasicDescription. If all of the device's streams are mono
-- there are some devices like this -- you can special-case that and
just have one converter.
Or you could write your own set of interleaving/deinterleaving
routines (it's a bit of a pain to handle arbitrary numbers of
channels efficiently but it's certainly possible). If you do this it
would be wise to analyze the generated code for stalls.
Doug
Thanks.
I was thinking using Converter would always be more efficient (because
i guess they are Altivec optimized) than writing
interleaving/deinterleaving routines.
At the moment the interleave/deinterleave loops are not altiveced
(subject to change) though they are well scheduled.
BTW what does the AUHAL? can the AUHAL convert a set of stream (like
828) in a set of mono non inteleaved streams? does the HAL use also
several converter to do the convertion?
yes and yes.
Doug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden