Re: Audio Unit ioConfigs (Resolved)
Re: Audio Unit ioConfigs (Resolved)
- Subject: Re: Audio Unit ioConfigs (Resolved)
- From: William Stewart <email@hidden>
- Date: Tue, 15 Dec 2009 12:09:39 -0800
When a host launches it will look at the AUs it discovers and one of
the things it checks is the version number to see if it needs to
update any cacheing information. I don't have any desire to change
this basic behaviour. I'll make some enquiries to discover what the
host apps are doing today, and we'll figure out a methodology to deal
with this
Bill
On Dec 15, 2009, at 11:52 AM, Brian Willoughby wrote:
I can't say what Apple's reasons are, but as a host developer, I
would not want to be asked to cache a file handle. Those can
change, depending upon various types of file systems supported, and
they're not 100% reliable indicators. The AU version version
number, however, is guaranteed to be the same no matter what kind of
file system the AU is stored on. To me, it makes more sense to
cache the AU version number instead of an amorphous blob.
In any event, I think that this AU information caching is really an
implementation detail of the host application, and not something
that the AU specification requires to be handled in any particular
way. I'm sure that others can give you a more complete answer.
Brian Willoughby
Sound Consulting
On Dec 15, 2009, at 11:40, Chris Santoro wrote:
Rather than re-scanning when seeing this or that version number,
why not simply re-scan a plug-in when the component file changes?
That seems like the most logical behavior, and is what I would have
expected behavior-wise from *any* host before Brain tipped me to
the obscure version number detail.
My problem occurred because I compiled my project with the wrong
channel config *once* in the past. When I corrected the channel
configuration reporting, I would have expected Logic and AU Lab to
see the change, but neither did, because the version number was
held constant (and was not 0x0 or 0xFFFF...).
Trying to correct the issue, I had totally removed the plug-in, and
confirmed that Logic and AU Lab no longer saw it. At that point I
would have expected that component to be removed from the component
manager in the system. Why keep it around? Perhaps that's a bug? Or
is there a good reason for that?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden