| Previous | Next |
| NS_E_INVALID_VIDEO_BUFFERMAX_2 | NS_E_INVALID_VIDEO_HEIGHT_ALIGN |
NS_E_INVALID_VIDEO_WIDTH_ALIGN
Diagnostic meaning beyond the standard text
For NS_E_INVALID_VIDEO_WIDTH_ALIGN (0xC00D1BCC), the actionable event is output width violates the selected codec or interlaced-mode alignment. Keep the result producing boundary attached to the original Encoder callback or COM call.
Why the session can reach this point
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. One concrete way to reach the condition is that an odd crop produces a width not divisible by the codec block requirement. 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 | width, required alignment, codec and interlace mode |
| 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 align boundary |
Decision matrix
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is width, required alignment, codec and interlace mode. It confirms output width violates the selected codec or interlaced-mode alignment in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the invalid video width align 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 width violates the selected codec or interlaced-mode alignment), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: round or choose width to the required multiple without altering aspect ratio accidentally. The original invalid video width align 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 width violates the selected codec or interlaced-mode alignment. In the representative case where an odd crop produces a width not divisible by the codec block requirement, keep the first failing call and its object identity so a later wrapper cannot replace the invalid video width align evidence.
Decision path
- Record
0xC00D1BCC, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture width, required alignment, codec and interlace mode. - 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: round or choose width to the required multiple without altering aspect ratio accidentally.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid video width align state.
Codes with similar symptoms but different owners
| Result | Why it is a different boundary |
|---|---|
NS_E_INVALID_VIDEO_BUFFERMAX_2 | maximum video buffer is not greater than the ordinary video buffer |
NS_E_INVALID_VIDEO_HEIGHT_ALIGN | output height violates codec or format alignment |
NS_E_INVALID_VIDEO_BUFFERMAX | maximum video buffer value is outside the accepted range |
Safe recovery
Resolve the producing condition by ensuring that you round or choose width to the required multiple without altering aspect ratio accidentally. Then rebuild only the portion of the Encoder graph affected by it and verify the original call.
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.
Source material
- 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.