Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-bad gst-plugins-bad
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 985
    • Issues 985
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 132
    • Merge requests 132
  • 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-badgst-plugins-bad
  • Issues
  • #614

Closed
Open
Created Sep 20, 2017 by Bugzilla Migration User@bugzilla-migration

gstdashdemux : Play a dash content from non-zero offset fails and always starts from beginning.

Submitted by Debdeep

Link to original bug (#787946)

Description

Dear Members,

When try to play a dash content from a non-zero offset, playback fails to start from the requested offset and always start from 0 i.e. from beginning.

The issue is only seen with contents having "isoff-on-demand" profile. This is because, in this profile, the entire content is downloaded and parsed at the beginning of the playback. Since the downloading/parsing the entire content at one go takes time, the position change request reaches dashdemux before the entire parsing is completed and is ignored.

Works fine with all the contents having "isoff-live" profile.

Use case :

  • Initiate a play request for dash content.
  • During pipeline creation, on receiving GST_MESSAGE_ASYNC_DONE from sink, issue a seek request to the pipeline i.e. suppose the duration of the content is 4 mins, issue a seek request to start the the playback from 2 mins,from begin.
  • The playback should start from the 2nd minute instead of beginning.

URL to reproduce the issue :
http://dash.edgesuite.net/dash264/TestCases/1a/sony/SNE_DASH_SD_CASE1A_REVISED.mpd

Can you please look into this ?

Thanks

Version: 1.8.0

Assignee
Assign to
Time tracking