• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Delivering MIDI causing crashes in some AUs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Delivering MIDI causing crashes in some AUs


  • Subject: Re: Delivering MIDI causing crashes in some AUs
  • From: Robert Grant <email@hidden>
  • Date: Fri, 8 Oct 2004 15:38:22 -0400

Well thanks for the all the advice.

I guess I'm going to hold off on doing anything for a bit longer to see if Logic 7 gets things sorted quickly.

I'll reassess in a few of weeks - and if necessary go with the known-bad list (with all the tweaks that have been suggested).

Thanks again,

Robert.

On Oct 7, 2004, at 9:16 PM, Brian Willoughby wrote:

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
References: 
 >Delivering MIDI causing crashes in some AUs (From: Robert Grant <email@hidden>)
 >Re: Delivering MIDI causing crashes in some AUs (From: Robert Grant <email@hidden>)
 >Re: Delivering MIDI causing crashes in some AUs (From: Marc Poirier <email@hidden>)
 >Re: Delivering MIDI causing crashes in some AUs (From: Brian Willoughby <email@hidden>)

  • Prev by Date: Re: [OT] List of AU Hosts
  • Next by Date: AudioFileGetProperty() reportes wrong format?!?
  • Previous by thread: Re: Delivering MIDI causing crashes in some AUs
  • Next by thread: Who is calling my MIDIReadProc?
  • Index(es):
    • Date
    • Thread