I'm confused, this is what the 'Filter' example is doing in the CoreAudio SDK. Specifically, I believe it is passing a pointer from the UI class back to the AU and then setting values in memory being pointed to.
It would seem to me that probably a lot of people do this, and what the property feature of the AU api would be used for, since it is specifically passing a void pointer.
Now, I agree, that I too would REALLY like to be able to run distributed AU's, as I run Digital Performer 5. How far is this feature off? 10.5?
What would be the suggestion? Not use properties and just keep two copies of my data, one in the AU and one in the UI and update them both on any changes from the host or UI?
Rick
>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.)
>Best,
>Stefan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
This email sent to email@hidden
