Joey Parrish ca3119dfba Correct segment timestamps in PresentationTimeline ...

Before, segment timestamps were used in PresentationTimeline without
regard for the period start.  This means they were not truly relative
to the presentation, but to the period.

The "isFirstPeriod" argument was also broken.  It was meant to be true
for segments from the first period *ever*, but was passed true for the
first period *in the latest manifest update*.  So data calculated from
that was bogus for live streams.

Now, notifySegments() is supplied with a period start time, so that
segment references can be combined with the period start to give
presentation timestamps.  This fixes a major issue with the original
fix for #999.

Closes #999

Change-Id: Id0fe450f3ce4f90a2387d7103c75eb88f0c69c72

2018-08-20 19:10:02 +00:00

..

abr

Restore addPartialStream method.

2018-08-16 22:51:59 +00:00

assumptions

Convert 'var' to 'let'/'const' (9 of 9).

2018-02-20 11:30:04 -08:00

cast

Add Context To The 5KB Chrome Cast Limit

2018-08-14 18:33:37 +00:00

dash

Correct segment timestamps in PresentationTimeline

2018-08-20 19:10:02 +00:00

hls

Restore addPartialStream method.

2018-08-16 22:51:59 +00:00

media

Correct segment timestamps in PresentationTimeline

2018-08-20 19:10:02 +00:00

net

Added 'retry' event to networking engine

2018-08-15 20:31:02 +00:00

offline

Add closedCaptions field to stream

2018-08-17 21:20:09 +00:00

test

Add closedCaptions field to stream

2018-08-17 21:20:09 +00:00

text

Re-enable some disabled style rules

2018-07-09 19:44:56 +00:00

util

Moved cloneObject to new util file

2018-08-07 13:15:06 -07:00

player_external.js

Don't count external asset tests as skipped

2018-07-31 19:09:56 +00:00

player_integration.js

Don't count external asset tests as skipped

2018-07-31 19:09:56 +00:00

player_unit.js

Restore addPartialStream method.

2018-08-16 22:51:59 +00:00