Re: View >> AU communication
Re: View >> AU communication
- Subject: Re: View >> AU communication
- From: "Sophia Poirier [dfx]" <email@hidden>
- Date: Mon, 31 Aug 2009 18:48:42 -0400
But no, it's not safe. Bill already mentioned earlier in the thread a
context where it won't work (Logic nodes: separate address spaces).
And if you look at the Filter example, you'll see that it is doing
what I describe (passing buffers of the data itself), not passing a
reference to data or a class instance.
Sophia
On Aug 30, 2009, at 9:09 PM, tahome izwah wrote:
I still claim that passing a reference is safe as long as you do it in
-setAU, which is where view and DSP part of the AU are associated. I
also recall seeing this being used by the filter example in Apple's
developer AUs.
--th
2009/8/30 Sophia Poirier [dfx] <email@hidden>:
You use the GetProperty/SetProperty system. Define your own custom
properties and handle passing the actual data itself in buffers,
rather than
references to data (as the previous example of passing your effect
unit's
"this" pointer was incorrectly demonstrating). If it's a property
that can
change and your view (or anything else) needs to be aware of the
changes,
then you use PropertyChanged() from your effect AU.
If you search the archives, you'll find more info (this has been
covered
many times in detail on the list). Also I've made a relatively
simple open
source AU that demonstrates some of this stuff if you're interested
in an
example:
http://destroyfx.org/extras/#rmsbuddy
- Sophia
_______________________________________________
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