Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gstreamer
gstreamer
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 409
    • Issues 409
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 83
    • Merge Requests 83
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #532

Closed (moved)
Open
Opened Apr 08, 2020 by Benjamin Muzal@bmuzal

tsdemux sends gap event before segment event on sparse streams

tsdemux sends a new gap event on sparse streams with timesamp=0 in gst_ts_demux_update_program() and gst_ts_demux_program_started() This happens before the segment event is sent out.

Downstream from tsdemux, this causes an ugly critical warning in GstAggregator based elements when they try to clip the event without a segment.

If streams always need a gap event at the beginning of sparse streams, maybe the gap event should be sent at the end of calculate_and_push_newsegment() using the start of the segment for the timestamp instead of a timestamp of 0?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gstreamer/gstreamer#532