DASH loading failure when SegmentTimeline with $number format is used

[kazuhide]

It seems that the manifest loading might fail depending on the DASH manifest format type. During testing, I found it always reproduces when using the DASH SegmentTimeline with $number. This can also be reproduced using the below DASH-IF’s test vector.

https://reference.dashif.org/dash.js/nightly/samples/dash-if-reference-player/index.html LIVE (Dynamic MPD) -> [DASH-IF] SegmentTimeline with $number (livesim)

• manifest url: https://livesim2.dashif.org/livesim2/segtimelinenr_1/testpic_2s/Manifest.mpd

  <SegmentTemplate media="$RepresentationID$/$Number$.m4s" initialization="$RepresentationID$/init.mp4" startNumber="864529554" timescale="48000">
  <SegmentTimeline>
  <S t="82994837184512" d="96256"></S>
  : 

When I validated the error logic, it seems that Bitmovin Player's player.getAvailableSegments() API (implemented in the preprocessHttpRequest callback here and here) throws an error when loading the DASH manifest. And since exception handling is not implemented for this, the network API can't process the request properly, resulting in an error.

Although further investigation of why API shows an error, it seems the loading failure can be avoided by implementing the exception handling.

[kazuhide]

fixed with https://github.com/bitmovin/bitmovin-player-web-integration-cmcd/pull/7