• 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: Audio Unit scope
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Audio Unit scope


  • Subject: Re: Audio Unit scope
  • From: Bill Stewart <email@hidden>
  • Date: Wed, 30 May 2001 12:44:06 -0700

AudioUnits are components.

We distribute the built-in components as a .component CFBundle. Project
Builder has settings that allow you to specify output as a component. So
you're Audio Unit will should be built this way.

Installation:
There are two pre-installed directories where you can install the AudioUnits
and they will be automatically scanned by the ComponentManager and
registered on log in.

/Library/Audio/Components
~/Library/Audio/Components

/Lib is a system wide directory who's contents are available to ALL users of
a particular machine. You have to be a user with admin priveleges to install
into this directory.

~/Lib is a USER-based directory structure - each user gets their own copy of
this directory and has complete ownership of it. Thus, different users can
have their own version of components, sound fonts, DLS, plug-ins, etc... and
are free to install/remove/modify contents of those directories.

If you want to keep them private... You can have private components and
register them yourself - this is quite acceptable of course. See docs on the
Component Manager for how to do this

Bill

on 29/5/01 6:18 PM, Roger Butler wrote:
> Hi all,
>
> I'm starting to write a general Audio Unit that has both inputs and outputs.
> My question is about packaging it. Can AUs be packaged as plug-ins
> (loadable bundles)? If so, are they available to the whole system or just
> to applications that know how to find and use them? Is there a folder
> within the /system/library folder to place plug-ins? What if I want to keep
> them private? Can I make a private framework and embed it within my own
> application?
>
> Roger Butler,
> Lake Technology.
> _______________________________________________
> coreaudio-api mailing list
> email@hidden
> http://www.lists.apple.com/mailman/listinfo/coreaudio-api


mailto:email@hidden
tel: +1 408 974 4056
__________________________________________________________________________
Cat: "Leave me alone, I'm trying to nap... Ah, What's that clicking noise?"
__________________________________________________________________________


  • Follow-Ups:
    • Re: Audio Unit scope
      • From: James McCartney <email@hidden>
References: 
 >Audio Unit scope (From: Roger Butler <email@hidden>)

  • Prev by Date: Re: Repost of SDK instructions? (and Doc availability)
  • Next by Date: Re: Audio Unit scope
  • Previous by thread: Audio Unit scope
  • Next by thread: Re: Audio Unit scope
  • Index(es):
    • Date
    • Thread