| Previous | Next |
| NS_E_TOO_MANY_VIDEO | NS_E_MISMATCHED_MEDIACONTENT |
NS_E_NOMATCHING_ELEMENT
Diagnostic meaning beyond the standard text
For NS_E_NOMATCHING_ELEMENT (0xC00D1B5E), the actionable event is lookup of an Encoder object in a collection by index, name or expected media role. Keep the result producing boundary attached to the original Encoder callback or COM call.
Why the session can reach this point
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.
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. One concrete way to reach the condition is that a saved index is reused after an audience or source group was removed. 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
| Field | What to preserve |
|---|---|
| Decisive values | collection count, requested index or name and the object identities returned during enumeration |
| Producing object | source-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 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 nomatching element boundary |
Decision matrix
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is collection count, requested index or name and the object identities returned during enumeration. It confirms lookup of an Encoder object in a collection by index, name or expected media role in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the nomatching element 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 (lookup of an Encoder object in a collection by index, name or expected media role), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: refresh the collection and use an existing element from the same object generation. The original nomatching element 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 lookup of an Encoder object in a collection by index, name or expected media role. In the representative case where a saved index is reused after an audience or source group was removed, keep the first failing call and its object identity so a later wrapper cannot replace the nomatching element evidence.
Decision path
- Record
0xC00D1B5E, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture collection count, requested index or name and the object identities returned during enumeration. - verify the source groups, streams and plug-ins precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison in which only this condition changes: refresh the collection and use an existing element from the same object generation.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier nomatching element state.
Codes with similar symptoms but different owners
| Result | Why it is a different boundary |
|---|---|
NS_E_TOO_MANY_VIDEO | enforcement of the source-group limit for video inputs |
NS_E_MISMATCHED_MEDIACONTENT | comparison of source-group media content with the assigned profile content type |
NS_E_TOO_MANY_AUDIO | enforcement of the source-group limit for audio inputs |
Safe recovery
Resolve the producing condition by ensuring that you refresh the collection and use an existing element from the same object generation. Then rebuild only the portion of the Encoder graph affected by it and verify the original call.
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.
Source material
- Preparing a source group for encoding.
- Retrieving the profile assigned to a source group.
- Retrieving the configured encoder input.
- Saving a Windows Media Encoder configuration.
Looking for a different code? Search another status or error code.