What does HRESULT 0xC00D1B5B (NS_E_UNSUPPORTED_SOURCETYPE) mean?

 
Previous Next
NS_E_NOMATCHING_MEDIASOURCE NS_E_TOO_MANY_AUDIO

NS_E_UNSUPPORTED_SOURCETYPE

The failing boundary in the Encoder object model

The useful reading of NS_E_UNSUPPORTED_SOURCETYPE (0xC00D1B5B) is not merely the standard message shown above. It locates dispatch from the configured source type to an Encoder source plug-in inside source groups, streams and plug-ins.

The Encoder object model groups audio, video and script inputs in an IWMEncSourceGroup, associates one profile with that group, and asks a source plug-in to expose a media format that can feed the selected output streams in a session that returns this result.

Evidence that separates this code from a wrapper error

Successful creation of the COM objects does not prove that the source group is complete; profile assignment, source discovery and format negotiation are later checkpoints in a session that returns this result. For example, automation passes a newer capture-source type to the legacy Encoder 9 object model. Preserve the result distinction before a UI layer converts the result into a broad start, capture or profile failure.

FieldWhat to preserve
Decisive valuesinput scheme, source type enumeration, plug-in CLSID and interfaces returned by GetSourcePlugin
Producing objectsource-group collection index and name, active/prepared state, stream type, input scheme and stream name, source plug-in CLSID, negotiated media type and assigned profile
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 unsupported sourcetype boundary

Interpret the next measurement

ObservationHow to interpret it
Observation that supports itThe decisive evidence is input scheme, source type enumeration, plug-in CLSID and interfaces returned by GetSourcePlugin. It confirms dispatch from the configured source type to an Encoder source plug-in in the same object generation.
Observation that points to an earlier failureThe recorded values satisfy the unsupported sourcetype 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 (dispatch from the configured source type to an Encoder source plug-in), but a codec, archive or broadcast sink then fails in a subsequent stage.
Verification after correctionApply this isolated change: use a source type implemented by the installed Encoder plug-ins or install the intended trusted plug-in. The original unsupported sourcetype call should then advance past the same checkpoint.

The operational impact of it is limited to the source groups, streams and plug-ins transition that owns dispatch from the configured source type to an Encoder source plug-in. In the representative case where automation passes a newer capture-source type to the legacy Encoder 9 object model, keep the first failing call and its object identity so a later wrapper cannot replace the unsupported sourcetype evidence.

Test the condition without rewriting the session

  1. Record 0xC00D1B5B, 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 input scheme, source type enumeration, plug-in CLSID and interfaces returned by GetSourcePlugin.
  3. verify the source groups, streams and plug-ins 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 a source type implemented by the installed Encoder plug-ins or install the intended trusted plug-in.
  5. After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier unsupported sourcetype state.

Interpret neighboring results carefully

ResultWhy it is a different boundary
NS_E_NOMATCHING_MEDIASOURCEselection of a source stream whose media type matches the requested source kind
NS_E_TOO_MANY_AUDIOenforcement of the source-group limit for audio inputs
NS_E_TOO_MANY_VIDEOenforcement of the source-group limit for video inputs

Resolution and verification

The direct repair for this occurrence is to use a source type implemented by the installed Encoder plug-ins or install the intended trusted plug-in. 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 unsupported sourcetype checkpoint.

Do not delete and recreate every source group before exporting the.wme configuration and recording the active group; otherwise the failing object relation is lost in a session that returns it.

References for the boundary


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