Choose a comparison with a reason
When playback fails, a second item can help describe the scope. It should be chosen deliberately, with the rest of the setup kept as consistent as possible. Comparing one live channel and one on-demand title can reveal whether both paths fail, but it does not make them technically identical.
Live and on-demand playback can use different media resources and account arrangements. A successful on-demand item therefore does not prove every live feed is available, while a failed film does not establish a total service outage. The comparison narrows the report rather than delivering a final diagnosis.
A hypothetical two-item record
Imagine a viewer opens the same player on the same device and ordinary connection. A named live item produces sound but no picture. A named on-demand item then displays picture and sound. This is evidence that the second path worked at that time, not proof that the first item has one particular codec or rights problem.
Reverse the result and the report changes: a live channel works while an on-demand item fails at a certain playback position. That position becomes useful context. If both fail before an item list appears, the failed stage is earlier than either media comparison.
Record the information each mode needs
| Mode | Useful identifying detail |
|---|---|
| Live channel | Full feed name, regional edition and local date/time |
| On-demand title | Exact title, film edition or season/episode and playback position |
| Replay | Original programme date and the actual replay control selected |
| Both paths | Device, app version and the connection used |
Keep the test within confirmed access
Use only the items and account conditions actually available to you. Do not add an unknown public source or a different account merely to obtain a working result. That would change both the technical route and the access arrangement.
If the account has a simultaneous-connection limit, stop the first stream deliberately before opening another where required. A comparison intended to investigate picture behavior should not accidentally become an unreported concurrency test.
Tell support what the comparison excludes
A clear message can say that the app opened, the list loaded, one named live item failed in a stated way and one named on-demand item worked. It should not say all channels are down if only one was tried.
If you then change a network or output setting, repeat the same selected action and note the result. Do not silently replace the comparison item each time. Keeping the source names and conditions visible makes the next investigation more precise and helps prevent a successful unrelated item from hiding the original problem.
Questions answered
Does one working film prove every live channel works?
No. It establishes a result for that item and playback path at that time.
Why record a playback position for on-demand video?
A repeatable position can help distinguish a fault at one passage from a failure before the item starts.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.