Match up the exit behavior when the no-fuzz enviroment variable
is set.

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

This implements an API used in future encoders to avoid dynalloc doing silly things
on periodic LSB patterns and to reduce the bitrate on near-silence.

Timothy B. Terriberry authored 12 years ago and Gregory Maxwell committed 12 years ago

Use exact integer operations to confirm the value returned is the
 correct one.

Cyril Lashkevich authored 12 years ago and Gregory Maxwell committed 12 years ago

Signed-off-by: Gregory Maxwell <greg@xiph.org>
silk_get_TOC is unused, unreachable, and not useful without some
packet pre-processing, but until we remove it it should be correct.
This was also reported by Mozilla.

The usage of restrict in include/opus_custom.h was missed
by the prior commit replacing this keyword with a macro.

Also fixes some prototype/function agreement with respect to
restrict.

The usage of restrict in include/opus_custom.h was missed
by the prior commit replacing this keyword with a macro.

gcp authored 12 years ago and Gregory Maxwell committed 12 years ago

Add more MSVC files to .gitignore.
Make all configurations use default floating point model.

We had previously advised people to -Drestrict on
non-C99 compilers, but this creates problems for
some of the MSVC headers. Instead this just
uses a macro and defines it sanely.

When libopus is forced to sufficiently low rates it will start
outputting 'PLC' (one byte) frames. The code that did this
did not sanitize the mode well enough and would create corrupted
TOC values in some cases.

Thanks to Fatbag for pointing out the issue.

He's an author now.

Plural works better with the previous sentence. The agreement problem
was there in my original commit. I was just confused by the half
that Tim promoted.

gcp authored 12 years ago and Gregory Maxwell committed 12 years ago

Also make the 64-bit builds use the default output directories.
Fix the type of the default Opus output to be a library.

gcp authored 12 years ago and Gregory Maxwell committed 12 years ago

The (non-default) temporary & output dirs configured in the projects could
cause issues when doing compilation on a multiprocessor machine. Cleaned
this up a little to use the defaults, which makes that work again and
doesn't make the output structure any worse. Also removed debug output for
release binaries & a tiny whitespace fix.

Sort alphabetically, and move vorbis-trim to "Informative".
Also fix a misuse of "streams" instead of "channels" in the packet
 size limits exposition.

* Bump the document date.
* Mandate that the ID header must complete on the first page (to
   remove any ambiguities about this requirement in RFC 3533).
* Remove reundant wording that rillian forgot to remove in 360a4117.
* Split the "Granule Position" section into subsections.
* Move the first paragraph of the "Other Implementation Notes"
   section into the "Granule Position" section, add general seeking
   implementation guidance, and be specific about the interaction
   between pre-roll and pre-skip.
* Retitle the remaining contents of the "Other Implementation Notes"
   section to "Packet Size Limits"
* Specify that all the header fields are REQUIRED (and add a
   description of the Channel Mapping Table as a whole, so we can
   say when it is REQUIRED).
* Specify that implementations MUST NOT reject headers with extra
   data if they have an unknown minor version number.
* Add a reference to RFC 3629 (UTF-8).
* Minor formatting adjustments to vorbis-trim and vorbis-mapping
   cites.
* Eliminate semicolons and terrible "Else, if" constructs.

Remove a redundant phrase from the previous commit.
Thanks to Tim for pointing this out.

Clarify what 'skipped' means.

Give a reference for the vorbis granulepos-trimming.

Commas and semicolons in the resampling decision list.

Capital SHOULD on treating unknown channel mapping families
as discrete.

Clarify why goes in the vendor string. Maybe needs an example?
'gstoggmux 1.0.12; libopus 1.2.3'

Remove a redundant word. 'could' already covers 'potential' and
the line is stronger without it.

Hopefully it's clear from this that the demuxer can parse the
TOC sequence to verify the equal-duration constraint.