• 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: AU state & MaximumFramesPerSlice
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU state & MaximumFramesPerSlice


  • Subject: Re: AU state & MaximumFramesPerSlice
  • From: Stefan Gretscher <email@hidden>
  • Date: Tue, 18 Apr 2006 10:56:09 +0200

Hi Jeremy,

Am 17.04.2006 um 18:28 schrieb Jeremy Sagan:
So, Apple, is this part of the AU specification? Does a host have to save and restore the plug-ins state simply because the sample rate or frame size changes?
As Bill already wrote, you do not have to do this for AUs.
The Logic engine does it because it does handle other plug-in formats as well (e.g. TDM and our built-in plug-ins) and in some of these formats it's necessary to do this. The generic plug-in handling layer doesn't know what particular format a given plug-in has, so it tears them all down, even if it wouldn't have to do so for AUs.


Best,
Stefan

_______________________________________________
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


  • Follow-Ups:
    • Re: AU state & MaximumFramesPerSlice
      • From: Jeremy Sagan <email@hidden>
References: 
 >AU state & MaximumFramesPerSlice (From: Jeremy Sagan <email@hidden>)

  • Prev by Date: A few more questions on QT-CA data transfers, and spontaneous AU uninitialization
  • Next by Date: siCompressionParams Question
  • Previous by thread: Re: AU state & MaximumFramesPerSlice
  • Next by thread: Re: AU state & MaximumFramesPerSlice
  • Index(es):
    • Date
    • Thread