• 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: Bill Stewart <email@hidden>
  • Date: Tue, 9 Sep 2003 14:32:12 -0700

On Tuesday, September 9, 2003, at 02:31 AM, Jean-Alexis Montignies wrote:

One of the Apple representatives on the list (Bill, I think) stated that AU
open times to get basic properties should be kept as low as possible, in
the tens of ms. Because of the nature of VST plug-ins (generally
monolithic) and the way VST-AU's loader works (initialize as much as
possible as early as possible, so crappily coded VSTs are less likely to
crash when we ask them questions later), and also because of the way
people tend to hoard those plugs, it makes sense for me to avoid going
through the load sequence at all unless I absolutely have to.

It sounds more logical to handle the shortcomings of the VST format would be
better handled in VST-AU.
VST-AU could cache the required informations the first time a VST plug-in is
loaded.

Now if each host decides to cache those things its own way, prepare for some
headackes.

Hosts can and do cache information about AU's - any problems are going to be created by AU developers going outside of the AU guidelines... Remember, the host can only know what it can know about an AU through public API. Thus, much of the internal state of an AU is transparent to the host (ie. num parameters, their "current" values, the contract that those values don't change in arbitrary ways, that these are preserved across reset and initialization)... That "previous" versions of the class info dictionary you publish will still be readable by new versions of your AU, etc...

The Component Versioning is also an important consideration to indicate to a host that the AU has been revised, and should be re-assessed.

Bill


Jean-Alexis
_______________________________________________
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.


-- mailto:email@hidden
tel: +1 408 974 4056

________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __
_______________________________________________
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: "Jean-Alexis Montignies" <email@hidden>)

  • Prev by Date: Re: kAudioUnitProperty_MaximumFramesPerSlice
  • Next by Date: everyone having fun with the Digidesign CoreAudio drivers?
  • Previous by thread: Re: AUView opening before initialzation BIG HASSLE!
  • Next by thread: AudioUnitRender >= 2048 Problem
  • Index(es):
    • Date
    • Thread