Site icon EfmSoft

What does HRESULT 0xC00D1B99 (NS_E_AUDIENCE_CONTENTTYPE_MISMATCH) mean?

 
Previous Next
NS_E_MISSING_AUDIENCE NS_E_MISSING_SOURCE_INDEX

NS_E_AUDIENCE_CONTENTTYPE_MISMATCH

How to interpret the code in a real encoding session

0xC00D1B99 is named NS_E_AUDIENCE_CONTENTTYPE_MISMATCH. Its practical scope is audiences in one output tree declare different overall media content types, 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: one MBR audience omits video while the others contain audio and video. This makes the first result from the Encoder more valuable than a later generic message.

Reproduction matrix

FieldWhat to preserve
Decisive valuesContentType and stream presence for every audience
Producing objectprofile name and content type, audience count and total bitrate, source indexes, stream types, language identifiers, selected audiences and result of IWMEncProfile2.Validate
Session correlationthe same source-group generation, audience index, object identity and callback sequence that produced this result
Lower-level evidencethe first COM, driver, file-system or codec HRESULT observed before the Encoder mapped the condition to this result
Controlled comparisona known-good session that changes only the setting named in the audience contenttype mismatch boundary

Evidence matrix

ObservationHow to interpret it
Observation that supports itThe decisive evidence is ContentType and stream presence for every audience. It confirms audiences in one output tree declare different overall media content types in the same object generation.
Observation that points to an earlier failureThe recorded values satisfy the audience contenttype mismatch rule, but a source, driver, COM activation or file operation returns a different HRESULT first.
Observation that points to a later failureThe Encoder passes this boundary (audiences in one output tree declare different overall media content types), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correctionApply this isolated change: make all audiences represent the same audio/video/script/file content topology. The original audience 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 audiences in one output tree declare different overall media content types. In the representative case where one MBR audience omits video while the others contain audio and video, keep the first failing call and its object identity so a later wrapper cannot replace the audience contenttype mismatch evidence.

Minimal experiment

  1. Record 0xC00D1B99, it, the Encoder version and the exact API call or property access that returned it.
  2. Export the current .wme or .prx configuration, then capture ContentType and stream presence for every audience.
  3. verify the profile, audience and stream topology precondition without changing the source, profile and output sink at the same time.
  4. Run one controlled comparison in which only this condition changes: make all audiences represent the same audio/video/script/file content topology.
  5. After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier audience contenttype mismatch state.

Do not collapse these results together

ResultWhy it is a different boundary
NS_E_MISSING_AUDIENCEan output-tree reference points to an audience that is absent
NS_E_MISSING_SOURCE_INDEXan audience stream lacks a source index mapping
NS_E_PROFILE_MISMATCHswitching or combining sources whose assigned profiles are not equivalent for the session

What to change—and what to leave alone

Change the smallest responsible precondition: make all audiences represent the same audio/video/script/file content topology. 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


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

Exit mobile version