MABR: consider the diff between fetch time and publishTime

[rbouqueau]

What else do we want to compensate? presentationTimeOffset? suggestedPresentationDelay?

[rbouqueau]

This is the list of test streams:
A: Live segment template without manifest updates
https://livesim2.dashif.org/livesim2/testpic_2s/Manifest.mpd => OK
B: Live segment template with manifest updates every 30s
https://livesim2.dashif.org/livesim2/mup_30/testpic_2s/Manifest.mpd => OK
C: Live segment timeline with manifest updates every 30s
https://livesim2.dashif.org/livesim2/segtimeline_1/testpic_2s/Manifest.mpd => Less Stable (sometimes stops with message [DASH] Segment list has not been updated for more than 2003 ms - assuming end of period.)
D: multi-period, 1 period per minutes
https://livesim2.dashif.org/livesim2/periods_60/continuous_1/testpic_2s/Manifest.mpd => OK
E: low-latency single rate
https://akamaibroadcasteruseast.akamaized.net/cmaf/live/657078/akasource/out.mpd => LL playback occurs too soon
F: Low latency multi rate https://cmafref.akamaized.net/cmaf/live-ull/2006350/akambr/out.mpd => LL playback occurs too soon

[rbouqueau]

For C., I tried to mitigate the error message ("Segment list has not been updated for more than %d ms - assuming end of period") by forcing a MPD relaord to no avail.

The client fails with 3 error messages:

1. "Segment list `has not been updated for more than %d ms - assuming end of period"
2. [ROUTE] No data for 10002 ms, aborting
3. This sequence (where we seem to adjust in the future):

[DASH] current time 82378335971472 is greater than last SegmentTimeline end 82378335936512 by 0.728333 sec - defaulting to last entry in SegmentTimeline
[DASH] current time 154459379946510 is greater than last SegmentTimeline end 154459379880000 by 0.739 sec - defaulting to last entry in SegmentTimeline
[DASH] Error in downloading new segment http://groute/service1/A48/82378335744000.m4s: Bad Parameter