HRESULT 0xC00D1B9D (NS_E_VBRMODE_MISMATCH): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The same source index in different audiences should use the same VBR encoding mode.%0

Previous	Next
NS_E_LANGUAGE_MISMATCH	NS_E_INVALID_INPUT_AUDIENCE_INDEX

NS_E_VBRMODE_MISMATCH

Diagnostic meaning beyond the standard text

For NS_E_VBRMODE_MISMATCH (0xC00D1B9D), the actionable event is the same source index uses different rate-control modes across audiences. Keep the result producing boundary attached to the original Encoder callback or COM call.

Why the session can reach this point

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. One concrete way to reach the condition is that one audience is CBR while another uses constrained VBR for the same video source. The result test should therefore preserve the object generation and numeric settings, not just a screenshot of the final dialog.

Trace fields with diagnostic value

Field	What to preserve
Decisive values	source index, stream type and VBRMode for 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 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 vbrmode mismatch boundary

Decision matrix

Observation	How to interpret it
Observation that supports it	The decisive evidence is source index, stream type and VBRMode for every audience. It confirms the same source index uses different rate-control modes across audiences in the same object generation.
Observation that points to an earlier failure	The recorded values satisfy the vbrmode 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 uses different rate-control modes across audiences), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correction	Apply this isolated change: select one common VBR/CBR mode for that source index. The original vbrmode 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 the same source index uses different rate-control modes across audiences. In the representative case where one audience is CBR while another uses constrained VBR for the same video source, keep the first failing call and its object identity so a later wrapper cannot replace the vbrmode mismatch evidence.

Decision path

Record 0xC00D1B9D, it, the Encoder version and the exact API call or property access that returned it.
Export the current .wme or .prx configuration, then capture source index, stream type and VBRMode for every 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: select one common VBR/CBR mode for that source index.
After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier vbrmode mismatch state.

Codes with similar symptoms but different owners

Result	Why it is a different boundary
`NS_E_LANGUAGE_MISMATCH`	language identifiers differ across audiences for the same source index
`NS_E_INVALID_INPUT_AUDIENCE_INDEX`	an audience index supplied to profile or input mapping is outside the collection
`NS_E_NUM_LANGUAGE_MISMATCH`	the same source index exposes different language counts across audiences

Safe recovery

Resolve the producing condition by ensuring that you select one common VBR/CBR mode for that source index. Then rebuild only the portion of the Encoder graph affected by it and verify the original call.

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.

Source material

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