Repository navigation
Replies: 5 comments 2 replies
Can you please share the following information:
If I disable |
|
Thank you for your response. My dash.js version is 5.1.1. I have continued investigating the issue. dash.js code seems to suppose that data is received by chunks, so we are supposed to get several "progress" event during streaming. In fact, I use dash.js in a personal c# MAUI application, which embeds a HybridWebView (embedding a Microsoft WebView2), and I intercept/process network requests for some reasons. So instead of getting data by chunks, dash.js receives xmlHttpRequest responses in one unique block, so there is only one progress event, and traces are only made on one item. To answer your question, useResourceTimingApi is set but httpRequest._resourceTimingValues is always null, probably for the reason above. Anyway, don't worry finding a solution. What I was looking for was explanations more than a solution. Once the reason is confirmed, I will be able to find a solution, maybe by modifying dash.js code in my application. I just wanted to be sure than my understanding is correct. Thanks |
|
I've found why resource timing API was not used. My steam provider doesn't set "Timing-Allow-Origin" in header, so ResourceTimingApi cannot be used. Anyways, both "resource timing" computation and "traces" computations both suppose that we get several 'progress' events for a HttpRequest, so suppose that data is provided by chunks :
I suppose that providing data by chunks is necessary for dash streaming. My interception is just broking this. Regards |
|
Hello again, In fact, I get correct timing here (ResourceTiming API) function _addResourceTimingValues(httpRequest, httpResponse) { (ex : responseStart =1132, responseEnd = 1308, duration =175) But in function _calculateThroughputValuesForXhr(httpRequest, latencyInMs) httpRequest._resourceTimingValues.responseStart is not correct. It is equal to httpResponse.resourceTiming.responseEnd. => Is it a bug or wanted ? I am not sure data provided by ResourceTiming API is really used.
Thanks in advance |
|
I’ve created an issue to make things easier to track and follow: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
Abr is not working in my case.
After investigation, the problem is due to the fact that 'traces' length (infos on xmlHttpRequests) doesn't go above 1.
If I understand correctly, code expects that several 'progress' events are received for a give XmlHttpRequest but I only get one.
Is my understanding correct ? Are we sure to get several progress events in usual cases ?
Thank you
All reactions