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:36:58 +0200
Message-ID: <CAL9tNz_7WpYg9WQqkphQRXP24qACaBjRr0KCPOZL=y5VhwMV=A@mail.gmail.com>
To: Alessandro Saccoia <alessandro.saccoia@gmail.com>
Cc: public-audio@w3.org
Although the thing you mentioned, adding gain modules, would likely get
that construction to work:


I would be adding a lot of overhead nodes just for one module, but for the
time being (until jsnodes supply multiple inputs and outputs) i might stick
to this workaround.

Unless someone else has better suggestions ofcourse :)


2012/7/23 Peter van der Noord <peterdunord@gmail.com>

> 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:37:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:11 UTC