Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gst-plugins-good
gst-plugins-good
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 618
    • Issues 618
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 108
    • Merge Requests 108
  • 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
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GStreamer
  • gst-plugins-goodgst-plugins-good
  • Issues
  • #417

Closed
Open
Opened Nov 24, 2017 by Bugzilla Migration User@bugzilla-migration

rtpsession: avoid computing the sources multiple times in the same RTCP cycle

Submitted by Miguel París Díaz @mparisdiaz

Link to original bug (#790795)

Description

Created attachment 364343
rtpsession: avoid computing the sources multiple times in the same RTCP cycle

I come across a problem when RTCP is generated in an RtpSession with more than 1 internal&sender RtpSources that causes to add the same Report Blocks (RB) in each RTCP SR packet generated per each internal&sender RtpSource.
Whit this behavior:

  • Bandwidth is wasted.
  • fraction-lost value is wrong (except in the RBs of the first SR) due to its calculation is based in a previous state refreshed each time the RB is generated, which should only take place once per RTCP cycle, not per each internal&sender RtpSource in each RTCP cycle.

I am attaching a patch that fixes the issue and adds a test about it.
I think that the test could be improved using GstTestClock to crank RTCP thread.

Patch 364343, "rtpsession: avoid computing the sources multiple times in the same RTCP cycle":
0001-rtpsession-avoid-computing-the-sources-multiple-time.patch

Version: 1.8.3

Depends on

  • Bug 790762
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gstreamer/gst-plugins-good#417