• 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: AU Components on the fly
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU Components on the fly


  • Subject: Re: AU Components on the fly
  • From: Urs Heckmann <email@hidden>
  • Date: Thu, 9 Jan 2003 22:53:12 +0100

Am Donnerstag, 09.01.03, um 21:10 Uhr (Europe/Berlin) schrieb Marc Poirier:

Sure, it should be possible. If you look at the AUPublic headers,
ComponentBase.h in particular, there's the ComponentRegistrar class
that will do exactly this for you. And the COMPONENT_REGISTER macro to
make it easier. To go a little lower-level, the Component Manager has
the RegisterComponent() and RegisterComponentResource() functions.

The only thing I'm not sure about is if when you register a component
in your app, will it be made available in other processes?

Luckily that's what the registration flags argument is for. More info:

http://developer.apple.com/techpubs/macosx/Carbon/runtime/ ComponentManager/Component_Manager/Enumerations/ Register_Com_source_flags.html

Marc


Okay, just read through the references. Components can simply be put up from memory and (if I understand correctly) be treated just the same way as a file-based component where the description is in the resource. This opens up amazing possibilities, right? ComponentManager takes care of component lifetime and sends the host a cheerful letter when the application that in our case "owns" the AU quits and hence the component is no longer available.

Seriously, doesn't this mean we have System built-in ReWire equivalent? - I mean, an App could easily switch to slave mode if its internal AU space gets hired by another Application. It would then be synced via the Tempo callbacks, etc. etc. etc. Or is there a trap like the AU-providing app can't access foreign invoced component instances? I mean, registerComponentGlobal just says that it won't be available to foreign apps if not set.

Robert, please make a RAX rack optionally available as an AudioUnit so we can use your GUI to drive the Apple AUs from within SynthTest :-))

I think we should send P'heads a reasonenable mail?

Okay okay, I'll consult the Carbonites first...

Cheers,

;) Urs
_______________________________________________
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.

  • Prev by Date: Some CoreAudio properties not accessible via Java API?
  • Next by Date: kAudioUnitParameterFlag_Global
  • Previous by thread: Re: AU Components on the fly
  • Next by thread: Re: AU Components on the fly
  • Index(es):
    • Date
    • Thread