Thin horizontal teeth around moving objects often indicate interlaced fields being shown without suitable deinterlacing. They differ from blocky compression or a network loading pause. Check the input format and decoder processing before adjusting sharpness. Check whether the teeth follow moving boundaries while still areas look normal. That pattern is useful evidence of field processing, although combing already encoded into a progressive source may remain even when the local player is configured correctly.
Use movement to diagnose
Static scenes can hide the issue. Use a repeated section with clear horizontal movement and observe the edges in motion as well as on pause. Alternating field lines can show different moments along the same boundary, producing thin horizontal teeth. A paused frame alone can exaggerate the symptom, so compare normal playback too. If media information reports progressive video, the artifact may have been created during an earlier conversion before the stream reached your device.
Avoid excessive sharpening
It can exaggerate the field edges. Keep sharpness and edge enhancement modest while checking the cause. Increasing either can make the horizontal teeth more obvious without fixing the timing represented by the two fields. Similarly, noise reduction may smear the edges while hiding some teeth. Return picture processing to a known preset and change the supported deinterlacing option in the player separately, so the comparison does not confuse a cosmetic blur with correct field reconstruction.
Compare a progressive source
A clean progressive rendition narrows the problem to the interlaced path. Try an authorized progressive rendition of the same event if one is supplied, or a known clean progressive sample. If only the interlaced rendition shows combing, document its format and the selected decoder path. If the exact artifact appears at the same point on another compatible client, include that observation when reporting the source. Avoid presenting this comparison as proof that all interlaced material or every application is defective.
A practical sequence
- Find a moving diagonal edge
- Read the scan format
- Compare supported deinterlacing modes
- Check a progressive control item
An example
A moving player arm shows alternating horizontal edges while the paused studio backdrop looks normal. The teeth stay attached to a runner's moving arm while the static stadium lettering remains clean. A progressive comparison removes the teeth, directing investigation toward interlaced handling rather than a general sharpening preference or a failure affecting the entire screen.
Questions about this topic
Is this necessarily packet loss?
No. Packet loss has other possible symptoms; the field-shaped pattern needs its own diagnosis.
Can all apps deinterlace equally?
No. Implementation and hardware paths vary. Check the actual player and decoder path rather than relying on a shared operating-system brand.
