Re: AU Properties and Initialization
Re: AU Properties and Initialization
- Subject: Re: AU Properties and Initialization
- From: Marc Poirier <email@hidden>
- Date: Sat, 29 Mar 2003 22:25:33 +0100 (CET)
Bill,
Thanks, this clarification is very much appreciated! There's just one
little thing that I see left hanging:
>
It seems a simpler semantic to us (and this was our initial design
>
goal) to firmly separate the establishment of state from the process of
>
rendering., thus, returning an error is I believe entirely acceptable
>
and appropriate. This might be different for different AU's and a host
>
application should be prepared to deal with this.
This sounds fine, but unfortunately there currently isn't a clear way to
say to the host, "Hey, you can't do that because I'm already initialized.
You need to unitialize me if you want to do that." 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.
Marc
_______________________________________________
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.