Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-bad gst-plugins-bad
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 985
    • Issues 985
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 132
    • Merge requests 132
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #561

Closed
Open
Created Jun 01, 2017 by Bugzilla Migration User@bugzilla-migration

dashdemux: Nominal bitrate is estimated rather than set from selected stream

Submitted by Jonathan Miles

Link to original bug (#783324)

Description

adaptivedemux sets GST_TAG_NOMINAL_BITRATE to stream->fragment.bitrate. If fragment.bitrate isn't set by the subclass, it will calculate a bitrate based on fragment size and duration.

As dashdemux doesn't set fragment.bitrate, and the fragments vary in size, this means that the nominal bitrate for DASH playback varies and doesn't reflect the headline bitrate of the selected stream.

Version: 1.12.0

Assignee
Assign to
Time tracking