Re: Audio unit view communication
Re: Audio unit view communication
- Subject: Re: Audio unit view communication
- From: Marc Poirier <email@hidden>
- Date: Mon, 7 Jun 2004 09:00:53 -0400 (EDT)
On Mon, 7 Jun 2004, Frederik Slijkerman wrote:
>
Hi all,
>
>
We're porting a VST plugin to the Audio Unit format, and I
>
have a question about how the view is supposed to communicate
>
with the audio unit itself. As I understand it, the view is
>
instantiated by the host separately from the audio unit itself,
>
and should communicate with the audio unit through the standard
>
property mechanisms.
>
>
Is it possible to just retrieve a property from the audio unit
>
that returns a pointer to an internal object in the audio unit
>
that is subsequently used and modified by the view, or is this
>
unsafe?
>
>
In other words, do the view and the audio unit always live in
>
the same address space?
Yes, they currently always do live in the same address space. However,
this is still not a good idea. One problem is that there can be more than
one UI opened for a single audio component. This happens in some
circumstances in Digital Performer and Rax, I know. And that's valid
behavior, and a properly made AU should handle this.
You should communicate using custom properties. Here is some more info:
http://www.mat.ucsb.edu:8000/CoreAudio/54
Marc
_______________________________________________
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.