W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

Re: Question about channels and merger on destination

From: Peter van der Noord <peterdunord@gmail.com>
Date: Mon, 23 Jul 2012 11:10:31 +0200
Message-ID: <CAL9tNz-XxDRSP3aEyH1FBbMur5BmKO2g+NxSZUG2n=AysQU2-Q@mail.gmail.com>
To: Alessandro Saccoia <alessandro.saccoia@gmail.com>
Cc: public-audio@w3.org
No! Hmmm, that makes my plan impossible then i guess. For the time being, I
had created a system where custom modules with more inputs or outputs would
get wrapped into a construction like this...

http://i.imgur.com/sjObQ.png

...so i would have access to those in/outs through the channels of the (js)
audionode, but if the merger and splitters behave like that i don't think
that's possible.


Peter


> it's the merger that does this. In your code, the merger has 2 inputs, but
> the number of output channels is the sum of the number of channels of the
> -- active -- inputs of the merger. input here means "connected to some
> source node", and it's consistent, since there is no way to know how many
> channels the input N has until some other node that provides an audio
> stream gets connected to itů
> So, until you don't connect some other node to the second input (input 1),
> the output will remain mono, as long as your source node for the input 0 is
> mono.
> To summarize, for a merger with 2 channels, the input/output
> configurations are:
>
> Input0          Input1          Output
> Mono       -            Mono
> Mono    Mono    Stereo
> Stereo     -            Stereo
> Stereo  Mono    3 channels
> Stereo  Stereo  4 channels
>
> and so onů (and I sincerely hope this is correct)
>
> >
>
Received on Monday, 23 July 2012 09:11:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 July 2012 09:11:03 GMT