Applies to: A player exposing a visible timeline or loading indicator; a replayable lawful item with noticeable movement.
The useful distinctions
- NVIDIA documents conversion when source and display rates differ.
- SHIELD frame-rate matching has app and display limitations.
- Diagnostic inference to test: A timeline that continues and a loading stop are distinct observable events.
Observe more than the picture
A pan can appear uneven while the programme continues to advance. A stalled player may instead hold a picture while it waits, show a loading symbol or stop advancing its timeline. These signs are not universal, so record what your player actually exposes. Audio continuing through an event is another useful observation, not a definitive diagnosis.
Keep cadence and interruption separate
Describe a repeated small step as a motion event unless you have evidence of a playback stop. Describe a visible waiting state as a stall. If both occur, report them separately with their positions. This prevents a frame-output comparison from being credited with solving a network interruption, or a connection change from being credited with changing source cadence.
Choose a controlled follow-up
A supported local reference can help check whether the output chain handles continuous motion, but it exercises a different delivery path and possibly a different decode path. A known-rate clip is useful only when its provenance is known. Keep conclusions narrow and preserve the original item’s timeline evidence for an app or provider report if the problem remains item-specific.
A focused way to proceed
- Choose a short passage that repeatedly looks uneven.
- Watch for timeline movement, loading indicators and continuing audio.
- Replay the passage and log the event’s position and duration descriptively.
- Compare a known-rate local reference on the same output path if supported.
- Use the resulting event description to choose motion or delivery checks.
Worked example · synthetic
Hypothetical example: a pan has small regular steps while the timeline and speech continue, with no waiting symbol. Another attempt freezes with a loading ring. The user records two symptoms and investigates cadence and waiting separately, rather than treating both as one speed problem.
When to stop or ask for help
No loading symbol does not prove the network is perfect. Escalate with the exact observable event and item position rather than a guessed cause.