What does HRESULT 0xC00D1BCE (NS_E_MULTIPLE_SCRIPT_BITRATES) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

All bit rates must have the same script bit rate.%0

Previous	Next
NS_E_INVALID_VIDEO_HEIGHT_ALIGN	NS_E_INVALID_SCRIPT_BITRATE

NS_E_MULTIPLE_SCRIPT_BITRATES

The failing boundary in the Encoder object model

The useful reading of NS_E_MULTIPLE_SCRIPT_BITRATES (0xC00D1BCE) is not merely the standard message shown above. It locates script-stream bitrate differs across audiences in one profile inside profile, audience and stream topology.

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.

Evidence that separates this code from a wrapper error

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. For example, only the highest audience is edited after adding a script stream. Preserve the result distinction before a UI layer converts the result into a broad start, capture or profile failure.

Field	What to preserve
Decisive values	script bitrate for every audience and source index
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 script bitrates boundary

Interpret the next measurement

Observation	How to interpret it
Observation that supports it	The decisive evidence is script bitrate for every audience and source index. It confirms script-stream bitrate differs across audiences in one profile in the same object generation.
Observation that points to an earlier failure	The recorded values satisfy the multiple script bitrates 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 (script-stream bitrate differs across audiences in one profile), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correction	Apply this isolated change: use one common script bitrate across the profile. The original multiple script bitrates 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 script-stream bitrate differs across audiences in one profile. In the representative case where only the highest audience is edited after adding a script stream, keep the first failing call and its object identity so a later wrapper cannot replace the multiple script bitrates evidence.

Test the condition without rewriting the session

Record 0xC00D1BCE, it, the Encoder version and the exact API call or property access that returned it.
Export the current .wme or .prx configuration, then capture script bitrate for every audience and source index.
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 common script bitrate across the profile.
After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier multiple script bitrates state.

Interpret neighboring results carefully

Result	Why it is a different boundary
`NS_E_MULTIPLE_VIDEO_CODECS`	audiences choose different video codecs for the same source
`NS_E_INVALID_SCRIPT_BITRATE`	script-stream bitrate is outside the accepted range
`NS_E_MULTIPLE_AUDIO_CODECS`	audiences choose different audio codecs for the same audio source

Resolution and verification

The direct repair for this occurrence is to use one common script bitrate across the profile. Recreate the affected source group, profile or output object, repeat the same operation, and confirm that the first failing HRESULT no longer comes from the multiple script bitrates checkpoint.

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.

References for the boundary

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