| Previous | Next |
| NS_E_INVALID_VIDEO_PEAKRATE_2 | NS_E_INVALID_VIDEO_HEIGHT |
NS_E_INVALID_VIDEO_WIDTH
How to interpret the code in a real encoding session
0xC00D1BC3 is named NS_E_INVALID_VIDEO_WIDTH. Its practical scope is output video width fails codec or profile range validation, which belongs to video stream and audience settings rather than to every part of Windows Media playback or Windows itself.
Mechanism and point of failure
The video profile selects a codec and rate-control mode, then supplies bitrate, peak rate, frame rate, frame size, key-frame spacing, quality, buffer and optional interlace or pixel-aspect settings in a session that returns this result. The codec validates both values and combinations.
A source preview does not prove that the output profile is accepted; output dimensions and rate-control settings are validated by the selected encoder codec in a session that returns this result. A typical reproduction is: a profile template leaves width at an invalid sentinel rather than same-as-input zero. This makes the first result from the Encoder more valuable than a later generic message.
Reproduction matrix
| Field | What to preserve |
|---|---|
| Decisive values | numeric width, codec, pixel format, interlace flag and alignment requirements |
| Producing object | audience index, codec FOURCC/index, VBR mode, width and height, frame rate, average and peak bitrate, buffer values, key-frame interval, quality values, interlace mode and pixel aspect ratio |
| 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 invalid video width boundary |
Evidence matrix
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is numeric width, codec, pixel format, interlace flag and alignment requirements. It confirms output video width fails codec or profile range validation in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the invalid video width 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 (output video width fails codec or profile range validation), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: select a positive width supported by the codec and intended source. The original invalid video width call should then advance past the same checkpoint. |
The operational impact of it is limited to the video stream and audience settings transition that owns output video width fails codec or profile range validation. In the representative case where a profile template leaves width at an invalid sentinel rather than same-as-input zero, keep the first failing call and its object identity so a later wrapper cannot replace the invalid video width evidence.
Minimal experiment
- Record
0xC00D1BC3, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture numeric width, codec, pixel format, interlace flag and alignment requirements. - verify the video stream and audience settings precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison in which only this condition changes: select a positive width supported by the codec and intended source.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid video width state.
Do not collapse these results together
| Result | Why it is a different boundary |
|---|---|
NS_E_INVALID_VIDEO_PEAKRATE_2 | video peak bitrate is not greater than average bitrate for the selected constrained mode |
NS_E_INVALID_VIDEO_HEIGHT | output video height fails codec or profile range validation |
NS_E_INVALID_VIDEO_PEAKRATE | video peak bitrate lies outside the codec or VBR mode's accepted range |
What to change—and what to leave alone
Change the smallest responsible precondition: select a positive width supported by the codec and intended source. While retesting it, keep all unrelated source, audience and output values fixed until the same call is repeated.
Do not rely on the UI label alone; record the numeric profile fields and codec identity before changing presets in a session that returns it.
Authoritative documentation
- Selecting a video codec for an audience.
- IWMEncProfile2.VBRMode.
- IWMEncVideoSource2.Width and live capture sizing.
- Non-square pixel mode in an encoder profile.
Looking for a different code? Search another status or error code.