| Previous | Next |
| NS_S_WMR_ALREADYRENDERED | NS_S_WMR_PINTYPEFULLMATCH |
NS_S_WMR_PINTYPEPARTIALMATCH
Windows Media pin type partially matches
NS_S_WMR_PINTYPEPARTIALMATCH is HRESULT 856160 (0x000D1060) from Windows Media. AllStat describes it as “The specified type partially matches this pin type.” 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 specified type partially matches this pin type. Treat it as a distinct branch whose postcondition must be proven before subsequent operations begin.
What must be true before accepting it
Verify that the negotiated differences are understood and a compatible transform can safely bridge the remaining media-type fields. The caller should make the acceptance test for this HRESULT explicit in code and telemetry.
Inspect the current generation of every affected object before deciding what happens next.
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 major type and subtype.
- preserve format block differences.
- preserve source and target pins.
- preserve candidate transform.
- preserve final negotiated media type.
Also record ns_s_wmr_pintypepartialmatch_operation, ns_s_wmr_pintypepartialmatch_state_before, ns_s_wmr_pintypepartialmatch_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Evidence for this HRESULT should be reproducible but sanitized, with sensitive buffers represented by length and hash.
Correct handling and recovery
Compare every media-type field, enumerate transforms, and connect only after validating the effective type. Do not assume a partial match is directly connectable.
Retry it only when a documented input or state has changed. Distinguish protocol continuation from retrying the entire high-level operation.
Practical scenario
A decoder output matches video major type and subtype but differs in format details. The graph inserts a converter and records the final negotiated type.
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.
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.
Exact handling of it matters because a generic success path cannot express its required next action.
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.