Understand traces for Guardians of Galaxy video

[danalex97]

^

[danalex97]

This may be useful: AbandonRequestRule @ https://github.com/Dash-Industry-Forum/dash.js/wiki/ABR-Logic

[danalex97]

We need to implement something like this that talks to the backend in order to abandon segments that could possibly cause rebuffering: https://github.com/Dash-Industry-Forum/dash.js/blob/development/src/streaming/rules/abr/AbandonRequestsRule.js

[danalex97]

Dash JS ref version: https://github.com/Dash-Industry-Forum/dash.js/tree/b90898e81f08c52384f1003c201b74476bf1531d

[danalex97]

Check onFragmentLoadProgress from https://github.com/Dash-Industry-Forum/dash.js/blob/b90898e81f08c52384f1003c201b74476bf1531d/src/streaming/controllers/AbrController.js for the handling of abandoned fragments.

[danalex97]

If the abandons don't work, we can try to change the quality by hand and stop the XMLHttp request via abort.

[danalex97]

Update bc4df6b: since we intercept the normal request, the fragment model has no requests, thus the check if (request) fails:

                const fragmentModel = streamProcessor.getFragmentModel();
                const request = fragmentModel.getRequests({state: FragmentModel.FRAGMENT_MODEL_LOADING, index: e.request.index})[0];

Nope, seems to be working...

[danalex97]

New idea:

• basically stopping the current request and making a new one works
• we can try to return 404 and doing something like reset BlacklistController after url resolution failed Dash-Industry-Forum/dash.js#2539
  --- here is a comment with a dash js modification that can be made for this: Handling missing segments "gracefully" Dash-Industry-Forum/dash.js#651 (comment)
  --- trapping errors: https://stackoverflow.com/questions/35631329/dash-js-trapping-404-errors-from-mpeg-dash-player

[danalex97]

Maybe relevant: https://github.com/Dash-Industry-Forum/dash.js/blob/development/src/streaming/utils/BaseURLSelector.js

[danalex97]

Should be partly fixed by 1cbcd43 - ad06eeb