Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gstreamer gstreamer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 680
    • Issues 680
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 354
    • Merge requests 354
  • 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
  • gstreamergstreamer
  • Issues
  • #259

Closed
Open
Created Dec 04, 2017 by Bugzilla Migration User@bugzilla-migration

aggregator: need gst_aggregator_pad_set_nowait() for sparse streams

Submitted by Tim Müller @tpm

Link to original bug (#791202)

Description

We need a way to tell GstAggregator to never wait for data on certain pads.

This is needed for sparse inputs where we may not always get data or regular GAP events.

Without this, a muxer in non-live mode will just lock up if it doesn't receive data or GAP events on one of the input pads, and in live mode we will always end up with the maximum configured latency since we'll always wait and time out.

See gst_collectpads_set_waiting().

Assignee
Assign to
Time tracking