• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: using Cocoa for AU views ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: using Cocoa for AU views ?


  • Subject: Re: using Cocoa for AU views ?
  • From: email@hidden
  • Date: Fri, 27 Sep 2002 15:45:01 +0100

Hello,

Of course other people on this list know my complaints about having to use the Carbon APIs, so it's nice that other people feel the same way :) It is disappointing to hear you might have to use them for interface elements too!

-- John


Hello

We have some already existing plugin views coded in Cocoa (using a proprietary
sdk for host<->plugin integration) and we'd like to turn them into AUs.

Right now, the way we AU interfaces need to be implemented enforce the use of
Carbon, am I right ?

If I understand correctly, the main call that needs to be implemented is :

virtual ComponentResult CreateCarbonView(
AudioUnit inAudioUnit,
WindowRef inWindow,
ControlRef inParentControl,
const Float32Point& inLocation,
const Float32Point& inSize,
ControlRef& outParentControl
);

This is a problem for Cocoa hosts that need to host AU, although they can create a Carbon
window and host the AU view in its own window, but for people using Cocoa for AU views,
what can be done ?

The problem is the ControlRef parent control. I don't know Carbon _at all_, but would it be
possible to create an NSView that would somehow be embedded in this ControlRef ?

Maybe attaching an NSWindow to the existing WindowRef and then creating an NSView at the
ControlRef location could work but then, how could i synchronise the size and pos when theCarbon control
is moved ? (i'm just throwing ideas at random here)

Or, better : maybe there are plans to provide hooks for Cocoa-based views ?

Would I be better buying a copy of 'Learning Carbon in 100 days' instead ? I'd HATE to do this....

I know Apple is probably concerned first by people who want to port their existing VST plugins to AU,
but it'd be sad if developers weren't allowed to use the best gui sdk (cocoa) on top of the best
audio plugin sdk.

Thanks for some info

Benjamin-
_______________________________________________
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.

References: 
 >using Cocoa for AU views ? (From: Benjamin Golinvaux <email@hidden>)

  • Prev by Date: Stoopid Synth and Filter
  • Next by Date: Re: Routing QT audio to an AudioUnit
  • Previous by thread: using Cocoa for AU views ?
  • Next by thread: Re: using Cocoa for AU views ?
  • Index(es):
    • Date
    • Thread