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: Marc Poirier <email@hidden>
- Date: Thu, 7 Oct 2004 18:38:12 -0400
On Oct 7, 2004, at 6:11 PM, Robert Grant wrote:
OK - I spoke too soon (perhaps I've been talking to myself so it
doesn't matter!). After re-reading the license agreement I find that I
can't redistribute AUValidation!
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.
I dunno - it's all a bit depressing...
Hmmm, I'm not sure that it's so bad, or that you have to do so much
work. The nice thing about Logic being the first app to enforce auval
is that it's a rather popular app with a lot of sway in the AU world.
My prediction is that we are going to see every AU passing auval by the
end of the month. Some folks may have not been able to get that
happening by Logic 7's release date, but they know and I doubt that
there is any AU maker who hasn't fixed their stuff yet who is not
working on it and close to being ready. Also, I doubt that we will
ever see another new AU arrive that does not pass auval. I mean, who
in their right mind is going to release a new AU that, from day 1, is
unusable in Logic (and potentially other apps)? So in other words,
what I'm saying is that I think that Logic does this is enough and that
every other host developer is going to gain from this, gain in that
they are not going to have to be the ones to do this but the AU
conformance situation will, as a result, improve greatly so that host
developers will no longer need to think about workarounds for and
blacklisting of wonky AUs. I could be wrong, of course, but this is
what I imagine will be the case very soon...
Marc
_______________________________________________
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