a reason to not access AU from AUView via a direct pointer
a reason to not access AU from AUView via a direct pointer
- Subject: a reason to not access AU from AUView via a direct pointer
- From: Marc Poirier <email@hidden>
- Date: Fri, 27 Dec 2002 17:29:33 +0100 (CET)
The topic of communicating between AU (audio part) and AUView by using
properties and parameters vs. using direct pointers to the AUEffectBase
(or whatever you use) class instances was discussed a few months ago. I
remember Apple folks saying that using properties was better. I have
still been using direct pointers for some things as a matter of
convenience, but I just thought of a pretty good reason to not do this
anymore.
This might not be a very likely scenerio today, but I could see it
sometime in the near future: What if the effect/instrument component was
loaded in a different address space than the view component? A simple
example: a musician is using a group of computers to handle audio
processing; one computer is running the DSP component of the AU while the
musician is using another computer to edit the AU parameters, hence the
AUEffect and AUView are instanciated on different computers (which to me
is one of the nice advantages of having them be separate components). The
pointer address for one will be completely bogus in the context of the
other component.
So anyway, I just thought I'd share this idea with other folks, and maybe
someone else has more to say about it...
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.