Initialize, Cleanup, State
Initialize, Cleanup, State
- Subject: Initialize, Cleanup, State
- From: Art Gillespie <email@hidden>
- Date: Sun, 11 Dec 2005 23:32:48 -0700
I need to check my mental model of the Initialization/Cleanup/State
Persistence stuff and ask some questions.
Here's how I currently understand it:
An Audio Unit is expected to maintain its user-facing state
(parameters, settings, etc.) across paired Cleanup/Initialize calls.
Is that correct?
If it *is* correct, where would this leave loaded samples? Should a
plug-in unload them on Cleanup() and reload during Initialize()? The
documentation for Cleanup ("This function may be used to return an
Audio Unit to its uninitialized state, causing it to release
resources without closing the component") suggests that it should,
but that seems like a lot of heavy lifting for a simple sample rate
change.
Also, I found it difficult to nail this whole subject down: the
aforementioned documentation didn't turn up any mention of
maintaining state across these calls, and neither did grepping the
CoreAudio SDK headers and source. Is there a Single Point Of Truth
somewhere that I'm missing or is this aspect of the Audio Unit
specification more of an Oral Tradition thing?
Thanks,
Art
--
Art Gillespie
CEO
Glaresoft, Inc.
e. email@hidden
a. bitshift189
p. 520.245.7839
_______________________________________________
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