Re: Cocoa-Heavy Audio Unit
Re: Cocoa-Heavy Audio Unit
- Subject: Re: Cocoa-Heavy Audio Unit
- From: Andrew Kimpton <email@hidden>
- Date: Sun, 29 Jan 2006 18:48:42 -0800
Daniel Jalkut wrote:
I'm writing an Audio Unit which will sport not only a Cocoa UI but a
Cocoa-heavy backend. The configuration state for this Audio Unit will
be managed by a key-value compliant objective-C class. So I'd like to
link up my Cooca UI with my AudioUnit logic through bindings.
The example "CocoaUI" does a great job of demonstrating how one might
best provide a Cocoa UI as a "thin exterior" on an otherwise
straight-C based AudioUnit. Does anybody have any thoughts on how
best to bridge the gap for a Cocoa-savvy (to the exclusion of a Carbon
UI) Audio Unit?
The AU approach is very centered around using Parameters and properties
as the only communication between a view and it's processing unit. It
doesn't strike me as an easy transition to use an alternative
Model-View-Controller architecture (like Cocoa's built in one) whilst
retaining the parameter approach.
I'm thinking I'll take the "CocoaUI" approach, but provide a "Fetch my
Cocoa Object" parameter on the Audio Unit, such that the Cocoa nib
owner (...PluginViewFactory) can be charged with returning a
bindings-compatible "audio unit instance" object.
Whilst this will work and allow KVC operations to cross the
view/processing unit boundary it will fail if the two parts are ever
located in separate address spaces or on separate machines. The AU
parameter approach is more robust in these situations.
Any thoughts?
Daniel
Andrew 8-)
_______________________________________________
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