Playback bug on setting play range start and end

[hiren3897]

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

What version of Shaka Player are you using?
3.3.2

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

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

Are you using the demo app or your own custom app?
Demo APP

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

What browser and OS are you using?
Chrome, Firefox, safari edge on iOS, iPadOS, macOS, Linux, windows

For embedded devices (smart TVs, etc.), what model and firmware version are you using?

What are the manifest and license server URIs?

https://dash.akamaized.net/akamai/bbb_30fps/bbb_with_tiled_thumbnails.mpd
https://multiplatform-f.akamaihd.net/i/multi/will/bunny/big_buck_bunny_,640x360_400,640x360_700,640x360_1000,950x540_1500,.f4v.csmil/master.m3u8

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

playRangeStart: 10,
playRangeEnd: 100

What did you do?

I try to set the start and end range for a VOD DASH and HLS

What did you expect to happen?
To have a timeline according and a playback

What actually happened?

As the previous problem related to the timeline has been resolved by #4026 of #4068

But after setting the range the playback is paused at the start edge of the timeline.
When I click ahead of the start point it plays the video but after some time for both DASH and HLS

When the HLS VOD gets ended the player is not able to play it again

Every time when I click on the timeline or try to seek the video is played very delayed and sometimes it stops the playback, especially in the case of HLS VOD.

[hiren3897]

One more bug:

When we seek the timeline it changes the playRangeEnd === duration === endtime in the player

[hiren3897]

Hello @joeyparrish Can you please comment on this bug?

Thanks

[hiren3897]

Hello, did you have time to see about this bug?

[hiren3897]

⚠️ Can we look around this bug please?

[hiren3897]

Hello, We are in urgent need of this feature can you please respond to this bug?