[opus] Channel Mapping Family for Ambisonics

Jean-Marc Valin jmvalin at jmvalin.ca
Tue Apr 19 19:25:23 UTC 2016

On 04/19/2016 03:17 PM, Timothy B. Terriberry wrote:
> Michael Graczyk wrote:
>> That makes sense. For now I will focus on encoder only changes. If an
>> adaptive pre/post transform had to send side information, would it
>> also need to go through the IETF process?
> The IANA registry for channel mappings has a policy of "specification
> required", but not "RFC required", so it is possible to specify
> something without going through the full IETF process. Still, if this is
> something you expect to be used outside of Google properties (and it
> sounds like it is), I think going through the IETF process would be a
> good idea (even though that means more work for me).

Well, keep in mind that the side information has to go somewhere too. If
that information goes into the padding, then we'd need an RFC that
updates the Opus RFC. If it goes into Ogg directly, then we may need an
RFC to update the Ogg Opus RFC.


More information about the opus mailing list