• 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: AUView opening before initialzation BIG HASSLE!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AUView opening before initialzation BIG HASSLE!


  • Subject: Re: AUView opening before initialzation BIG HASSLE!
  • From: Marc Poirier <email@hidden>
  • Date: Mon, 8 Sep 2003 22:20:10 -0500 (CDT)

On Mon, 8 Sep 2003, Angus F. Hewlett wrote:

> Can you not just call Initialize() (or better, an internal initialize
> method) from your plug when you run in to a problem? That's what I do in
> VST-AU:- if it is possible for it to complete a call without
> Initialize()ing, it does so, but if it has to intialize those things, it
> does that instead. Equally, in the view class, I don't instantiate anything
> big until I need to create and display the view.

Are you sure it's okay for the plugin to Initialize itself without the
host knowing? I thought that it was only up to the host to do that. And
then the host will surely Initialize you and you will already be
Initialized, and then what would the correct behavior be?

> The downside of this approach is that it makes host load times a bit
> unpredictable... depending on what the host asks for when scanning plugins,
> it may take a couple of ms per AU or a few hundred ms (many VST plugins are
> slow to load). I could improve performance some more by caching more
> information than I currently do (the output configuration is cached; the
> audio I/O properties are cached; the parameter table is not).

In my opinion, this is not something that you should have to worry about,
but a shortcoming of the host when the host is rescanning that information
for every AU during every launch. If a host needs some info about every
AU during launch time, then it should be up to that host to query the info
about newly encountered AUs and then cache any required info for itself
(and refresh that when a "known" AU's version value changes). Just my
opinion, but I really don't think that that burden should be yours, and
moreover if you make workarounds for your stuff, it's still a problem with
other AUs.

Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: AUView opening before initialzation BIG HASSLE! (From: "Angus F. Hewlett" <email@hidden>)

  • Prev by Date: Re: Drawing an EQ curve
  • Next by Date: Re: AUView opening before initialzation BIG HASSLE!
  • Previous by thread: AU Manifesto (was Re: AUView opening before initialzation BIG HASSLE!)
  • Next by thread: Re: AUView opening before initialzation BIG HASSLE!
  • Index(es):
    • Date
    • Thread