Support mediaRange in DASH

We find some of the streams from service provider couldn’t play due to lack of support on mediaRange in Bitmovin web player.

The attribute mediaRange in SegmentURL within SegmentList doesn’t trigger a fragment request with corresponding byte range. The request is blocked due to missing byte range in request header.

Compared with Shaka player, it’s requesting with correct byte range in request.
Here is a short sample manifest that can observe this missing byte range issue.

hello @victor.wu

thanks for logging your request via our community.
I matched this with your internal Zendesk ticket and I see we already opened a Feature Request to our product board (internal code 33938361)
Our product team will evaluate this and update this ticket in the future when they have a decision on this request.


This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.