Re: [codec] possible issues to track

["Benjamin M. Schwartz" <[e-mail]>]

Benjamin M. Schwartz wrote:
> 1. The codec should provide an interface for coding a pair of closely
> coupled channels with the presumption that they represent something like a
> stereo pair.
> 
> 2.  The format should provide an efficient way to pack multiple
> independent synchronized codec channels into a single stream.
> 
> 3. The format should provide a way to specify N named output channels as
> linear combinations of the coded channels.

On closer inspection, I think (3) is best left out of this work for now.
Instead, channels should be named according to their significance.
Applications that perform complex manipulations on the channels, such as
arbitrary mixing, can select appropriate names for their coded channels.
This is the approach taken in the CELT RTP encapsulation draft [1]

Positioning of speakers in multi-party conference streams should be
performed by the client in accordance with its user interface.

--Ben

[1] http://tools.ietf.org/html/draft-valin-celt-rtp-profile-02#page-13