What does HRESULT 0xC00D1B9E (NS_E_INVALID_INPUT_AUDIENCE_INDEX) mean?

 
Previous Next
NS_E_VBRMODE_MISMATCH NS_E_INVALID_INPUT_LANGUAGE

NS_E_INVALID_INPUT_AUDIENCE_INDEX

The failing boundary in the Encoder object model

The useful reading of NS_E_INVALID_INPUT_AUDIENCE_INDEX (0xC00D1B9E) is not merely the standard message shown above. It locates an audience index supplied to profile or input mapping is outside the collection 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, code caches index 2 after the profile is reduced to two audiences. Preserve the result distinction before a UI layer converts the result into a broad start, capture or profile failure.

FieldWhat to preserve
Decisive valuesrequested index, AudienceCount and collection generation
Producing objectprofile name and content type, audience count and total bitrate, source indexes, stream types, language identifiers, selected audiences and result of IWMEncProfile2.Validate
Session correlationthe same source-group generation, audience index, object identity and callback sequence that produced this result
Lower-level evidencethe first COM, driver, file-system or codec HRESULT observed before the Encoder mapped the condition to this result
Controlled comparisona known-good session that changes only the setting named in the invalid input audience index boundary

Interpret the next measurement

ObservationHow to interpret it
Observation that supports itThe decisive evidence is requested index, AudienceCount and collection generation. It confirms an audience index supplied to profile or input mapping is outside the collection in the same object generation.
Observation that points to an earlier failureThe recorded values satisfy the invalid input audience index rule, but a source, driver, COM activation or file operation returns a different HRESULT first.
Observation that points to a later failureThe Encoder passes this boundary (an audience index supplied to profile or input mapping is outside the collection), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correctionApply this isolated change: use an index from the current audience collection after refreshing it. The original invalid input audience index 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 an audience index supplied to profile or input mapping is outside the collection. In the representative case where code caches index 2 after the profile is reduced to two audiences, keep the first failing call and its object identity so a later wrapper cannot replace the invalid input audience index evidence.

Test the condition without rewriting the session

  1. Record 0xC00D1B9E, it, the Encoder version and the exact API call or property access that returned it.
  2. Export the current .wme or .prx configuration, then capture requested index, AudienceCount and collection generation.
  3. verify the profile, audience and stream topology precondition without changing the source, profile and output sink at the same time.
  4. Run one controlled comparison in which only this condition changes: use an index from the current audience collection after refreshing it.
  5. After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid input audience index state.

Interpret neighboring results carefully

ResultWhy it is a different boundary
NS_E_VBRMODE_MISMATCHthe same source index uses different rate-control modes across audiences
NS_E_INVALID_INPUT_LANGUAGEa language value or language index supplied for an input stream is not accepted
NS_E_LANGUAGE_MISMATCHlanguage identifiers differ across audiences for the same source index

Resolution and verification

The direct repair for this occurrence is to use an index from the current audience collection after refreshing it. 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 invalid input audience index 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.