shithub: opus

--- a/README

+++ b/README

@@ -13,7 +13,7 @@

 have historically used high latency formats such as MP3, AAC, or Vorbis.

                     Opus is specified by IETF RFC 6716:

-                    http://tools.ietf.org/html/rfc6716

+                    https://tools.ietf.org/html/rfc6716

   The Opus format and this implementation of it are subject to the royalty-

 free patent and copyright licenses specified in the file COPYING.

@@ -20,7 +20,7 @@

 This package implements a shared library for encoding and decoding raw Opus

 bitstreams. Raw Opus bitstreams should be used over RTP according to

- http://tools.ietf.org/html/draft-spittka-payload-rtp-opus

+ https://tools.ietf.org/html/rfc7587

 The package also includes a number of test  tools used for testing the

 correct operation of the library. The bitstreams read/written by these

@@ -29,7 +29,7 @@

 Opus stored in files should use the Ogg encapsulation for Opus which is

 described at:

- http://wiki.xiph.org/OggOpus

+ https://wiki.xiph.org/OggOpus

 An opus-tools package is available which provides encoding and decoding of

 Ogg encapsulated Opus files and includes a number of useful features.

@@ -37,7 +37,7 @@

 Opus-tools can be found at:

  https://git.xiph.org/?p=opus-tools.git

 or on the main Opus website:

- http://opus-codec.org/

+ https://opus-codec.org/

 == Compiling libopus ==

@@ -50,7 +50,7 @@

 1) Clone the repository:

-% git clone git://git.opus-codec.org/opus.git

+% git clone https://git.xiph.org/opus.git

 % cd opus

 2) Compiling the source

@@ -106,11 +106,11 @@

 There is also collection of standard test vectors which are not

 included in this package for size reasons but can be obtained from:

-http://opus-codec.org/testvectors/opus_testvectors.tar.gz

+https://opus-codec.org/testvectors/opus_testvectors.tar.gz

 To run compare the code to these test vectors:

-% curl -O http://opus-codec.org/testvectors/opus_testvectors.tar.gz

+% curl -O https://opus-codec.org/testvectors/opus_testvectors.tar.gz

 % tar -zxf opus_testvectors.tar.gz

 % ./tests/run_vectors.sh ./ opus_testvectors 48000

--- a/README.draft

+++ b/README.draft

@@ -7,8 +7,8 @@

 in the Makefile.

 An up-to-date implementation conforming to this standard is available in a

-Git repository at git://git.xiph.org/opus.git or on a website at:

-http://opus-codec.org/

+Git repository at https://git.xiph.org/opus.git or on a website at:

+https://opus-codec.org/

 However, although that implementation is expected to remain conformant

 with the standard, it is the code in this RFC that shall remain normative.

 To build from the git repository instead of using this RFC, follow these

@@ -17,7 +17,7 @@

 1) Clone the repository (latest implementation of this standard at the time

 of publication)

-% git clone git://git.opus-codec.org/opus.git

+% git clone https://git.xiph.org/opus.git

 % cd opus

 2) Compile

--- a/include/opus_multistream.h

+++ b/include/opus_multistream.h

@@ -111,9 +111,9 @@

   * duration, can be computed without any special negotiation.

   * The format for multistream Opus packets is defined in the

-  * <a href="http://tools.ietf.org/html/draft-terriberry-oggopus">Ogg

+  * <a href="https://tools.ietf.org/html/draft-ietf-codec-oggopus">Ogg

   * encapsulation specification</a> and is based on the self-delimited Opus

-  * framing described in Appendix B of <a href="http://tools.ietf.org/html/rfc6716">RFC 6716</a>.

+  * framing described in Appendix B of <a href="https://tools.ietf.org/html/rfc6716">RFC 6716</a>.

   * Normal Opus packets are just a degenerate case of multistream Opus packets,

   * and can be encoded or decoded with the multistream API by setting

   * <code>streams</code> to <code>1</code> when initializing the encoder or

@@ -140,7 +140,7 @@

   * The output channels specified by the encoder

   * should use the

-  * <a href="http://www.xiph.org/vorbis/doc/Vorbis_I_spec.html#x1-800004.3.9">Vorbis

+  * <a href="https://www.xiph.org/vorbis/doc/Vorbis_I_spec.html#x1-810004.3.9">Vorbis

   * channel ordering</a>. A decoder may wish to apply an additional permutation

   * to the mapping the encoder used to achieve a different output channel

   * order (e.g. for outputing in WAV order).