Re: AU Components on the fly
Re: AU Components on the fly
- Subject: Re: AU Components on the fly
- From: Urs Heckmann <email@hidden>
- Date: Sat, 11 Jan 2003 00:02:24 +0100
I wrote:
Okay okay, I'll consult the Carbonites first...
I did, and it was not very couraging.
The ComponentManager stuff Marc mentioned seems to be out of date.
However, this is what Stephen Zellers of Apple's Carbonites says:
The documentation is out of date and incorrect:
If you do not specify this flag, the component is available for use
only by the registering application or component (that is, the
component is local to the A5 world of the registering program).
We don't have A5 worlds anymore, either ;-)
It would be possible to create a stub component that could use mach
messaging to communicate between additional components instantiated
within other applications. But the component manager itself will not
do anything to facilitate this. You might try looking into using
CFMessagePort to set up a communications with a master instance of
your component (or preferably, a seperate process that provides
services to your component.)
--smz
Okay, so we still have a chance to cybowire audio from one app to
another. But I don't know if this isn't more complex than writing a
virtual soundcard with an SMPTE signal on line 9...
Cheers,
;) Urs
_______________________________________________
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.