You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make it possible to set start time separate from availabilityStartTime.
start time is to be interpreted as the timeline offset for media timeline.
In addition, it should be possible to specify that the first period starts at a later time.
For the most general case, we need three URL parameters, all defined in NTP seconds
(relative to epoch start 1970-01-01T00:00:00Z).
start - this is the anchor point for the media timeline relative to epoch start
ast (availabilityStartTime) >= start is the start and reference point for the mediaTimeline in the MPD. It is defined relative to epoch start.
fpstart (firstPeriodStart >= ast is the time that the first period starts. It should be AST when the timeShiftBufferDepth makes the current interval overlap with ast. PresentationTimeOffset values must be set so that the media timeline is correct.
presentationTimeOffset must be set relative to timelineStart (start), so it may be be non-zero even for a period starting at the availabilityStartTime. This mimics the situation where one wants to have the availabilityStartTime point to the start of a program in a live channel, but the media timeline is relative to some other time like the Epoch start.
Constraints:
start <= ast <= fpstart
If only start is specified (could be via relstart), ast and fpstart will automatically change to the same value.
With more values specified, unspecified values are automatically shifted to fulfil the constraints.
If specified values are not compatible, an error is returned.
The text was updated successfully, but these errors were encountered:
Make it possible to set start time separate from availabilityStartTime.
start time is to be interpreted as the timeline offset for media timeline.
In addition, it should be possible to specify that the first period starts at a later time.
For the most general case, we need three URL parameters, all defined in NTP seconds
(relative to epoch start 1970-01-01T00:00:00Z).
start
- this is the anchor point for the media timeline relative to epoch startast
(availabilityStartTime) >= start is the start and reference point for the mediaTimeline in the MPD. It is defined relative to epoch start.fpstart
(firstPeriodStart >= ast is the time that the first period starts. It should be AST when the timeShiftBufferDepth makes the current interval overlap with ast. PresentationTimeOffset values must be set so that the media timeline is correct.presentationTimeOffset must be set relative to timelineStart (
start
), so it may be be non-zero even for a period starting at the availabilityStartTime. This mimics the situation where one wants to have the availabilityStartTime point to the start of a program in a live channel, but the media timeline is relative to some other time like the Epoch start.Constraints:
If only
start
is specified (could be viarelstart
), ast and fpstart will automatically change to the same value.With more values specified, unspecified values are automatically shifted to fulfil the constraints.
If specified values are not compatible, an error is returned.
The text was updated successfully, but these errors were encountered: