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
7abe7d65
Commit
7abe7d65
authored
10 years ago
by
Ralph Giles
Browse files
Options
Downloads
Patches
Plain Diff
oggopus: Clarify leading zeros are ok for R128 tags.
Add a limit of no more than 6 characters for these tags' values.
parent
fd562eef
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/draft-ietf-codec-oggopus.xml
+3
-1
3 additions, 1 deletion
doc/draft-ietf-codec-oggopus.xml
with
3 additions
and
1 deletion
doc/draft-ietf-codec-oggopus.xml
+
3
−
1
View file @
7abe7d65
...
...
@@ -1217,8 +1217,10 @@ The gain is also a Q7.8 fixed point number in dB, as in the ID header's
<t>
An Ogg Opus stream MUST NOT have more than one of each tag, and if present
their values MUST be an integer from -32768 to 32767, inclusive,
represented in ASCII with no whitespace.
represented in ASCII
as a base 10 number
with no whitespace.
A leading '+' or '-' character is valid.
Leading zeros are also permitted, but the value MUST be represented in
no more than 6 characters.
Other non-digit characters MUST NOT be present.
</t>
<t>
...
...
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