A DASH presentation can describe alternative media representations with different technical properties. A manifest listing an option does not prove that the current device selected or successfully decoded it.
Separate declared capability choices from observed playback when judging resolution, codec support or HDR.
Read the representation as a configuration
A representation can be associated with properties such as codec, dimensions or rate. The client needs to consider support before choosing a playable route. DASH-IF’s dash.js documentation describes filtering based on codec and other required properties.
That makes a manifest an inventory of possibilities, not a record of a completed viewing test. An application can reject an unsupported option or choose another representation. A technical listing alone cannot establish what the television actually showed.
Audio and text selections add their own requirements. Successful video decoding does not prove that the intended language, captions or sound format was selected. Keep the chosen tracks and route with the picture observation.
Keep viewer and developer evidence distinct
A viewer can record the app’s reported current source information and the display’s detected output. A developer can inspect a presentation they are authorized to work on. Neither should expose private account URLs or tokens in a public troubleshooting capture.
If a high-resolution option is declared but playback stays lower, describe both facts. Do not assume the cause is one component without checking application selection, decoder support and the actual source route.
| Evidence | Useful limit |
|---|---|
| Manifest lists a representation | It is declared, not proven played |
| Player reports current dimensions | A runtime observation in that implementation |
| Display reports input mode | An output-stage observation |
| A representation fails | Needs the exact configuration and error |
Use a supported comparison
If the source offers a legitimate manual quality choice, read its meaning in that application. Compare the same scene and record what the player reports before and after. Keep television processing unchanged so the source comparison remains interpretable.
For support, include title, app, device, reported representation and exact symptom. Avoid treating the existence of an MPD file as proof that every browser or player supports the complete presentation. Compatibility belongs to the actual media and implementation.
- Identify the selected source and application.
- Record current runtime media information where available.
- Keep declared options separate from the observed selection.
- Compare one documented supported option.
- Report the exact unsupported or unknown stage.
Useful answers
Does a DASH manifest listing 4K prove 4K playback?
No. Selection, decoding and output still need runtime evidence.
Can two DASH representations require different capabilities?
Yes. Their codec or other media properties can differ.