Apple

On Thu, Jan 14, 2016 at 9:59 AM, Paul Sanders <email@hidden> wrote:

Hah! Spoken from the heart, clearly a man who's sufferred. I hope it gets you somewhere.

Soon I will be hosting these too. Sounds like there might be some white water ahead, but thanks for the heads-up. If the plugin crashes, I guess you go down too, nothing to be done about it. Yuk.

Apart from this rather thorny issue, is there very much to it? I've not looked into it at all so far so I know nothing about it, but I thought I might at least take the opportunity to ask you, since you're here. Everyone knows that you're well informed on this, so any titbits you can pass my way would be appreciated. Perhaps by others, too.

I know Cocoa, and I know what I believe to be the relevant bits of Core Audio (I'm pulling and pushing audio via AUHal - AudioOutputUnitStart, AudioOutputUnitStop, blah blah blah), so I probably already have 90% of what I need. I probably just need to know how to enumerate, load, initialise, chain and configure them, something like that. It's probably all in the docs, but Apple always say that, and, somehow, it never quite is.

Thx.

Paul Sanders.

On 14/01/2016 14:03, Paul Davis wrote:

This is a tiny rant.

If you're a plugin developer, you probably know about auval, Apple' s own AudioUnit validation tool.

If you're a plugin developer, do you consider it your responsibility to ensure that your plugin can pass auval's validation process? Or do you just say "It works with <insert-name-of-various-DAWs>" ?

If you're a plugin developer, and a user shows you auval crashing when attempting to use your plugin, do you pay attention?

If you're a plugin developer, and the developers of another host report specific erratic behaviour that looks a lot like an uninitialized global variable, do you pay attention?

Most of you AU plugin developers have the right answers to these questions. But it would be nice if *everyone* did. I don't know what Apple's official position is on whether or not auval is the canonical testbed for an AU, but it certainly seems as if that ought to be the case.

If you're from Apple, can you comment on the status of auval as the canonical test tool? Does Logic still use auval for its own evaluation?

References:
	>plugin developers responsibilities (From: Paul Davis <email@hidden>)
	>Re: plugin developers responsibilities (From: Paul Sanders <email@hidden>)