Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • gst-rtsp-server gst-rtsp-server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 94
    • Issues 94
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • 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

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • GStreamerGStreamer
  • gst-rtsp-servergst-rtsp-server
  • Issues
  • #49
Closed
Open
Issue created Sep 24, 2018 by Bugzilla Migration User@bugzilla-migration

gst_rtsp_media_seek fails after pipeline is playing

Submitted by Benjamin Kleine

Link to original bug (#797195)

Description

There seems to be a seeking issue concerning gstreamer rtsp-server versions 1.13+.

I want to play an existing h264-video file using the rtsp-server and seek to a specific timestamp after the pipeline has been completely set up.

The initial connection is established correctly and the video is played correctly. When calling gst_rtsp_media_seek after a few (10) seconds on the stream media, the video gets stuck and stops playing.

Using older gstreamer versions (1.12.5) the media_seek call is working fine.

Checking the commits, the fix of Bug 788340 might have to do with this, but I'm not that deep into the code to be able to fix it.

Version: 1.14.x

Assignee
Assign to
Time tracking