Re: Don't exchange pointers, was Re: Objective-C++/C++ with CocoaUI Issue...
Re: Don't exchange pointers, was Re: Objective-C++/C++ with CocoaUI Issue...
- Subject: Re: Don't exchange pointers, was Re: Objective-C++/C++ with CocoaUI Issue...
- From: Shaun Wexler <email@hidden>
- Date: Tue, 20 Jun 2006 08:54:58 -0700
On Jun 20, 2006, at 3:41 AM, Stefan Gretscher wrote:
Am 19.06.2006 um 17:10 schrieb Richard Burnett:
What I had tried to do was pass in the address of a pointer from
the UI to the AU code
Please don't - AUs are generally designed so that the view code and
the processing code can live in separate address space or even on
separate machines, and exchanging pointers between UI and core
breaks this design.
Consider an environment like Logic Nodes where the audio processing
can be distributed to remote machines for utilizing additional CPU
resources, while the UI is working on the main machine - there's no
way to exchange pointers there.
(Logic Nodes are currently limited to Logics built-in plug-ins, but
there's a strong user demand to open up this technology for AUs as
well.)
To exemplify that point, MacFOH handles its audio in a root daemon
process that is controlled by a separate GUI app, thus the engine
can't even "see" the app in the global bootstrap namespace, and the
GUI app(s) might in fact be running on a different host... yes,
multiple GUI's controlling the same engine.
--
Shaun Wexler
MacFOH
http://www.macfoh.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden