Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gst-plugins-bad
gst-plugins-bad
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,012
    • Issues 1,012
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 199
    • Merge Requests 199
  • 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
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #517

Closed
Open
Opened Feb 07, 2017 by Bugzilla Migration User@bugzilla-migration

AVFVideoSource must post a latency message after it renegotiates caps

Submitted by Nick Kallen

Link to original bug (#778273)

Description

Background:

The AVFVideoSource represents the iphone front- and rear-facing cameras. The cameras can output at various frame-rates and putting a capsfilter downstream will trigger the frame-rate selection during caps negotiation. The frame-rate affects the latency, because for example 30fps leads to a latency of ~33ms.

The bug:

Adding an avfvideosrc to a pipeline in the NULL state works fine because PLAYING the pipeline will calculate latency after all the caps have been negotiated.

However, if you add an avfvideosrc to an already running pipeline, it will renegotiate caps but it will not trigger a latency event after deciding its frame-rate. If the pipeline already had a latency less than 1/frame-rate frames will be dropped.

The fix:

Post latency message after caps have been set.

Version: 1.11.1

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gstreamer/gst-plugins-bad#517