Re: Overriding SupportedNumChannels
Re: Overriding SupportedNumChannels
- Subject: Re: Overriding SupportedNumChannels
- From: William Stewart <email@hidden>
- Date: Tue, 29 Jun 2010 19:39:32 -0700
Yes, I understand, but I wanted to refine the assertion that it does actually work, and that the problem seems to be in the reporting/cacheing side of it, rather than not being able to do it a priori.
Bill
On Jun 29, 2010, at 6:26 PM, Brian Willoughby wrote:
>
> On Jun 29, 2010, at 18:18, William Stewart wrote:
>> On Jun 29, 2010, at 1:55 PM, Alex Weiss wrote:
>>> I think I found the culprit. First of all, it seems that AULab expects
>>> the same number of input and output channels.
>>
>> No. I just tried adding a 1->2 AUMatrxiReverb and that works fine.
>
>
> I believe what Alex is saying is that the AU must advertise that it is capable of supporting the same number of input and output channels. In other words, AUMatrixReverb certainly supports 2->2, so it's not the same test if AULab can instantiate AUMatrixReverb. In Alex's case, his algorithm does not translate well to 2->2 or 8->8, so he's leaving those options entirely out of the advertised support. As Alex mentioned, adding 8->8 caused his AU to appear in AULab, so it seems clear that AUMatrixReverb appears because it supports 2->2, even if you're only using 1->2 in your specific case.
>
> Brian Willoughby
> Sound Consulting
>
_______________________________________________
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