Open the panel in a supported player path
The current publisher guide documents Stream info with built-in web players using unified controls and experimental frame-copy Embedded MPV. Start playback, reveal the controls and select its information control. External players have their own diagnostic interfaces.
Allow playback to settle before recording values. A startup interval is different from an established session, and some engines expose fewer fields than others. Record the app and engine alongside the observation so a later comparison can be interpreted correctly.
Tie the numbers to the symptom
Write down the moment the picture stops, becomes uneven or changes quality. Look for what changes at that time rather than copying a counter after the event. A dropped-frame total carried from startup differs from one that keeps rising throughout a scene.
Keep resolution, source frame rate and measured presentation distinct. The video window can be large while the media itself is small. A measured rate falling during a freeze shows interrupted presentation; it does not, by itself, identify whether delivery or decoding caused it.
Make a controlled comparison
Repeat the same item and output when testing a different engine or available quality. Compare the visible behaviour as well as the numbers, because another engine may measure or expose different things. Do not present two unlike counters as a precise performance benchmark.
If only one item fails, compare another from the same source before generalising. If every item fails in one engine but works in another, that is useful evidence about the selected playback path. It is still not proof that the network is universally healthy or the service universally compatible.
Prepare a useful private report
The publisher documents Copy diagnostics on relevant 0.24 error screens, with stream URLs and credentials omitted from that generated report. Review any separate screenshots or text you add yourself: the tool’s redaction does not protect a full desktop capture.
Include version, operating system, engine, source type, time and the smallest reproduction sequence. State missing values as unavailable. This gives support enough context to investigate without converting a diagnostic overlay into an unsupported claim of measured internet capacity or verified service reliability.