Re: crash-proof AU plugin scanning?
Re: crash-proof AU plugin scanning?
- Subject: Re: crash-proof AU plugin scanning?
- From: Brian Willoughby <email@hidden>
- Date: Wed, 30 Jun 2010 04:06:07 -0700
On Jun 30, 2010, at 01:44, Ross Bencina wrote:
Thanks for that, its a good idea. I wonder though, whether auval
has a standard output format for supported and default channel
counts etc which I could depend on even in future OS releases...
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.
Since Apple is unlikely to promise not to change the output format
for auval, I would not rely upon it. There is an official means for
obtaining the channel counts, etc., so it doesn't make sense to be
parsing textual information to get the same data.
Perhaps its not so much more work to make a separate AU-scanner
executable. Not sure how to suppress Apple crash reports if it
crashes though.
I don't think auval generates crash reports. Also, if you make a
custom AU scanner which is a Unix command-line executable like auval,
but with your own custom code, then I don't think it will generate a
crash report either. Just be sure to return your error codes via exit
(errCode); and you should be able to communicate with your AU host.
Brian Willoughby
Sound Consulting
_______________________________________________
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