Re: more AU info and plugins (should be "I need to share data")
Re: more AU info and plugins (should be "I need to share data")
- Subject: Re: more AU info and plugins (should be "I need to share data")
- From: Marc Poirier <email@hidden>
- Date: Mon, 23 Jun 2003 07:53:17 -0500 (CDT)
On Sun, 22 Jun 2003, Glenn Olander wrote:
>
That sounds like a definitive answer to my question about properties.
>
So, where did that guideline Marc mentioned about not passing pointers
>
between the DSP and GUI components come from? It is starting to look
>
like an urban myth :-).
I don't know, I think that some people started saying it, and then no one
ever said it was wrong. Despite Chris's post, I have been reading this
list for a long time (since before there were AUCarbonViews) and
definitely don't remember anyone every conclusively saying that this
wasn't the case, but perhaps that just slipped past me. So I'm not sure
how definitively to take Chris' comments, but of course we don't have a
definitive answer for either way.
Also, since every property get and set involves specifying a size for the
data being set and get, so there's nothing making it impossible for the
Component Manager to know about the size of the data content.
But at any rate, there were more reasons for the "Marc guideline" ;) than
just this. Like Philippe mentioned, you also don't control the life cycle
of other components like the GUI component, and in addition I mentioned in
there that there can be multiple GUI components for a single audio
component (Rax already does this, for example). But since the whole
accross-processes thing is more in question than I initially realized,
I'll go back and ammend my contribution to the swiki...
>
Of course, if you're looking for a way to significantly distinguish AU
>
from the VST/DX/MAS/RTAS crowd, offering a mechanism to put the GUI and
>
DSP components into separate processes would certainly qualify. In
>
other words, you may want to consider replacing the current property
>
and component system with one which _does_ support inter-process
>
communication. I don't have any illusions that this would be a small
>
job, but it would certainly be a significant step
>
forward for plugins.
Yeah, even if it's not possible currently, the current AU design is
certainly the way to allow it to be possible in the near or distant
future, and there's NO doubt that this capability is something that
musicians really really want, and that would be quite attractive for
musicians if Apple/CoreAudio could be the ones to make it happen... :)
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.