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?
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
