What does HRESULT 0xC00D1BC4 (NS_E_INVALID_VIDEO_HEIGHT) mean?

 
Previous Next
NS_E_INVALID_VIDEO_WIDTH NS_E_INVALID_VIDEO_FPS

NS_E_INVALID_VIDEO_HEIGHT

Where the Encoder produces this result

0xC00D1BC4 (NS_E_INVALID_VIDEO_HEIGHT) identifies output video height fails codec or profile range validation. The important diagnostic boundary is the Encoder object that validates this state; a later “cannot start encoding” dialog can hide that more precise origin.

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.

What has already succeeded

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. In a representative invalid video height case, a cropped height becomes zero after margins are applied. The result observation should be tested at the producing object instead of being treated as a general codec or operating-system failure.

State snapshot to capture

FieldWhat to preserve
Decisive valuesnumeric height, codec, pixel format, interlace flag and alignment requirements
Producing objectaudience 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 correlationthe same source-group generation, audience index, object identity and callback sequence that produced this result
Lower-level evidencethe first COM, driver, file-system or codec HRESULT observed before the Encoder mapped the condition to this result
Controlled comparisona known-good session that changes only the setting named in the invalid video height boundary

How to read the next observation

ObservationHow to interpret it
Observation that supports itThe decisive evidence is numeric height, codec, pixel format, interlace flag and alignment requirements. It confirms output video height fails codec or profile range validation in the same object generation.
Observation that points to an earlier failureThe recorded values satisfy the invalid video height rule, but a source, driver, COM activation or file operation returns a different HRESULT first.
Observation that points to a later failureThe Encoder passes this boundary (output video height fails codec or profile range validation), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correctionApply this isolated change: select a positive supported height or the documented same-as-input value. The original invalid video height 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 height fails codec or profile range validation. In the representative case where a cropped height becomes zero after margins are applied, keep the first failing call and its object identity so a later wrapper cannot replace the invalid video height evidence.

A controlled diagnostic sequence

  1. Record 0xC00D1BC4, it, the Encoder version and the exact API call or property access that returned it.
  2. Export the current .wme or .prx configuration, then capture numeric height, codec, pixel format, interlace flag and alignment requirements.
  3. verify the video stream and audience settings precondition without changing the source, profile and output sink at the same time.
  4. Run one controlled comparison in which only this condition changes: select a positive supported height or the documented same-as-input value.
  5. After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid video height state.

Nearby HRESULTs that mean something else

ResultWhy it is a different boundary
NS_E_INVALID_VIDEO_WIDTHoutput video width fails codec or profile range validation
NS_E_INVALID_VIDEO_FPSoutput frame-rate value is outside the codec/profile constraints
NS_E_INVALID_VIDEO_PEAKRATE_2video peak bitrate is not greater than average bitrate for the selected constrained mode

Corrective action at the right layer

The focused correction is to select a positive supported height or the documented same-as-input value. A retry is useful only after the recorded invalid video height precondition changes.

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.

Technical references


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