Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Vorbis Vorbis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Xiph.Org
  • VorbisVorbis
  • Issues
  • #1609
Closed
Open
Created Oct 18, 2009 by Gitlab Bot@GitlabBotDeveloper

Some specification improvements

Michael Scheerer has following comments on the Vorbis specification after successfully implementing a Vorbis decoder accordign to spec:

  1. A not actual MDCT link.

Actual is e.g. http://www.digital-audio.net/res/docs/ps/eusipco_corrected.ps

  1. A decoder side scaling factor described in the paper was proposed for the vorbis decoder, including following code lines: float scale;

scale=4.f/n;

but then never used, because the scale is now done encoder sided.

This should be mentioned in the spec.

  1. The residue reconstruction after the sentence:

"Packet decode proceeds as follows, matching the description offered earlier in the document."

has at least one curly bracket error in the pseudo code. A developer can't determine, which code block belongs to which curly bracket.

Assignee
Assign to
Time tracking