Re: View >> AU communication
Re: View >> AU communication
- Subject: Re: View >> AU communication
- From: William Stewart <email@hidden>
- Date: Thu, 27 Aug 2009 20:17:29 -0700
We don't recommend doing this.
You should be able to keep the view and the model separate, and by
passing addressed between the two, you preclude the capability of say
running in a situation like Logic Nodes
On Aug 26, 2009, at 10:23 PM, tahome izwah wrote:
In your view you keep a reference to your AudioUnit (via the mAU
member variable). In your -setAU method you could call
AudioUnitGetProperty(mAU,
kAudioUnitCustomProperty_AssociatedDSPClassPointer,
kAudioUnitScope_Global,
0,
&mRefCon,
&dataSize);
to get the instance of your DSP class (in mRefCon), and cast this to
(myDSPClass*) in your code to use it to set your preset name.
In your DSP class you would have to implement this property (in
GetProperty and GetPropertyInfo) so it returns "this"
HTH
--th
2009/8/26 Stephen Blinkhorn <email@hidden>:
Bonjour,
I'm struggling with something that seems simple. In my Cooca view
I have
some text fields where the user may enter strings to name certain
parts of
the audio unit. I need to save these strings as part of a preset
which I
can do via SaveState() and RestoreState(). But, I can't figure out
how to
tell the AU that the user has entered new strings.
I thought I could just issue a PropertyChanged() type call from
within the
view but it seems this is not the intended use for properties. Am I
mistaken? Should I just pass a pointer from my AU to my view?
That seems a
bit shaky somehow.
Thanks,
Stephen
_______________________________________________
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
_______________________________________________
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