- From: olivier Thereaux <olivier.thereaux@bbc.co.uk>
- Date: Mon, 21 May 2012 14:29:02 +0100
- To: Audio Working Group <public-audio@w3.org>
On 18 May 2012, at 15:19, Audio Working Group Issue Tracker wrote: > Audio-ISSUE-95 (ChannelLayouts): Channel Layouts are not sufficiently defined [Web Audio API] > > http://www.w3.org/2011/audio/track/issues/95 > > Raised by: Philip Jägenstedt > On product: Web Audio API > > https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#ChannelLayouts > > This section admits that "Other layouts can also be considered." It should be defined exactly which channel configurations must be supported. We discussed the question of channel handling in the recent past, as part of our handling of ISSUE-9 http://www.w3.org/2011/audio/track/issues/9 http://www.w3.org/2012/04/25-audio-minutes#item02 http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0077.html http://www.w3.org/2012/05/02-audio-minutes.html#item06 My understanding of the consensus so far was that: * The API should support and (by default) match the channel configuration specified by the hardware * The spec should not constrain the channel support to "typical" contemporary layouts I guess this leaves us with two questions: - Should we normatively specify the channel ordering/naming for typical layouts - How can we ensure interoperability between implementation in their naming/ordering of channels in atypical layouts (say, a 100-speaker concert configuration) Olivier
Received on Monday, 21 May 2012 13:29:46 UTC