Re: AU2 - saying "no" to interleaved streams
Re: AU2 - saying "no" to interleaved streams
- Subject: Re: AU2 - saying "no" to interleaved streams
- From: Doug Wyatt <email@hidden>
- Date: Mon, 7 Oct 2002 18:24:52 -0700
On Tuesday, Sep 24, 2002, at 10:48 US/Pacific, Paul Kellett wrote:
I think I missed something here - at the moment my v2 effects
(based on SampleEffectUnit) are designed to cope with interleaved or
non-interleaved audio data, as I looked at what ProcessBufferLists()
was doing.
That code is that way because we use it internally for our own units,
some of which have to support V1 for backwards compatibility.
But are you saying that AUBase has already rejected interleaved
channels and I'll never see them? And it's ok because nobody is ever
going to ask a v2 effect to process interleaved channels?
They might ask, but you would be within the spec to return an error.
This might help conceptually: "inside" the AU world, everything is
expected to be in the canonical format, deinterleaved Float32. On the
edges -- e.g. an input proc supplying integers to a unit which supports
conversion, or outputting to hardware (e.g. interleaved, some odd
channel configuration) -- there is support for other formats.
Doug
--
Doug Wyatt
work: email@hidden (CoreAudio)
personal: email@hidden
http://www.sonosphere.com
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.