- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 28 May 2013 13:11:13 +1200
- To: Chris Rogers <crogers@google.com>
- Cc: Paul Adenot <paul@paul.cx>, "public-audio@w3.org" <public-audio@w3.org>
Received on Tuesday, 28 May 2013 01:11:43 UTC
The last time maxChannelCount and multichannel output came up, I suggested that AudioDestinationNode should default channelCountMode to 'max' instead of 'explicit', so many users of Web Audio would not need to use maxChannelCount at all --- they could just produce as many channels as they want, and the Web Audio implementation would downmix (or upmix) to the actual speaker configuration. (Especially convenient when the speaker configuration changes over time.) I don't recall any replies to that suggestion. I still like it :-). If we do that, it's still useful to expose maxChannelCount on AudioDestinationNode --- it lets advanced users customize the audio graph to the number of speakers. However, I don't think we need maxChannelCount on MediaStreamDestinationAudioNode. What would it even mean? I don't think we can detect the number of speakers a MediaStream is feeding into --- it could be feeding into many sinks, or none, or into a sink like a MediaRecorder that can handle any number of channels equally well. Rob -- q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
Received on Tuesday, 28 May 2013 01:11:43 UTC