| Previous | Next |
| NS_S_WMR_PINTYPEFULLMATCH | NS_S_WMG_ADVISE_DROP_TO_KEYFRAME |
NS_S_WMG_ADVISE_DROP_FRAME
Windows Media advises dropping a late frame
NS_S_WMG_ADVISE_DROP_FRAME is HRESULT 856166 (0x000D1066) from Windows Media. AllStat describes it as “The timestamp is late compared to the current render position; Advise dropping this frame.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.
In the legacy Windows Media pipeline or Player state, this result means that the timestamp is late compared to the current render position; Advise dropping this frame. Acceptance depends on the returned state and outputs, not only on the cleared severity bit.
Where the status is encountered
- Windows Media source, reader, writer, or renderer callbacks; log the exact method and object state instead of interpreting the constant outside that contract.
- Windows Media Player SDK automation; log the exact method and object state instead of interpreting the constant outside that contract.
- Media graph, playlist, image, rights, or buffering state; log the exact method and object state instead of interpreting the constant outside that contract.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
Evidence and telemetry
- preserve frame timestamp and current position.
- preserve measured lateness.
- preserve drop policy threshold.
- preserve frame dependency type.
- preserve audio-video synchronization error.
Also record ns_s_wmg_advise_drop_frame_operation, ns_s_wmg_advise_drop_frame_state_before, ns_s_wmg_advise_drop_frame_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. When logging it, redact secret payloads but preserve stable identifiers and hashes needed for correlation.
What must be true before accepting it
Verify that the caller may drop this frame according to quality policy while maintaining synchronization. This check separates a legitimate it outcome from code that ignores an incomplete or altered operation.
Before retrying it, classify its effects as completed, partial, pending, cancelled, adapted, or terminal.
Correct handling and recovery
Prefer dropping when the lateness exceeds the render budget, but record the decision. If drops accumulate, reduce quality or investigate scheduling and decode latency.
Retry it only when a documented input or state has changed. Do not immediately repeat it when the same stable state would produce the same informational result.
Difference from nearby results
It must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.
The distinction around it determines whether the caller stops, waits, consumes output, or changes state.
Practical scenario
A video frame arrives slightly late. The renderer drops it under low-latency policy and keeps the next frame aligned with audio.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
References
- Microsoft: Windows Media Format SDK error codes — official Microsoft material used to interpret it.
- Microsoft: Windows Media Player SDK
- Microsoft: Windows Media Player buffering event
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.