Re: Cocoa and AudioUnits?
Re: Cocoa and AudioUnits?
- Subject: Re: Cocoa and AudioUnits?
- From: Chris Reed <email@hidden>
- Date: Mon, 20 Jan 2003 15:37:45 -0600
Robert Grant, a list member, recently did some experimentation with
Cocoa interfaces for Audio Units, and the results were kind of
disappointing, at best.
The real problem is that the Cocoa/Carbon interoperability stuff is
limited in that Cocoa and Carbon views cannot be embedded into a window
of the other API. That is, you cannot embed an NSView in a Carbon
window. And the AudioUnitCarbonView API is designed to work at the
control level, not the window level. So you have to create a host
Carbon control that opens your Cocoa edit window. It works, but the
user experience is so bad that you just shouldn't do it.
That said, you really should take a look at Airy Andri's Audio Unit GUI
SDK. See <
http://airy.andre.online.fr/AU/>. Airy's library lets you use
Interface Builder to construct the edit view and set up
control-to-parameter mappings. For simple to medium complexity
interfaces, you probably won't have to write a line of code.
Urs Heckmann, another list member, also has an excellent GUI SDK that
makes it much easier to build your interface than using Carbon alone.
http://www.u-he.com/audiounits/
Writing AU editors may not be as easy as Cocoa, but it's not *that*
hard. Using one of the SDKs above, it's really no harder than it would
be using Cocoa. (honestly!) You just have to get used to the
differences.
-chris
On Monday, January 20, 2003, at 02:15 PM, Robert Abernathy wrote:
I've started to work on developing (learning to develop) AudioUnits. I
was at first disappointed to see that I would need to use Carbon for
the UI. Then I went and looked at the Carbon docs, and now I'm really
disappointed! There were good reasons I stopped using Macs and went to
NeXT. I looked through the archives regarding this question and I've
got to say I was disturbed.
So now that 10.2.3 is out, and the Cocoa-Carbon interoperability stuff
is there a bit, is this a reasonable path to take? This seems to be a
bit painful to have to do each time. When looking at the bundle
documentation, it seemed to me that the only limitation to having a
native Cocoa AudioUnit SDK would be the ObjC runtime limitation on
unloading symbols.
Can someone from Apple give a hint about the possible future of Cocoa
for AU UI's? Do we need to start a grassroots movement to develop a
way to do this?
Sorry to be a bit grumpy about this, but when I look at the developer
site at Apple, I get the feeling that Cocoa is taking a back seat (and
not just for audio). I think that this is a major mistake.
Thanks for your help,
Rob
_______________________________________________
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.
_______________________________________________
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.