Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Read the selected values
A diagnostic capture page can ask for a particular configuration and then display the request as if it were the actual result. The track getSettings method exists to retrieve its current constrainable property values. MDN distinguishes those selected settings from getConstraints, which reflects the constraints established by the site. When investigating a low resolution preview, report what the track actually selected rather than copying a number out of the application form.
Make the discrepancy explicit
Consider an invented test in which a page requests an ideal width of 1920 but the returned settings report 1280. The request and the result should occupy different columns in the report. Do not round either into a generic HD label, and do not infer that the camera is defective from that difference alone. Preserve other applicable settings and whether the property was actually present, since the API can omit values which are unavailable in a given context.
Keep missing data distinct from zero
A property absent from the settings object is not a measured value of zero. MDN notes that context and support affect what is returned, including some differences for WebRTC tracks. A useful developer report identifies the capture method, browser and actual settings observed after startup. This procedure checks a local media track configuration. It does not measure the native production resolution of a television programme, a remote service bitrate, or the resolution capabilities of every television connected to the computer.