GNOME Bugzilla – Bug 775757
mpdparser: Parse MPD Anchor "t" and "period" parameters
Last modified: 2018-11-03 14:01:21 UTC
ISO/IEC 23009-1:2014 Annex C.4 defines MPD Anchor which is to indicate start time offset, period, and etc. Basically, the syntax of MPD Anchor follows Media Fragments URI 1.0 from key-value pair parsing point of view.
Created attachment 341556 [details] [review] mpdparser: Parse MPD Anchor "t" and "period" parameters
Created attachment 341557 [details] [review] dashdemux: Set presentation time range by MPD Anchor If there is successfully parsed MPD Anchor, demux will seek to the startup position corresponding to MPD Anchor. And, presentation time range (i.e., segment.{start/stop}) will be set by the MPD Anchor.
If URI has MPD Anchor which is a sort of URI Media Fragment, playback should start from the position corresponding to parsed MPD Anchor. Note that, if there are any syntax error in MPD Anchor, the URI Media Fragment will be ignored. <UseCase> (without MPD Anchor) gst-play-1.0 http://dash.akamaized.net/dash264/TestCases/1a/netflix/exMPD_BIP_TC1.mpd ==> Normal playback (with MPD Anchor, "t=90,95") gst-play-1.0 http://dash.akamaized.net/dash264/TestCases/1a/netflix/exMPD_BIP_TC1.mpd#t=90,95 ==> Playback starts at 90sec and ends at 95sec.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/491.