Re: buggy AUMatrixReverb, reaper ??
Re: buggy AUMatrixReverb, reaper ??
- Subject: Re: buggy AUMatrixReverb, reaper ??
- From: Paul Davis <email@hidden>
- Date: Tue, 1 Dec 2009 18:45:33 -0500
On Tue, Dec 1, 2009 at 5:32 PM, James McCartney <email@hidden> wrote:
>
> On Dec 1, 2009, at 6:57 AM, Paul Davis wrote:
>
>> Just noticed that Reaper's 3.1415 release includes this detail:
>>
>> OSX: Audio Unit buggy compatibility mode includes constant blocksize
>> (fixes AUMatrixReverb)
>>
>> Does anybody know what this is about, since this plugin fairly
>> regularly crashes Ardour too.
>
> Did you file a bug report?
>
>> Google didn't reveal anything of value,
>> and presumably it passes the AULab validation tests anyway.
We have made a policy of not filing bug reports against AU plugins
that pass the AULab validation suite, because we believe that the
problem lies in our hosting code. When a plugin runs correctly in at
least 3 other DAWs it seems reasonable to conclude that we goofed. In
this case, I've never run the test mostly because I tend to believe
that if you guys released it, you tested it. Am I wrong? :)
However, I was just intrigued by the comment in the Reaper release
notes. I have been unable to find out anymore about the issue that
they claim to have worked around.
BTW, the "inverse" of the AULab validation stuff - a plugin that tests
host compliance - would be pretty cool. I know, for example, that the
way Ardour delivers carbon events to AU Carbon views is quite
different from other hosts and negatively impacts plugins from quite a
few manufacturers. Sophie Poirier at DestroyFX was kind enough to give
me event traces from Ardour and 2 other DAWs to show this.
--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