| Previous | Next |
| NS_E_NO_AUDIO_COMPAT | NS_E_NO_PROFILE_NAME |
NS_E_INVALID_VBR_COMPAT
How to interpret the code in a real encoding session
0xC00D1BB2 is named NS_E_INVALID_VBR_COMPAT. Its practical scope is VBR rate control conflicts with the selected Windows Media Player 7.1 compatibility target, which belongs to legacy player compatibility rules rather than to every part of Windows Media playback or Windows itself.
Mechanism and point of failure
Windows Media Encoder profiles can be checked for compatibility with older Windows Media Player generations in a session that returns this result. VBR, multiple audiences, audio/video format variation, interlace and non-square pixels can move a profile beyond the version 7.1 compatibility envelope.
The profile may be valid for Windows Media 9 or later and still be intentionally rejected when an older compatibility target is required in a session that returns this result. A typical reproduction is: a modern VBR profile is marked for Player 7.1 playback. This makes the first result from the Encoder more valuable than a later generic message.
Reproduction matrix
| Field | What to preserve |
|---|---|
| Decisive values | DetectCompatibility result and VBRMode for each stream |
| Producing object | DetectCompatibility result, target player generation, audience count, VBR mode, codec and format per audience, frame size, interlace flag and non-square-pixel flag |
| 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 compat boundary |
Evidence matrix
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is DetectCompatibility result and VBRMode for each stream. It confirms VBR rate control conflicts with the selected Windows Media Player 7.1 compatibility target in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the invalid vbr compat 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 rate control conflicts with the selected Windows Media Player 7.1 compatibility target), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: use CBR for the legacy target or raise the minimum supported player version. The original invalid vbr compat call should then advance past the same checkpoint. |
The operational impact of it is limited to the legacy player compatibility rules transition that owns VBR rate control conflicts with the selected Windows Media Player 7.1 compatibility target. In the representative case where a modern VBR profile is marked for Player 7.1 playback, keep the first failing call and its object identity so a later wrapper cannot replace the invalid vbr compat evidence.
Minimal experiment
- Record
0xC00D1BB2, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture DetectCompatibility result and VBRMode for each stream. - verify the legacy player compatibility rules precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison in which only this condition changes: use CBR for the legacy target or raise the minimum supported player version.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid vbr compat state.
Do not collapse these results together
| Result | Why it is a different boundary |
|---|---|
NS_E_NO_AUDIO_COMPAT | older-player compatibility check requires an audio stream in the profile |
NS_E_MULTIPLE_AUDIO_FORMATS | audiences use different audio formats while legacy Player 7.1 compatibility is requested |
NS_E_MULTIPLE_VIDEO_SIZES | audiences use different frame sizes while Player 7.1 compatibility is requested |
What to change—and what to leave alone
Change the smallest responsible precondition: use CBR for the legacy target or raise the minimum supported player version. While retesting it, keep all unrelated source, audience and output values fixed until the same call is repeated.
Do not describe a compatibility result as codec corruption; first decide whether support for the older player is a real requirement in a session that returns it.
Authoritative documentation
- Detecting profile compatibility.
- IWMEncProfile2.VBRMode.
- Selecting a video codec for an audience.
- Adding an audience to an encoder profile.
Looking for a different code? Search another status or error code.