What does HRESULT 0xC00D1BB6 (NS_E_UNCOMP_COMP_COMBINATION) mean?

 
Previous Next
NS_E_MULTIPLE_VBR_AUDIENCES NS_E_MULTIPLE_AUDIO_CODECS

NS_E_UNCOMP_COMP_COMBINATION

Where the Encoder produces this result

0xC00D1BB6 (NS_E_UNCOMP_COMP_COMBINATION) identifies one session mixes compressed and uncompressed streams in an unsupported profile combination. The important diagnostic boundary is the Encoder object that validates this state; a later “cannot start encoding” dialog can hide that more precise origin.

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.

What has already succeeded

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. In a representative uncomp comp combination case, one audience uses uncompressed video while the others use Windows Media Video. The result observation should be tested at the producing object instead of being treated as a general codec or operating-system failure.

State snapshot to capture

FieldWhat to preserve
Decisive valuescodec/compression state for every stream and 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 uncomp comp combination boundary

How to read the next observation

ObservationHow to interpret it
Observation that supports itThe decisive evidence is codec/compression state for every stream and audience. It confirms one session mixes compressed and uncompressed streams in an unsupported profile combination in the same object generation.
Observation that points to an earlier failureThe recorded values satisfy the uncomp comp combination 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 (one session mixes compressed and uncompressed streams in an unsupported profile combination), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correctionApply this isolated change: make the session consistently compressed or uncompressed as required. The original uncomp comp combination 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 one session mixes compressed and uncompressed streams in an unsupported profile combination. In the representative case where one audience uses uncompressed video while the others use Windows Media Video, keep the first failing call and its object identity so a later wrapper cannot replace the uncomp comp combination evidence.

A controlled diagnostic sequence

  1. Record 0xC00D1BB6, 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 codec/compression state for every stream and 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 the session consistently compressed or uncompressed as required.
  5. After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier uncomp comp combination state.

Nearby HRESULTs that mean something else

ResultWhy it is a different boundary
NS_E_MULTIPLE_VBR_AUDIENCESmultiple-bit-rate audiences are combined with a VBR profile mode not supported by that topology
NS_E_MULTIPLE_AUDIO_CODECSaudiences choose different audio codecs for the same audio source
NS_E_NO_PROFILE_NAMEsaving or validating a custom profile without a profile name

Corrective action at the right layer

The focused correction is to make the session consistently compressed or uncompressed as required. A retry is useful only after the recorded uncomp comp combination precondition changes.

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.

Technical references


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