Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-base gst-plugins-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 641
    • Issues 641
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • 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-basegst-plugins-base
  • Issues
  • #367
Closed
Open
Issue created Jul 17, 2017 by Bugzilla Migration User@bugzilla-migration

videorate: Outputs too much data on segment updates

Submitted by Edward Hervey @bilboed

Link to original bug (#785027)

Description

When an "update" segment arrives in videorate, the next timestamps is resetted, causing a huge amount of duplicate (and late) frames to be outputted.

To reproduce, using the gst-validate media suite:
gst-launch-1.0 -v uridecodebin uri=file://$HOME/gst-validate/gst-integration-testsuites/medias/defaults/mp4/fragmented_nonseekable_sink.mp4 ! identity name=before silent=False ! videorate ! fakesink name=after silent=False

What comes in to videorate:

  • segment start:0, stop:2s
  • buffers from 0 to 2s
  • segment start:0, stop:4s
  • buffers from 2s to 4s
  • etc...

What comes out of videorate

  • segment start:0 stop:2s
  • buffers from 0 to 2s
  • segment start:0, stop:4s
  • buffers from 0 to 2s /!\
    ** The problem is right here. Those buffers are all duplicates of the incoming 2s buffer and are all late.
  • buffers from 2s to 4s

Any element after videorate that assumes that timestamps are increasing is going to have a looot of problems.

Blocking

  • Bug 783842
Assignee
Assign to
Time tracking