Open dsilhavy opened 1 month ago
According to the contents of '@duration' in '5.3.9.5.2 Initialization Segment information' of ISO IEC 23009-1 : 2022 document below,
There is no rule for MUST pairing '$Number$ : @duration' and '$time$ : sengmentTimeline'
According to the above document, when using @duration, there is a definition of how '$time$' is determined, so I think it is usable.
According to the document, the @startNumber value is affected, but the @presentationTimeOffset value has no effect on both '$time$' and '$number$'.
When using '$time$' and @duration in mpd, 'Shaka player' matches the @presentationTimeOffset value to the 'start time' value of '$time$', I can't find such content in the above standard document, so I think it is a bug in shaka player related to time calculation.
TF 2024/08/16
$Time$
and @Number
, but use Segment Timeline with r=-1
to have an open ended template.
Description
Based on our discussion in the DASH-IF Live Call last week and an issue we addressed recently in dash.js I would like to clarify the right player behavior for content that uses
SegmentTemplate
with$time$
but does not contain aSegmentTimeline
element.As an example:
Discussion Items
startNumber
have an influence on how the player determines the right segment URL. For instance, ifstartNumber
is set to 5 do we need to request a segment with$time$
larger than0
@presentationTimeOffset
is specified? Do we assume that theearliestPresentationTime
of the first segment is equal to the@presentationTimeOffset
? This would imply that we have an@eptDelta
of 0. We then replace$time$
with the value of the@presentationTimeOffset
for the first segment. For subsequent requests, the@duration
is added.tfdt.baseMediaDecodeTime
and add the sample durations to find the right URL for the next segment?Related Issues