| Previous | Next |
| NS_E_BAD_CONTENTEDL | NS_E_NONSQUAREPIXELMODE_MISMATCH |
NS_E_INTERLACEMODE_MISMATCH
The failing boundary in the Encoder object model
The useful reading of NS_E_INTERLACEMODE_MISMATCH (0xC00D1BAB) is not merely the standard message shown above. It locates the same source index has different interlace modes across audiences inside profile, audience and stream topology.
A Windows Media Encoder profile declares content types and one or more audiences in a session that returns NS_E_INTERLACEMODE_MISMATCH. Each audience maps source indexes to audio, video, script or file streams and must remain structurally consistent with the other audiences in a multiple-bit-rate profile at the interlacemode mismatch checkpoint.
Evidence that separates this code from a wrapper error
Individual fields may be syntactically valid while the complete profile is inconsistent across audiences or does not match the source group in a session that returns NS_E_INTERLACEMODE_MISMATCH. For example, the highest audience preserves interlace while lower audiences encode progressive output. Preserve the NS_E_INTERLACEMODE_MISMATCH distinction before a UI layer converts the result into a broad start, capture or profile failure.
| Field | What to preserve |
|---|---|
| Decisive values | interlace mode for the source index in every audience |
| Producing object | profile name and content type, audience count and total bitrate, source indexes, stream types, language identifiers, selected audiences and result of IWMEncProfile2.Validate |
| Session correlation | the same source-group generation, audience index, object identity and callback sequence that produced NS_E_INTERLACEMODE_MISMATCH |
| Lower-level evidence | the first COM, driver, file-system or codec HRESULT observed before the Encoder mapped the condition to NS_E_INTERLACEMODE_MISMATCH |
| Controlled comparison | a known-good session that changes only the setting named in the interlacemode mismatch boundary |
Interpret the next measurement
| Observation | How to interpret it |
|---|---|
| Observation that supports this result | The decisive evidence is interlace mode for the source index in every audience. It confirms the same source index has different interlace modes across audiences in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the interlacemode mismatch rule, but a source, driver, COM activation or file operation returns a different HRESULT first. |
| Observation that points to a later failure | The Encoder passes this boundary (the same source index has different interlace modes across audiences), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: use one interlace treatment consistently across the MBR audiences. The original interlacemode mismatch call should then advance past the same checkpoint. |
The operational impact of NS_E_INTERLACEMODE_MISMATCH is limited to the profile, audience and stream topology transition that owns the same source index has different interlace modes across audiences. For NS_E_INTERLACEMODE_MISMATCH, it does not, by itself, prove that every input is corrupt, every codec is missing or the complete Windows Media installation is unusable. In the representative case where the highest audience preserves interlace while lower audiences encode progressive output, keep the first failing call and its object identity so a later wrapper cannot replace the interlacemode mismatch evidence.
Test the condition without rewriting the session
- Record
0xC00D1BAB,NS_E_INTERLACEMODE_MISMATCH, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture interlace mode for the source index in every audience. - For
NS_E_INTERLACEMODE_MISMATCH, verify the profile, audience and stream topology precondition without changing the source, profile and output sink at the same time. - Run one controlled comparison in which only this condition changes: use one interlace treatment consistently across the MBR audiences.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier interlacemode mismatch state.
Interpret neighboring results carefully
| Result | Why it is a different boundary |
|---|---|
NS_E_INVALID_INPUT_STREAM | an input stream type or index does not identify a valid source stream |
NS_E_NONSQUAREPIXELMODE_MISMATCH | non-square-pixel mode differs across audiences sharing a source index |
NS_E_INVALID_INPUT_LANGUAGE | a language value or language index supplied for an input stream is not accepted |
Resolution and verification
The direct repair for this occurrence is to use one interlace treatment consistently across the MBR audiences. Recreate the affected source group, profile or output object, repeat the same operation, and confirm that the first failing HRESULT no longer comes from the interlacemode mismatch checkpoint.
Do not repair a profile by deleting arbitrary audiences; export the .prx first and compare the same source index across every audience in a session that returns NS_E_INTERLACEMODE_MISMATCH.
References for the NS_E_INTERLACEMODE_MISMATCH boundary
- Adding an audience to an encoder profile.
- IWMEncAudienceObj.TotalBitrate.
- Retrieving the profile assigned to a source group.
- Detecting profile compatibility.
Looking for a different code? Search another status or error code.