What does HRESULT 0x000D1104 (NS_S_WMPCORE_PLAYLIST_REPEAT_SECONDARY_SEGMENTS_IGNORED) mean?

 
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. The documented description is “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.

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.

Evidence to preserve

  • Preserve playlist URL and hash.
  • Preserve repeat block positions.
  • Preserve block selected by parser.
  • Preserve items and repeat counts produced.
  • Preserve parser version.

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 policy must follow the owning state machine rather than a generic transient-error loop.

Difference from nearby results

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.

References


Looking for a different code? Search another status or error code.