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: Glenn Olander <email@hidden>
- Date: Sun, 22 Jun 2003 22:12:51 -0700
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 :-).
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.
Glenn
Chris Reed wrote:
I thought the last time this came up (or one of the previous times, there have been several), it was determined that the OS X implementation of the ComponentManager simply did not, and almost certainly never would, support cross-process component instantiation.
Also, the current way properties are used really doesn't lend itself to working across process boundaries. Passing pointers in the Get/SetProperty calls that are then directly used within the AU code just won't work, will it? I mean, for a wrapper to work it would have to be aware of each property's data content and copy it between the process. So there would have to be something sitting on top of the ComponentManager that knows about the AU API. (Not impossible, though, if you could work around the ComponentManager.)
_______________________________________________
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.