Skip to content
GitLab
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 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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.OrgXiph.Org
  • VorbisVorbis
  • Issues
  • #1693
Closed
Open
Issue created Apr 30, 2010 by siddartha@siddu_1184

Truncated packets in ogg vorbis

In the ogg vorbis spec, it is mentioned that 'packets are designed that they may be truncated(padded) and remain decodable'. Are there any limitations to this truncation i.e., if the packet is truncated, is there any limitation on where the trunction can start? Or the truncation can start at any stage of encoding?

For example, truncation can only happen after floor decoding etc.,

Assignee
Assign to
Time tracking