Re: AUVal Source Code
Re: AUVal Source Code
- Subject: Re: AUVal Source Code
- From: Brian Willoughby <email@hidden>
- Date: Sun, 30 Oct 2011 17:16:12 -0700
It is not possible to test, via automated code, every part of the AU
specification. Therefore, it is impossible for auval and the AU spec
to be identical. By necessity, auval tests for a subset of the
requirements of AudioUnits, and it is even further limited by the
fact that it has to test all AudioUnits.
In the middle ground, it might be possible to create automated test
code for a specific AU, but only the developer of that AU could
create such tests.
Basically, auval should be seen as a low-cost but only partial test
of any AU. At a minimum, every AU that ships should pass auval. But
beyond that there is a great deal of additional testing that should
be done. There is also a necessary degree of human interpretation
needed to judge whether a specific AU meets Apple's specifications.
What you suggest would be quite nice if it were possible, but it
simply isn't possible to automate 100% of the compliance testing.
Brian Willoughby
Sound Consulting
On Oct 29, 2011, at 16:53, Chris Santoro wrote:
Sure, but shouldn't auval and the au spec be one in the same?
On Sat, Oct 29, 2011 at 5:36 PM, Kyle Sluder
<email@hidden> wrote:
On Sat, Oct 29, 2011 at 6:40 AM, Chris Santoro
<email@hidden> wrote:
> And if it can't be released, that's fine, but could someone
explain why? I
> just think it would be a great help to the many devs out there.
I think the AUVal developers would rather people program to the spec
than the AUVal implementation.
_______________________________________________
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