Re: AU Properties and Initialization
Re: AU Properties and Initialization
- Subject: Re: AU Properties and Initialization
- From: "K. Ware" <email@hidden>
- Date: Sun, 30 Mar 2003 11:22:04 -0500
Hello,
There is a
kAudioUnitErr_Uninitialized error, but no
cannot-do-that-when-initialized
counterpart. So anyway, I would propose adding an error code called
something like kAudioUnitErr_Initialized, because otherwise there
won't be
a way to clearly tell the host that unitialization is required.
I like this proposal. We've already run into the issue of a host
attempting to set/modify some properties while the AU was initialized.
We return an error (and the host now uninitializes/initializes) but
unfortunately, there seems to be at least a couple error codes that
could be generated in such a case: kAudioUnitErr_PropertyNotWriteable,
kAudioUnitErr_CannotDoInCurrentContext, kAudioUnitErr_InvalidScope
We currently give an kAudioUnitErr_PropertyNotWriteable error but
looking back, perhaps kAudioUnitErr_CannotDoInCurrentContext would be
the more appropriate code. This would be simplified if we could just
give the kAudioUnitErr_Initialized error. This would clearly indicate
to the host what the problem is. As it stands now, a host would either
need to attempt uninitialization/initialization when any error is
returned or attempt to guess which error codes indicate that the
attempted property set might work if the AU was uninitialized.
-k
_______________________________________________
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.