Skip to content
GitLab
Menu
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Tim-Philipp Müller
Opus
Commits
699b6430
Commit
699b6430
authored
Oct 23, 2015
by
Mark Harris
Committed by
Jean-Marc Valin
Oct 23, 2015
Browse files
Updating links for both https and new versions
Signed-off-by:
Jean-Marc Valin
<
jmvalin@jmvalin.ca
>
parent
d70b8ed6
Changes
3
Hide whitespace changes
Inline
Side-by-side
README
View file @
699b6430
...
...
@@ -13,14 +13,14 @@ soundtracks, portable music players, jukeboxes, and other applications that
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
http
s
://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.
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
http
s
://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 @@ additional debugging data and cannot support seeking.
Opus stored in files should use the Ogg encapsulation for Opus which is
described at:
http://wiki.xiph.org/OggOpus
http
s
://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 @@ Ogg encapsulated Opus files and includes a number of useful features.
Opus-tools can be found at:
https://git.xiph.org/?p=opus-tools.git
or on the main Opus website:
http://opus-codec.org/
http
s
://opus-codec.org/
== Compiling libopus ==
...
...
@@ -50,7 +50,7 @@ To build from the git repository, the following steps are necessary:
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 @@ To run the integrated tests:
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
http
s
://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 http
s
://opus-codec.org/testvectors/opus_testvectors.tar.gz
% tar -zxf opus_testvectors.tar.gz
% ./tests/run_vectors.sh ./ opus_testvectors 48000
...
...
README.draft
View file @
699b6430
...
...
@@ -7,8 +7,8 @@ If this does not work, or if you want to change the default configuration
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:
http
s
://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 @@ steps:
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
...
...
include/opus_multistream.h
View file @
699b6430
...
...
@@ -111,9 +111,9 @@ extern "C" {
* 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="http
s
://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="http
s
://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 @@ extern "C" {
*
* The output channels specified by the encoder
* should use the
* <a href="http://www.xiph.org/vorbis/doc/Vorbis_I_spec.html#x1-8
0
0004.3.9">Vorbis
* <a href="http
s
://www.xiph.org/vorbis/doc/Vorbis_I_spec.html#x1-8
1
0004.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).
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment