Skip to content
GitLab
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 933
    • Issues 933
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 438
    • Merge requests 438
  • 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
  • gstreamergstreamer
  • Issues
  • #1162
Closed
Open
Issue created Apr 18, 2022 by Sebastian Dröge@slomo🍵Owner

rtspsrc/rtpbin: Doesn't sync A/V if the server does not provide RTCP

The A/V synchronization only happens in rtpbin when it receives an RTCP SR from rtpjitterbuffer. In case of RTSP this could already happen once the caps are received with clock-base / npt-start, and the first packet is received to know the local arrival times. The clock-base is the RTP timestamp of each stream that corresponds to npt-start.

If the server never sends an RTCP SR then A/V sync is never fixed up, and even if the server sends an RTCP SR it would be much later than necessary.

This can probably be solved by adding a new variant of the sync signal to rtpjitterbuffer that provides clock-base and npt-start among other things and has rtpbin handle this as a special-case in gst_rtp_bin_associate().

Edited Apr 18, 2022 by Sebastian Dröge
Assignee
Assign to
Time tracking