- From: Chris Rogers <crogers@google.com>
- Date: Wed, 13 Feb 2013 18:02:29 -0800
- To: robert@ocallahan.org
- Cc: public-audio@w3.org
- Message-ID: <CA+EzO0kJN+PuCWur1dXynKvfws1VFZdQTj1DrcBi5JjvVzFYjA@mail.gmail.com>
On Wed, Feb 13, 2013 at 5:58 PM, Robert O'Callahan <robert@ocallahan.org>wrote: > Thanks. The basic approach sounds reasonable. I think instead of that > setInputMixingMode method, it might be simpler to have ChannelCountMode and > ChannelInterpretation and numberOfChannels be attributes on the node? Is > there a need to have different interpretations per input port? Since only > ChannelMergerNodes have more than one input port, I wouldn't have thought > so... > Robert, thanks for having such a quick look. Yes, it may be possible to do as you suggest. I'd considered the attributes, but thought it might be nice to be able to set these values for a specific input. I don't have any specific use case where that would be necessary, but thought it might scale better if we added nodes in the future where it potentially might make a difference. Chris > > Thanks, > Rob > -- > Wrfhf pnyyrq gurz gbtrgure naq fnvq, “Lbh xabj gung gur ehyref bs gur > Tragvyrf ybeq vg bire gurz, naq gurve uvtu bssvpvnyf rkrepvfr nhgubevgl > bire gurz. Abg fb jvgu lbh. Vafgrnq, jubrire jnagf gb orpbzr terng nzbat > lbh zhfg or lbhe freinag, naq jubrire jnagf gb or svefg zhfg or lbhe fynir > — whfg nf gur Fba bs Zna qvq abg pbzr gb or freirq, ohg gb freir, naq gb > tvir uvf yvsr nf n enafbz sbe znal.” [Znggurj 20:25-28] >
Received on Thursday, 14 February 2013 02:02:56 UTC