Re: vDSP: performance costs of stride size != 1
Re: vDSP: performance costs of stride size != 1
- Subject: Re: vDSP: performance costs of stride size != 1
- From: Brian Willoughby <email@hidden>
- Date: Fri, 17 Feb 2012 18:04:27 -0800
On Feb 16, 2012, at 12:11, Morgan Packard wrote:
I understand it's preferable to keep stride size to 1 when using
the vDSP functions of the accelerate framework. Does anyone have
any experience (or numbers) relating to performance and stride
size of greater than one? I have a single-channel envelope signal
that I'd like to apply to an interleaved stereo signal. If I can
get much better performance by using a two-channel envelope signal
(this keeping the stride to 1), I'll consider reworking my code.
You'll note that AudioUnits have deprecated the interleaved audio
formats. Thus, it should be rare that you'd be processing an
interleaved stereo signal. It's probably best to de-interleave that
stereo signal at the very beginning of your graph and then handle all
processing on the individual channels. That way, not only the
envelope but all other processing will be as fast as possible. Let
the output unit pair them up again as stereo.
Brian Willoughby
Sound Consulting
_______________________________________________
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