Skip to content

GitLab

  • Menu
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 645
    • Issues 645
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-plugins-basegst-plugins-base
  • Issues
  • #339

Closed
Open
Created Feb 22, 2017 by Bugzilla Migration User@bugzilla-migration

videoencoder: produces incorrect dts with vtenc, when crossing segment boundary

Submitted by Nick Kallen

Link to original bug (#779088)

Description

This bug is subtle and involves segment boundaries:

GstVideoEncoderBase, if dts == -1, will attempt to set it to a sane value.

In one case, it picks the "lowest unsent PTS". However, consider the case where there are e.g. 2 outstanding frames: one from one segment and another in a different segment. You cannot compare the PTS of these frames without factoring in the segment base. However, the code does not do that at all:

https://github.com/GStreamer/gst-plugins-base/blob/master/gst-libs/gst/video/gstvideoencoder.c#L2114

Version: 1.11.1

Assignee
Assign to
Time tracking