What does HRESULT 0xC00D1B9A (NS_E_MISSING_SOURCE_INDEX) mean?

 
Previous Next
NS_E_AUDIENCE_CONTENTTYPE_MISMATCH NS_E_NUM_LANGUAGE_MISMATCH

NS_E_MISSING_SOURCE_INDEX

Diagnostic meaning beyond the standard text

For NS_E_MISSING_SOURCE_INDEX (0xC00D1B9A), the actionable event is an audience stream lacks a source index mapping. Keep the result producing boundary attached to the original Encoder callback or COM call.

Why the session can reach this point

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.

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. One concrete way to reach the condition is that a manually edited.prx contains a video stream node without its source index. The result test should therefore preserve the object generation and numeric settings, not just a screenshot of the final dialog.

Trace fields with diagnostic value

FieldWhat to preserve
Decisive valuesaudience and stream type, source index property and available source streams
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 missing source index boundary

Decision matrix

ObservationHow to interpret it
Observation that supports itThe decisive evidence is audience and stream type, source index property and available source streams. It confirms an audience stream lacks a source index mapping in the same object generation.
Observation that points to an earlier failureThe recorded values satisfy the missing source 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 stream lacks a source index mapping), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correctionApply this isolated change: assign the stream to a valid source index consistently across audiences. The original missing source 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 stream lacks a source index mapping. In the representative case where a manually edited.prx contains a video stream node without its source index, keep the first failing call and its object identity so a later wrapper cannot replace the missing source index evidence.

Decision path

  1. Record 0xC00D1B9A, 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 audience and stream type, source index property and available source streams.
  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: assign the stream to a valid source index consistently across audiences.
  5. After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier missing source index state.

Codes with similar symptoms but different owners

ResultWhy it is a different boundary
NS_E_AUDIENCE_CONTENTTYPE_MISMATCHaudiences in one output tree declare different overall media content types
NS_E_NUM_LANGUAGE_MISMATCHthe same source index exposes different language counts across audiences
NS_E_MISSING_AUDIENCEan output-tree reference points to an audience that is absent

Safe recovery

Resolve the producing condition by ensuring that you assign the stream to a valid source index consistently across audiences. Then rebuild only the portion of the Encoder graph affected by it and verify the original call.

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.

Source material


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