| Previous | Next |
| NS_E_INVALID_AUDIO_BUFFERMAX | NS_E_MULTIPLE_VIDEO_SIZES |
NS_E_MULTIPLE_VIDEO_CODECS
Where the Encoder produces this result
0xC00D1BBD (NS_E_MULTIPLE_VIDEO_CODECS) identifies audiences choose different video codecs for the same source. The important diagnostic boundary is the Encoder object that validates this state; a later “cannot start encoding” dialog can hide that more precise origin.
A Windows Media Encoder profile declares content types and one or more audiences in a session that returns this result. Each audience maps source indexes to audio, video, script or file streams and must remain structurally consistent with the other audiences in a multiple-bit-rate profile.
What has already succeeded
Individual fields may be syntactically valid while the complete profile is inconsistent across audiences or does not match the source group in a session that returns this result. In a representative multiple video codecs case, one audience retains an older codec after the others are upgraded. 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 | video codec FOURCC/index per audience |
| Producing object | profile name and content type, audience count and total bitrate, source indexes, stream types, language identifiers, selected audiences and result of IWMEncProfile2.Validate |
| 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 multiple video codecs boundary |
How to read the next observation
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is video codec FOURCC/index per audience. It confirms audiences choose different video codecs for the same source in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the multiple video codecs 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 (audiences choose different video codecs for the same source), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: use one video codec across the complete MBR profile. The original multiple video codecs call should then advance past the same checkpoint. |
The operational impact of it is limited to the profile, audience and stream topology transition that owns audiences choose different video codecs for the same source. In the representative case where one audience retains an older codec after the others are upgraded, keep the first failing call and its object identity so a later wrapper cannot replace the multiple video codecs evidence.
A controlled diagnostic sequence
- Record
0xC00D1BBD, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture video codec FOURCC/index per audience. - verify the profile, audience and stream topology precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison in which only this condition changes: use one video codec across the complete MBR profile.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier multiple video codecs state.
Nearby HRESULTs that mean something else
| Result | Why it is a different boundary |
|---|---|
NS_E_MULTIPLE_AUDIO_CODECS | audiences choose different audio codecs for the same audio source |
NS_E_MULTIPLE_SCRIPT_BITRATES | script-stream bitrate differs across audiences in one profile |
NS_E_UNCOMP_COMP_COMBINATION | one session mixes compressed and uncompressed streams in an unsupported profile combination |
Corrective action at the right layer
The focused correction is to use one video codec across the complete MBR profile. A retry is useful only after the recorded multiple video codecs precondition changes.
Do not repair a profile by deleting arbitrary audiences; export the.prx first and compare the same source index across every audience in a session that returns it.
Technical references
- Adding an audience to an encoder profile.
- IWMEncAudienceObj.TotalBitrate.
- Retrieving the profile assigned to a source group.
- Detecting profile compatibility.
Looking for a different code? Search another status or error code.