| Previous | Next |
| NS_E_INVALID_VIDEO_BUFFERMAX | NS_E_INVALID_VIDEO_WIDTH_ALIGN |
NS_E_INVALID_VIDEO_BUFFERMAX_2
Diagnostic meaning beyond the standard text
For NS_E_INVALID_VIDEO_BUFFERMAX_2 (0xC00D1BCB), the actionable event is maximum video buffer is not greater than the ordinary video buffer. 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 at the invalid video buffermax 2 checkpoint.
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 both buffer fields are populated from one UI control. 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 | video buffer and maximum buffer values in the same audience |
| 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 buffermax 2 boundary |
Decision matrix
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is video buffer and maximum buffer values in the same audience. It confirms maximum video buffer is not greater than the ordinary video buffer in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the invalid video buffermax 2 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 (maximum video buffer is not greater than the ordinary video buffer), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: make the maximum strictly larger while remaining codec-valid. The original invalid video buffermax 2 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 maximum video buffer is not greater than the ordinary video buffer. In the representative case where both buffer fields are populated from one UI control, keep the first failing call and its object identity so a later wrapper cannot replace the invalid video buffermax 2 evidence.
Decision path
- Record
0xC00D1BCB, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture video buffer and maximum buffer values in the same audience. - 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: make the maximum strictly larger while remaining codec-valid.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid video buffermax 2 state.
Codes with similar symptoms but different owners
| Result | Why it is a different boundary |
|---|---|
NS_E_INVALID_VIDEO_BUFFERMAX | maximum video buffer value is outside the accepted range |
NS_E_INVALID_VIDEO_WIDTH_ALIGN | output width violates the selected codec or interlaced-mode alignment |
NS_E_INVALID_VIDEO_BUFFER | video buffer setting is invalid for the selected codec and bitrate mode |
Safe recovery
Resolve the producing condition by ensuring that you make the maximum strictly larger while remaining codec-valid. 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.