| 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.
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. 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. One concrete way to reach the condition is that both buffer fields are populated from one UI control.
Decision path
- Record
0xC00D1BCB, 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 that changes only the identified precondition: make the maximum strictly larger while remaining codec-valid.
Codes with similar symptoms but different owners
| Result | Why it differs |
|---|---|
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
Make the maximum strictly larger while remaining codec-valid.
Do not rely on the UI label alone; record the numeric profile fields and codec identity before changing presets.
Discriminating evidence: Capture the maximum video buffer value together with the selected codec, bitrate and source index. The rejected field is the buffer ceiling itself, so changing key-frame spacing or quality percentages is not proof that this boundary was corrected.
Source material
Looking for a different code? Search another status or error code.
