| Previous | Next |
| NS_E_INVALID_INTERLACEMODE | NS_E_INVALID_NONSQUAREPIXEL_COMPAT |
NS_E_INVALID_INTERLACE_COMPAT
How to interpret the code in a real encoding session
0xC00D1BDC is named NS_E_INVALID_INTERLACE_COMPAT. Its practical scope is interlace preservation conflicts with the Player 7.1 compatibility target, which belongs to legacy player compatibility rules rather than to every part of Windows Media playback or Windows itself.
Mechanism and point of failure
Windows Media Encoder profiles can be checked for compatibility with older Windows Media Player generations. VBR, multiple audiences, audio/video format variation, interlace and non-square pixels can move a profile beyond the version 7.1 compatibility envelope.
The profile may be valid for Windows Media 9 or later and still be intentionally rejected when an older compatibility target is required. A typical reproduction is: an interlaced Windows Media 9 profile is marked for 7.1 clients. This makes the first result from the Encoder more valuable than a later generic message.
Minimal experiment
- Record
0xC00D1BDC, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture DetectCompatibility result and interlace mode. - Verify the legacy player compatibility rules precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison that changes only the identified precondition: disable interlace preservation or raise the required player version.
Do not collapse these results together
| Result | Why it differs |
|---|---|
NS_E_MULTIPLE_VIDEO_SIZES | audiences use different frame sizes while Player 7.1 compatibility is requested |
NS_E_INVALID_NONSQUAREPIXEL_COMPAT | non-square-pixel output conflicts with the Player 7.1 compatibility target |
NS_E_MULTIPLE_AUDIO_FORMATS | audiences use different audio formats while legacy Player 7.1 compatibility is requested |
What to change—and what to leave alone
Do not describe a compatibility result as codec corruption; first decide whether support for the older player is a real requirement.
Why interlace compatibility is a separate decision
Interlace preservation is not simply another bitrate option. It changes how fields are represented in the encoded video and therefore affects the decoder and renderer capabilities assumed by the profile. Record whether the input is actually interlaced, the field order, the output dimensions, and the profile flag used to maintain interlacing. A progressive source with an inherited interlace flag is a profile-authoring defect; a genuinely interlaced source may instead require a newer playback baseline.
Use IWMEncProfile2.DetectCompatibility after changing only the interlace setting. If the profile becomes compatible while codec, bitrate, audience count and frame size remain unchanged, the result is specifically about the legacy compatibility target. If validation still fails with interlace preservation disabled, keep the later HRESULT separate because it belongs to another profile field.
Authoritative documentation
Looking for a different code? Search another status or error code.