| Previous | Next |
| NS_E_INVALID_PIXEL_ASPECT_RATIO | NS_E_INVALID_PROFILE_CONTENTTYPE |
NS_E_AUDIENCE__LANGUAGE_CONTENTTYPE_MISMATCH
How to interpret the code in a real encoding session
0xC00D1BE3 is named NS_E_AUDIENCE__LANGUAGE_CONTENTTYPE_MISMATCH. Its practical scope is different-language streams in one audience do not share compatible media properties, which belongs to profile, audience and stream topology rather than to every part of Windows Media playback or Windows itself.
Mechanism and point of failure
A Windows Media Encoder profile declares content types and one or more audiences in a session that returns this result. 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.
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 this result. A typical reproduction is: alternate-language audio tracks use different codecs in the same audience. This makes the first result from the Encoder more valuable than a later generic message.
Reproduction matrix
| Field | What to preserve |
|---|---|
| Decisive values | language entries, stream type, codec/format and source index within the 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 this result |
| Lower-level evidence | the first COM, driver, file-system or codec HRESULT observed before the Encoder mapped the condition to this result |
| Controlled comparison | a known-good session that changes only the setting named in the audience language contenttype mismatch boundary |
Evidence matrix
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is language entries, stream type, codec/format and source index within the audience. It confirms different-language streams in one audience do not share compatible media properties in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the audience language contenttype 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 (different-language streams in one audience do not share compatible media properties), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: make language variants use the same stream properties required by that audience. The original audience language contenttype mismatch call should then advance past the same checkpoint. |
The operational impact of it is limited to the profile, audience and stream topology transition that owns different-language streams in one audience do not share compatible media properties. In the representative case where alternate-language audio tracks use different codecs in the same audience, keep the first failing call and its object identity so a later wrapper cannot replace the audience language contenttype mismatch evidence.
Minimal experiment
- Record
0xC00D1BE3, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture language entries, stream type, codec/format and source index within the audience. - 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: make language variants use the same stream properties required by that audience.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier audience language contenttype mismatch state.
Do not collapse these results together
| Result | Why it is a different boundary |
|---|---|
NS_E_INVALID_FILE_BITRATE | file-transfer stream bitrate is invalid for the profile |
NS_E_INVALID_PROFILE_CONTENTTYPE | profile ContentType declares no usable audio or video stream |
NS_E_MULTIPLE_FILE_BITRATES | file-transfer stream bitrate differs across audiences |
What to change—and what to leave alone
Change the smallest responsible precondition: make language variants use the same stream properties required by that audience. While retesting it, keep all unrelated source, audience and output values fixed until the same call is repeated.
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 it.
Authoritative documentation
- 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.