Re: crash-proof AU plugin scanning?
Re: crash-proof AU plugin scanning?
- Subject: Re: crash-proof AU plugin scanning?
- From: "Ross Bencina" <email@hidden>
- Date: Fri, 2 Jul 2010 00:03:44 +1000
"Brian Willoughby" <email@hidden> wrote:
Why do you want the channel counts, etc., for AudioUnits that are
crashing? Seems like all you need the separate process for is to
distinguish crashing from non-crashing AUs. If they don't crash, then
load them into your host and get the channel counts, etc., through the
direct means that Apple intends for you to use. If a particular AU does
crash, then just put it on a list of AUs to avoid, and then it really
doesn't matter how many channels it supports.
Because it might work fine in auval and still crash in my host and I can't
afford that risk. Infact that's the most likely scenario, since they
probably won't crash in auval if the developer has tested in auval.
The main point of scanning in a separate process is that it won't take down
the host at startup -- and the best way to do that is avoid loading any
foreign code into the address space at all.
Since Apple is unlikely to promise not to change the output format for
auval, I would not rely upon it.
Yeah, fair enough.
Thanks
Ross.
_______________________________________________
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