• 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: Wed, 19 Apr 2006 00:03:37 +0200

Hi Jeremy,

Am 18.04.2006 um 18:25 schrieb Jeremy Sagan:
As you can imagine, my concern is that many plug-in developers will only test with Apple Logic and therefore will expect this behavior from an AudioUnit host.
I understand your concern, but as Bill said, auval tries to detect such failures - it should catch any AU that doesn't handle this properly. Logic on the other hand relies upon auval to only run valid AUs, AUs that fail it won't show up in Logic.

Therefore IMHO, either it should be part of the AU specification or Logic should not do it.
I think I'd disagree here. I will happily fix any bug in Logic or improve it in some way or the other, but in this particular case I'd rather not put resources into re-programming (and re-testing etc) some well-working parts of Logic just to expose a potential bug in a broken AU.
Finding bugs in AUs is what Logic uses auval for, not its own source code. If there is a bug that currently goes unnoticed by auval, please let Bill know so that he can add an appropriate test case for it.


Best,
Stefan


On Apr 18, 2006, at 4:56 AM, Stefan Gretscher wrote:
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.

_______________________________________________ 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: 
 >AU state & MaximumFramesPerSlice (From: Jeremy Sagan <email@hidden>)
 >Re: AU state & MaximumFramesPerSlice (From: Stefan Gretscher <email@hidden>)
 >Re: AU state & MaximumFramesPerSlice (From: Jeremy Sagan <email@hidden>)

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