Re: Audio Unit ioConfigs (Resolved)
Re: Audio Unit ioConfigs (Resolved)
- Subject: Re: Audio Unit ioConfigs (Resolved)
- From: Paul Davis <email@hidden>
- Date: Mon, 14 Dec 2009 21:56:37 -0500
On Mon, Dec 14, 2009 at 9:01 PM, Brian Willoughby <email@hidden> wrote:
> Chris,
> You can avoid this situation by changing the version number of your AU
> whenever you change it's interface to AU hosts. For public releases, a
> version number change is absolutely necessary. For development purposes on
> your private machine, you can use version 0.0.0 to force compliant AU hosts
a quick google only seems to mention this behaviour in a document
called "Optimizing Audio Unit User Experience in Logic Studio". Hardly
where I'd go expect a definition of "compliant AU hosts", but hey,
i've missed stuff before. Is this behaviour described anywhere else?
Is the behaviour of Logic Studio considered to be the definition of a
compliant host, or is this actually mapped out in a document that is
independent of a particular application? is the format of the cache
defined and documented anywhere, or is it considered to be solely for
the use of Logic, Soundtrack Pro 2, MainStage, and WaveBurner?
--p
_______________________________________________
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