For Live Dash Stream with TimeshiftBufferDepth, player starts from the beginning of the program instead of current time

[git-archs]

Have you read the FAQ and checked for duplicate open issues?
Yes

If the problem is related to FairPlay, have you read the tutorial?

Not related to Fairplay

What version of Shaka Player are you using?

4.13.2

Can you reproduce the issue with our latest release version?
Yes

Can you reproduce the issue with the latest code from main?
Yes

Are you using the demo app or your own custom app?
Custom

If custom app, can you reproduce the issue using our demo app?

What browser and OS are you using?
Chrome/77.0.3865.120, Linux

For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Its a Linux based Set Top Box which is running Chrome/77.0.3865.120

What are the manifest and license server URIs?

What configuration are you using? What is the output of player.getNonDefaultConfiguration()?

What did you do?

Tried this scenario in the Shaka 4.13.2 version and also in the latest main branch code.

Tried playing Widevine DRM protected Live Dash Stream while the program had started 20 mins ago.Instead of playing from the current position, the player started playing from the beginning of the program. This is a scenario where DVR options are available and manifest has historical LOD available with the timeShiftBufferDepth property.

Note: we are currently using the Shaka 4.11 version, and this issue does not happen there.

What did you expect to happen?
Player should have started playing from the current time.

What actually happened?

Player started to play from the beginning of the program which is not the current live postion.

Are you planning to send a PR to fix it?
Not Yet.

[avelad]

**What are the manifest and license server URIs?**
<!-- NOTE:
  You can send the URIs to <shaka-player-maintainers@googlegroups.com> instead,
  but please use GitHub and the template for the rest.
  A copy of the manifest text or an attached manifest will **not** be
  enough to reproduce your issue, and we **will** ask you to send a
  URI instead.  You can copy the URI of the demo app to send us the
  exact asset, licence server, and settings you have selected there.
  Avoid geo-blocked content if at all possible, as the contributors who diagnose
  Shaka Player issues may not be able to access it.
  If you send the URIs to email, the response time and resolution
  will be much higher.
-->

[git-archs]

The urls will require authentication and there are encryption details in the manifest. I can provide a manifest after modifying the encryption details. Is the main manifest along with one period example good?

[joeyparrish]

Please send whatever it takes for us to reproduce the issue.

[git-archs]

Details shared over slack channel.

[avelad]

The commit that introduces the regression is 1b19391, it only plays on slow devices.