What does HRESULT 0xC00D1BBE (NS_E_MULTIPLE_VIDEO_SIZES) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

All audiences should use the same video size to be compatible with Windows Media Player 7.1.%0

Previous	Next
NS_E_MULTIPLE_VIDEO_CODECS	NS_E_INVALID_VIDEO_BITRATE

NS_E_MULTIPLE_VIDEO_SIZES

The failing boundary in the Encoder object model

The useful reading of NS_E_MULTIPLE_VIDEO_SIZES (0xC00D1BBE) is not merely the standard message shown above. It locates audiences use different frame sizes while Player 7.1 compatibility is requested inside legacy player compatibility rules.

Windows Media Encoder profiles can be checked for compatibility with older Windows Media Player generations in a session that returns this result. VBR, multiple audiences, audio/video format variation, interlace and non-square pixels can move a profile beyond the version 7.1 compatibility envelope.

Evidence that separates this code from a wrapper error

The profile may be valid for Windows Media 9 or later and still be intentionally rejected when an older compatibility target is required in a session that returns this result. For example, an MBR profile scales video by audience but is marked compatible with Player 7.1. Preserve the result distinction before a UI layer converts the result into a broad start, capture or profile failure.

Field	What to preserve
Decisive values	width/height per audience and compatibility target
Producing object	DetectCompatibility result, target player generation, audience count, VBR mode, codec and format per audience, frame size, interlace flag and non-square-pixel flag
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 multiple video sizes boundary

Interpret the next measurement

Observation	How to interpret it
Observation that supports it	The decisive evidence is width/height per audience and compatibility target. It confirms audiences use different frame sizes while Player 7.1 compatibility is requested in the same object generation.
Observation that points to an earlier failure	The recorded values satisfy the multiple video sizes 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 (audiences use different frame sizes while Player 7.1 compatibility is requested), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correction	Apply this isolated change: use one common frame size or target a player version that supports the profile. The original multiple video sizes call should then advance past the same checkpoint.

The operational impact of it is limited to the legacy player compatibility rules transition that owns audiences use different frame sizes while Player 7.1 compatibility is requested. In the representative case where an MBR profile scales video by audience but is marked compatible with Player 7.1, keep the first failing call and its object identity so a later wrapper cannot replace the multiple video sizes evidence.

Test the condition without rewriting the session

Record 0xC00D1BBE, it, the Encoder version and the exact API call or property access that returned it.
Export the current .wme or .prx configuration, then capture width/height per audience and compatibility target.
verify the legacy player compatibility rules 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 common frame size or target a player version that supports the profile.
After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier multiple video sizes state.

Interpret neighboring results carefully

Result	Why it is a different boundary
`NS_E_MULTIPLE_AUDIO_FORMATS`	audiences use different audio formats while legacy Player 7.1 compatibility is requested
`NS_E_INVALID_INTERLACE_COMPAT`	interlace preservation conflicts with the Player 7.1 compatibility target
`NS_E_INVALID_VBR_COMPAT`	VBR rate control conflicts with the selected Windows Media Player 7.1 compatibility target

Resolution and verification

The direct repair for this occurrence is to use one common frame size or target a player version that supports the profile. 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 multiple video sizes checkpoint.

Do not describe a compatibility result as codec corruption; first decide whether support for the older player is a real requirement in a session that returns it.

References for the boundary

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