Add target-latency and current-latency to debug view #361
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📺 What
Adds MSE target latency and current latency reporting to the debug menu. Useful when debugging low-latency content, particularly on TV hardware where some decoder behaviours do not match what might be expected
🛠 How
Uses existing
DebugTool.dynamicMetric()
method to add these metrics each time atimeupdate
event is called.✅ Testing
Added underlying dash.js functions to the
mockDashInstance
. No additional unit tests were added.Test Guidelines
👀 See
New fields are seen below when the MSE strategy is chosen. The values
NaN
and 0 are seen when VOD content is played.The same changes are shown again, but using live low-latency content. Extra fields, along with the existing playback rate field, can be used to determine whether low-latency content is performing as expected.
♿ Accessibility [optional]
[Any accessibility features or considerations that this PR addresses should be listed here]