I hope.  Now that it's been clarified for me what this originally meant
to say, it's tricky to know if this actually contains the missing clue
for other readers.  Hopefully it should be obvious to anyone actually
implementing it once they look at what modes they have to choose from.

Ron's suggestion. We think it's clear enough as is and
removing it avoids confusion about this specification
versus future extensions.

This is really the best implementations can do as far as we
understand the possibilies, so it's better to be straightforward.

Mark Harris authored 11 years ago and Jean-Marc Valin committed 11 years ago

Signed-off-by: Jean-Marc Valin <jmvalin@jmvalin.ca>

Incorporate list feedback from Mark Harris, Tim and Jean-Marc
and try to improve clarity.

From http://www.ietf.org/mail-archive/web/codec/current/msg03030.html

Mark Harris authored 11 years ago and Jean-Marc Valin committed 11 years ago

Signed-off-by: Jean-Marc Valin <jmvalin@jmvalin.ca>

We released 1.1 with 1.1-beta as the hard-coded version.
Hopefully this only affects people doing their own windows builds
 without the git tools available.
Thanks to Ron Lee for the report.

If there's no complete author tag, we need to add an opening
quote character manually. See the EBU entry.

The normative reference is now the channel configurations
give directly in the draft.

Previous markup was invalid.

I've done some editing for clarity, but more needs to be done.
The language needs clean-up, we should forward-reference the LPC
Extrapolation section, and we need a reference for actually
computing linear prediction coefficients.

More recent versions of draft-sheffer-running-code suggest referring
to a wiki. We'd like to try maintaining the implementation status
separately.

Ralph Giles authored 11 years ago and Jean-Marc Valin committed 11 years ago

Release date based on directory timestamps in
https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/20.0/

The channel mapping family nested lists were hard to read.
Promoting each family description to a subsection makes it
more clear where one is in the document.

Also add suggested downmix matricies. These are what we're
currently using in opus-tools, opusfile, and Firefox.
Ascii-art matrices in 69 columns is hard.

With xml2rfc 2.3.9, I was getting the 'audio/ogg; codecs=opus'
figure hoisted out of the the containing paragraph, which was
very confusing.

I've tried to improve this by moving the surrounding paragraph
into the figure using the <preamble> and <postamble> tags, as
in the example in draft-mrose-writting-rfcs.

Unfortunately this still isn't perfect. Since the surrounding
paragraph is part of the figure we can't set align="center" on
the figure itself, and the processor seems to ignore it on the
artwork element. I've compensated by adding some leading
whitespace.

Mostly just being more verbose.

This clarifies the meaning in surround configurations and better
distinguishes it from 'rear center'.