Skip to content
GitLab
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 973
    • Issues 973
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 104
    • Merge requests 104
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #962
Closed
Open
Issue created May 03, 2019 by Seungha Yang@seungha.yang🐑Developer

h264,h265parse: nal alignment might cause noisy caps update

Follow up of !308 (comment 156190)

Some SEI messages (frame packing, HDR related and more) can be mapped to output caps field. The problem here is when output is nal aligned. Unlike AU alignment which aggregates complete AU so the sufficient information is available when initial negotiation time, current implementation of h264/h265parse could update output caps multiple times at initial negotiation time.

Condition

  • upstream is byte-stream with nal alignment (e.g, tsdemux)
  • a bitstream consist of | 1) AUD | 2) SPS | 3) PPS | 4) HDR related SEI | 5) IDR | ..
  • downstream allows byte-stream with nal alignment also

In above condition, output caps will be set 3 times at 1), 2), and 4)

Possible solution is

  • Delayed caps: aggregating nals until parse element can ensure output caps (e.g., until the first slice nal)
    • This can bring additional initial time latency and also some application can complain about delayed negotiation timing.

CC: @slomo

Assignee
Assign to
Time tracking