Re: After installing an Audio Unit...
Re: After installing an Audio Unit...
- Subject: Re: After installing an Audio Unit...
- From: Chris Reed <email@hidden>
- Date: Tue, 4 Mar 2003 14:41:24 -0600
I agree.
I build my AUs into the project directory and run a script as part of
the build that deletes the old component and copies the new build into
place. I've never once had to restart to get any app to see the
component.
And the same applies when installing third-party AUs. I just drop them
into place and they're pretty much immediately available. (After
re-lauching whatever host.)
-chris
On Tuesday, Mar 4, 2003, at 14:00 US/Central, Marc Poirier wrote:
Some observations, for what they're worth:
I've found that the Component Manager always finds new or changed AUs
if I
drag them into a Components folder in Finder. If the components have
more
or less "gradually appeared" via building them in Project Builder into
the final location for the first time, then I almost always have
problems,
but I can solve the problem by dragging the component out and then back
inside in Finder. I definitely don't know the underlying technical
issues, but it seems to me that there is some sort of monitoring of the
special enchanted locations where copying or moving activities will be
noticed. Perhaps the installer does those in a way that is not
noticed by
this monitoring.
Anyway, I don't know if this is all of much use, but I've recently at
least found that rebooting doesn't ever seem to be required and that,
in
those bad situations, simply manually dragging out and dragging back in
the component will make it become known. I wish that I could find a
better solution (certainly that makes for a not so useful installer),
though.
Marc
_______________________________________________
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.