RE: Audio Unit scope
RE: Audio Unit scope
- Subject: RE: Audio Unit scope
- From: Roger Butler <email@hidden>
- Date: Thu, 31 May 2001 11:46:04 +1000
Great, that's cleared up a lot of things. Are the folders you mention
actually /Library/Audio/Plug-Ins/Components rather than
/Library/Audio/Components?
And what about the GUI side of an Audio Unit. Do applications have to
manipulated AU properties through function calls? Can we write such an
application and have it appear in the System Preferences? Or is there
another preferred method for modifying AU properties?
Roger.
>
-----Original Message-----
>
From: Bill Stewart [mailto:email@hidden]
>
Sent: Thursday, 31 May 2001 5:44
>
To: Roger Butler; CoreAudio API
>
Subject: Re: Audio Unit scope
>
>
>
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?"
>
______________________________________________________________
>
____________