Should slightly improve coverage and reduce code size

This avoids a warning about obsolete AM_CONFIG_HEADERS() on more
recent autoconf. The new macro has been around at least since
autoconf 2.60. So this should be safe.

quant_band() now only handles the level0 case.

Fixes an MSVC double truncation warning.

This fixes a truncation warning in MSVC:

warning C4305: 'initializing' : truncation from 'double' to
'const opus_val16'.

opus_val16 is a float in the floating point build and an
int16 in the fixed-point build. The table isn't used in
the fixed-point build, but the compiler would presumedly
warn in that case as well.

Also fixes an issue with 40- and 60-ms frames using the repacketizer.

Can now work up to full-band and uses lsb_depth to fix the noise issue.

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

The command line has changed, for the better, but we need to
update the way we call it. Also adds an install hint if it's
not found on the path.

NB I tried to detect and fallback to the old syntax for the
version 1 (TCL) implementation but this is hard because it
doesn't support any switches (like --version) and it no
longer parses our remote entities.

The max reduction now depends on intensity threshold too.

Some tests like Kamedo's HA test suggested that our tonal boost was a bit
too extreme.

NB they only check for len < 1, not for null data.

This should reduce computation, reduce stack usage, and be
 substantially easier to read, but should not change behavior.
It's not quite bit-exact because I collapsed the application of the
 decay and the fading into a single pass to save one multiply per
 sample, but the difference signal is silent.

It also changes the comments into complete sentences.

Gregory Maxwell authored 12 years ago and Jean-Marc Valin committed 12 years ago

Also remove a useless extern that crept into the tests from some
optimization driven testcase generation.

Calling PLC/FEC with a different size was not updating it

Library soname versioning is something we normally change
only right before each release. However, with 1.0.2 being
released from the 1.0.x branch with 3.0.3, it makes sense
to make the same update here. That way when we do a new
release from master we can just increment again and have
the version properly reflect ranges relative to the stable
branch.

This applies in addition to the earlier grant made by
Skype, which was purchased by Microsoft.