| Previous | Next |
| NS_S_WMPCORE_MEDIA_VALIDATION_PENDING | NS_S_WMPCORE_COMMAND_NOT_AVAILABLE |
NS_S_WMPCORE_PLAYLIST_REPEAT_SECONDARY_SEGMENTS_IGNORED
Additional ASX repeat blocks were ignored
NS_S_WMPCORE_PLAYLIST_REPEAT_SECONDARY_SEGMENTS_IGNORED is HRESULT 856324 (0x000D1104) from Windows Media. AllStat describes it as “Encountered more than one Repeat block during ASX processing.” 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 encountered more than one Repeat block during ASX processing. The high-level request can be considered complete after it only when its documented postcondition has been checked.
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.
What must be true before accepting it
Verify that the application knows which repeat block was honored and the resulting playback sequence. The verification prevents it from being promoted to broader success than the producing API promised.
The component may have changed durable or in-memory state before returning it; inspect that state first.
Evidence and telemetry
- preserve playlist URL and hash.
- preserve repeat block positions.
- preserve block selected by parser.
- preserve items and repeat counts produced.
- preserve parser version.
Also record ns_s_wmpcore_playlist_repeat_secondary_segments_ignored_operation, ns_s_wmpcore_playlist_repeat_secondary_segments_ignored_state_before, ns_s_wmpcore_playlist_repeat_secondary_segments_ignored_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Protect user data in logs and keep only the identifiers required to reproduce component state.
Correct handling and recovery
Record the selected repeat segment, warn when author intent may differ, and validate the flattened playlist order before playback or export.
Retry it only when a documented input or state has changed. Retry policy must follow the owning state machine rather than a generic transient-error loop.
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 nearby-status comparison controls whether outputs are usable and whether more work is expected.
Practical scenario
An ASX playlist contains two Repeat blocks. The player honors the primary block, ignores the secondary one, and shows the resulting sequence in diagnostics.
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.