Thanks for your feedback. Cocoa UI is the one.
----- Original Message ----
From: Brian Willoughby <email@hidden>
To: Peter Johnson <email@hidden>
Cc: email@hidden
Sent: Thursday, 19 April, 2007 4:15:35 AM
Subject: Re: Audio Unit UI
Peter,
If your product is non-commercial, then just implement a Cocoa UI and
be done with it. Carbon-only hosts can show parameters in their
default UI. If your product is commercial, and you have a budget for
developing a Carbon UI,
then do both. In the commercial world, you
cannot afford to have customers asking why the UI does not appear in
their favorite host. In both cases, though, you should implement a
Cocoa UI, and hopefully your best efforts towards the long-term code
base will be on the Cocoa UI side.
Brian Willoughby
Sound Consulting
On Apr 17, 2007, at 17:32, Peter Johnson wrote:
> Hi
>
> I've been looking into adding a custom graphical UI to my AU. I
> have limited knowledge of both Cocoa and Carbon.
>
> The developer examples seem to focus more on Cocoa. However from
> what I can gather a lot of commercial AU's use Carbon. I'm
> wondering what the preferred API is? Going forward, should I be
> focusing my efforts into learning Cocoa, it seems to have better
> tool
support in Xcode. Or for maximum compatibility with various
> hosts (Logic, Garageband, Live, DP, STP) should I be providing a
> purely Carbon UI? It's a little confusing. And if Carbon is the
> "better" API, is their an SDK to make it easier?
>
> I realize this is a rather vague and general question, my request
> is more for opinions on the best way forward.
>
> thanks
> peter
>