Re: Delivering MIDI causing crashes in some AUs
Re: Delivering MIDI causing crashes in some AUs
- Subject: Re: Delivering MIDI causing crashes in some AUs
- From: Brian Willoughby <email@hidden>
- Date: Thu, 7 Oct 2004 18:16:51 -0700
I don't think it would be so difficult to manage a known-bad AU list if you
include the AU version number along with the plug-in name. If a new version of
a troublesome plug-in comes out, the known-bad list would not prematurely
exclude the plug-in. Of course, some AU vendors, particularly those who are
having trouble passing auval, may also not understand how to properly increment
the version number. But that should be rare.
Brian Willoughby
Sound Consulting
Begin forwarded message:
On Oct 7, 2004, at 6:11 PM, Robert Grant wrote:
> So I guess for all us non-Apple hosts we need to come up with an
> alternative solution but I don't feel like re-writing AUValidation.
>
> An XML file of known-bad AUs might be one way to do it. Be faster to
> start up too. It would also allow us to let in some less-than perfect
> members. And by going with the Bad AUs it would (hopefully) be a much
> shorter list!
[ I would consider this very carefully. The big potential problem with
[ blacklisting an AU is that then the developer updates it, fixes the
[ problems, and the user of your app is stuck with an app that is still
[ blacklisting the AU with no recourse for the user to fix the situation.
[ It means that you have to stay on top of every new AU update, forever.
_______________________________________________
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