Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
Opus
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Alexander Traud
Opus
Commits
15f0f1f3
Commit
15f0f1f3
authored
12 years ago
by
Jean-Marc Valin
Browse files
Options
Downloads
Patches
Plain Diff
Addressing some of Tina's comments on the RTP draft
parent
799b1700
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/draft-spittka-payload-rtp-opus.xml
+15
-15
15 additions, 15 deletions
doc/draft-spittka-payload-rtp-opus.xml
with
15 additions
and
15 deletions
doc/draft-spittka-payload-rtp-opus.xml
+
15
−
15
View file @
15f0f1f3
...
@@ -88,7 +88,7 @@
...
@@ -88,7 +88,7 @@
<t>
<t>
The Opus codec is a speech and audio codec developed within the
The Opus codec is a speech and audio codec developed within the
IETF Internet Wideband Audio Codec working group (codec). The codec
IETF Internet Wideband Audio Codec working group (codec). The codec
has a very low algorithmic delay and i
s
has a very low algorithmic delay and i
t
is highly scalable in terms of audio bandwidth, bitrate, and
is highly scalable in terms of audio bandwidth, bitrate, and
complexity. Further, it provides different modes to efficiently encode speech signals
complexity. Further, it provides different modes to efficiently encode speech signals
as well as music signals, thus, making it the codec of choice for
as well as music signals, thus, making it the codec of choice for
...
@@ -111,11 +111,14 @@
...
@@ -111,11 +111,14 @@
document are to be interpreted as described in
<xref
target=
"RFC2119"
/>
.
</t>
document are to be interpreted as described in
<xref
target=
"RFC2119"
/>
.
</t>
<t>
<t>
<list
style=
'hanging'
>
<list
style=
'hanging'
>
<t
hangText=
"CPU:"
>
Central Processing Unit
</t>
<t
hangText=
"CBR:"
>
Constant bitrate
</t>
<t
hangText=
"CPU:"
>
Central Processing Unit
</t>
<t
hangText=
"DTX:"
>
Discontinuous transmission
</t>
<t
hangText=
"FEC:"
>
Forward error correction
</t>
<t
hangText=
"IP:"
>
Internet Protocol
</t>
<t
hangText=
"IP:"
>
Internet Protocol
</t>
<t
hangText=
"PSTN:"
>
Public Switched Telephone Network
</t>
<t
hangText=
"samples:"
>
Speech or audio samples (usually per channel)
</t>
<t
hangText=
"samples:"
>
Speech or audio samples
</t>
<t
hangText=
"SDP:"
>
Session Description Protocol
</t>
<t
hangText=
"SDP:"
>
Session Description Protocol
</t>
<t
hangText=
"VBR:"
>
Variable bitrate
</t>
</list>
</list>
</t>
</t>
<section
title=
'Audio Bandwidth'
>
<section
title=
'Audio Bandwidth'
>
...
@@ -363,7 +366,7 @@
...
@@ -363,7 +366,7 @@
a multiplier according to
<xref
target=
"fs-upsample-factors"
/>
to determine
a multiplier according to
<xref
target=
"fs-upsample-factors"
/>
to determine
the RTP timestamp.
</t>
the RTP timestamp.
</t>
<texttable
anchor=
'fs-upsample-factors'
>
<texttable
anchor=
'fs-upsample-factors'
title=
"Timestamp multiplier"
>
<ttcol
align=
'center'
>
fs (Hz)
</ttcol>
<ttcol
align=
'center'
>
fs (Hz)
</ttcol>
<ttcol
align=
'center'
>
Multiplier
</ttcol>
<ttcol
align=
'center'
>
Multiplier
</ttcol>
<c>
8000
</c>
<c>
8000
</c>
...
@@ -376,11 +379,6 @@
...
@@ -376,11 +379,6 @@
<c>
2
</c>
<c>
2
</c>
<c>
48000
</c>
<c>
48000
</c>
<c>
1
</c>
<c>
1
</c>
<postamble>
fs specifies the audio sampling frequency in Hertz (Hz); Multiplier is the
value that the number of samples have to be multiplied with to calculate
the RTP timestamp.
</postamble>
</texttable>
</texttable>
</section>
</section>
...
@@ -621,11 +619,13 @@
...
@@ -621,11 +619,13 @@
changed, e.g. to adapt to changing network conditions.
<vspace
blankLines=
'1'
/>
changed, e.g. to adapt to changing network conditions.
<vspace
blankLines=
'1'
/>
</t>
</t>
<t
hangText=
"useinbandfec:"
>
specifies that Opus in-band FEC is
<t
hangText=
"useinbandfec:"
>
specifies that the decoder has the capability to
supported by the decoder and MAY be used during a
use the Opus in-band FEC. Possible values are 1 and 0. It is RECOMMENDED to provide
session. Possible values are 1 and 0. It is RECOMMENDED to provide
0 in case FEC cannot be used on the receiving side. If no
0 in case FEC is not implemented on the receiving side. If no
value is specified, useinbandfec is assumed to be 1.
value is specified, useinbandfec is assumed to be 1.
<vspace
blankLines=
'1'
/></t>
This parameter is only a preference and the receiver MUST be able to process
packets that have FEC information, even if it means the FEC part is discarded.
<vspace
blankLines=
'1'
/></t>
<t
hangText=
"usedtx:"
>
specifies if the decoder prefers the use of
<t
hangText=
"usedtx:"
>
specifies if the decoder prefers the use of
DTX. Possible values are 1 and 0. If no value is specified, usedtx
DTX. Possible values are 1 and 0. If no value is specified, usedtx
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment