What does HRESULT 0xC00D1BB4 (NS_E_INVALID_VBR_WITH_UNCOMP) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

It is not possible to use a VBR encoding mode with uncompressed audio or video.%0

Previous	Next
NS_E_NO_PROFILE_NAME	NS_E_MULTIPLE_VBR_AUDIENCES

NS_E_INVALID_VBR_WITH_UNCOMP

Where the Encoder produces this result

0xC00D1BB4 (NS_E_INVALID_VBR_WITH_UNCOMP) identifies VBR mode is combined with an uncompressed audio or video stream. 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 audio part of an encoder profile combines source format, codec, bitrate mode, average and peak rates, buffer limits and channel layout in a session that returns this result. Multiple audiences impose cross-audience consistency rules in addition to per-field ranges.

What has already succeeded

A codec can be installed and still reject the selected format or bitrate combination; codec presence and profile validity are different tests in a session that returns this result. In a representative invalid vbr with uncomp case, PCM audio is left uncompressed while the profile enables VBR globally. 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

Field	What to preserve
Decisive values	stream codec selection and VBRMode for each stream
Producing object	source WAVEFORMATEX, audience index, audio codec and format indexes, VBR mode, average/peak bitrate, buffer size, channel count, language and compatibility target
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 vbr with uncomp boundary

How to read the next observation

Observation	How to interpret it
Observation that supports it	The decisive evidence is stream codec selection and VBRMode for each stream. It confirms VBR mode is combined with an uncompressed audio or video stream in the same object generation.
Observation that points to an earlier failure	The recorded values satisfy the invalid vbr with uncomp 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 (VBR mode is combined with an uncompressed audio or video stream), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correction	Apply this isolated change: use compression with VBR or select a non-VBR mode for uncompressed output. The original invalid vbr with uncomp call should then advance past the same checkpoint.

The operational impact of it is limited to the audio stream and audience settings transition that owns VBR mode is combined with an uncompressed audio or video stream. In the representative case where PCM audio is left uncompressed while the profile enables VBR globally, keep the first failing call and its object identity so a later wrapper cannot replace the invalid vbr with uncomp evidence.

A controlled diagnostic sequence

Record 0xC00D1BB4, it, the Encoder version and the exact API call or property access that returned it.
Export the current .wme or .prx configuration, then capture stream codec selection and VBRMode for each stream.
verify the audio 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: use compression with VBR or select a non-VBR mode for uncompressed output.
After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid vbr with uncomp state.

Nearby HRESULTs that mean something else

Result	Why it is a different boundary
`NS_E_INPUT_WAVFORMAT_MISMATCH`	multiple WAV inputs used together do not share one WAVEFORMATEX
`NS_E_AUDIO_BITRATE_STEPDOWN`	audio bitrate ordering is inconsistent with ascending total audience bitrate
`NS_E_EXPECT_MONO_WAV_INPUT`	voice-analysis or optimization input requires a single-channel WAV source

Corrective action at the right layer

The focused correction is to use compression with VBR or select a non-VBR mode for uncompressed output. A retry is useful only after the recorded invalid vbr with uncomp precondition changes.

Do not substitute a different codec before saving the exact profile values rejected by validation; otherwise the incompatible combination cannot be identified in a session that returns it.

Technical references

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