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
  • #226
Closed
Open
Issue created Sep 21, 2015 by Bugzilla Migration User@bugzilla-migration

rtsprange: gst_rtsp_range_get_times() returns the wrong value for ntp ranges

Submitted by Linus Svensson

Link to original bug (#755353)

Description

Created attachment 311758
Unit test with an ntp error case

gst_rtsp_range_get_times() returns wrong values for reasonably large numbers for npt. I have attached a unit test, which uses ~40 years expressed in seconds, and the result is that the fractions of a second is lost/rounded.

Patch 311758, "Unit test with an ntp error case":
0001-rtsp-Unit-test-for-large-ntp-values.patch

Assignee
Assign to
Time tracking