Re: Clarification with regard to AudioNode.numberOfInputs and AudioNode.numberOfOutputs

On Tue, Oct 2, 2012 at 1:46 PM, Ehsan Akhgari <ehsan.akhgari@gmail.com>wrote:

> Yes, those are precisely what I'm talking about.  So if I understand
> things correctly, numberOfInputs and numberOfOutputs should return the
> maximum number of inputs/outputs that the node accepts.  If that's the
> case, I can submit a patch to fix the spec to mention this explicitly.
>

That sounds fine to me if you think the current wording is unclear.  But,
right now I think it's already explicit:

For example, right now, in the AudioChannelSplitter description it states:

"
There are always a total number of N outputs (determined by the
numberOfOutputs parameter to the AudioContext method createChannelSplitter()
"

I guess the AudioChannelMerger section could include something similarly
explicit.


>
> Cheers,
> --
> Ehsan
> <http://ehsanakhgari.org/>
>
>
>
> On Tue, Oct 2, 2012 at 4:35 PM, Chris Rogers <crogers@google.com> wrote:
>
>>
>>
>> On Tue, Oct 2, 2012 at 1:06 PM, Ehsan Akhgari <ehsan.akhgari@gmail.com>wrote:
>>
>>> Hi all,
>>>
>>> Let's imagine that a given AudioNode supports up to N inputs.  What
>>> should the numberOfInputs attribute return if the node has M inputs (M <=
>>> N) bound to it?  Specifically, the relationship between which slots in the
>>> node's inputs are connected and which whether numberOfInputs should only
>>> count those is not clear in the current spec.  And the equivalent question
>>> is applicable to numberOfOutputs.
>>>
>>> Thanks!
>>> --
>>> Ehsan
>>> <http://ehsanakhgari.org/>
>>>
>>
>> Hi Ehsan, I'm guessing you're thinking of AudioChannelSplitter and
>> AudioChannelMerger?  These nodes are created with a specific number of
>> inputs/outputs.  Whether or not they are connected should not reflect the
>> values reported in .numberOfInputs or .numberOfOutputs
>>
>> Chris
>>
>>
>