| Previous | Next |
| NS_E_MULTIPLE_SCRIPT_BITRATES | NS_E_MULTIPLE_FILE_BITRATES |
NS_E_INVALID_SCRIPT_BITRATE
Where the Encoder produces this result
0xC00D1BCF (NS_E_INVALID_SCRIPT_BITRATE) identifies script-stream bitrate is outside the accepted range. 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 invalid script bitrate case, a negative or oversized value is read from custom profile XML. 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 | script bitrate, audience totals and script source configuration |
| 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 invalid script bitrate boundary |
How to read the next observation
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is script bitrate, audience totals and script source configuration. It confirms script-stream bitrate is outside the accepted range in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the invalid script bitrate 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 is outside the accepted range), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: set a valid script allocation that fits every audience. The original invalid script bitrate 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 is outside the accepted range. In the representative case where a negative or oversized value is read from custom profile XML, keep the first failing call and its object identity so a later wrapper cannot replace the invalid script bitrate evidence.
A controlled diagnostic sequence
- Record
0xC00D1BCF, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture script bitrate, audience totals and script source configuration. - 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: set a valid script allocation that fits every audience.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid script bitrate state.
Nearby HRESULTs that mean something else
| Result | Why it is a different boundary |
|---|---|
NS_E_MULTIPLE_SCRIPT_BITRATES | script-stream bitrate differs across audiences in one profile |
NS_E_MULTIPLE_FILE_BITRATES | file-transfer stream bitrate differs across audiences |
NS_E_MULTIPLE_VIDEO_CODECS | audiences choose different video codecs for the same source |
Corrective action at the right layer
The focused correction is to set a valid script allocation that fits every audience. A retry is useful only after the recorded invalid script bitrate 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.