What does HRESULT 0xC00D1BD0 (NS_E_MULTIPLE_FILE_BITRATES) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

All bit rates must have the same file transfer bit rate.%0

Previous	Next
NS_E_INVALID_SCRIPT_BITRATE	NS_E_INVALID_FILE_BITRATE

NS_E_MULTIPLE_FILE_BITRATES

Where the Encoder produces this result

0xC00D1BD0 (NS_E_MULTIPLE_FILE_BITRATES) identifies file-transfer stream bitrate differs across audiences. This is an Encoder validation error; a later “cannot start encoding” dialog can hide the original HRESULT.

A Windows Media Encoder profile declares content types and one or more audiences. 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. For example, a file stream is added after audiences were configured independently. Reproduce the condition at the Encoder object that returned the HRESULT rather than treating it as a general codec or operating-system failure.

A controlled diagnostic sequence

Record 0xC00D1BD0, the Encoder version and the exact API call or property access that returned it.
Export the current .wme or .prx configuration, then capture file bitrate for each 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 that changes only the identified precondition: use one common file-transfer bitrate across audiences.

Nearby HRESULTs that mean something else

Result	Why it differs
`NS_E_INVALID_SCRIPT_BITRATE`	script-stream bitrate is outside the accepted range
`NS_E_INVALID_FILE_BITRATE`	file-transfer stream bitrate is invalid for the profile
`NS_E_MULTIPLE_SCRIPT_BITRATES`	script-stream bitrate differs across audiences in one profile

Corrective action at the right layer

To correct this, use one common file-transfer bitrate across audiences. A retry is useful only after the recorded multiple file bitrates precondition changes.

Do not repair a profile by deleting arbitrary audiences; export the .prx profile first and compare the same source index across every audience.

Discriminating evidence: Compare the file-transfer stream bitrate for the same source across all audiences and retain the per-audience values. This status is about conflicting file-stream rates, not about multiple video codecs, script rates, or a single out-of-range bitrate.

Technical references

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