| Previous | Next |
| NS_E_UNSUPPORTED_SOURCETYPE | NS_E_TOO_MANY_VIDEO |
NS_E_TOO_MANY_AUDIO
The failing boundary in the Encoder object model
The useful reading of NS_E_TOO_MANY_AUDIO (0xC00D1B5C) is not merely the standard message shown above. It locates enforcement of the source-group limit for audio inputs 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, AutoSetFileSource creates an audio source and application code adds a second one. Preserve the result distinction before a UI layer converts the result into a broad start, capture or profile failure.
| Field | What to preserve |
|---|---|
| Decisive values | audio source count in the target group and the code path that adds or auto-detects each input |
| 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 too many audio boundary |
Interpret the next measurement
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is audio source count in the target group and the code path that adds or auto-detects each input. It confirms enforcement of the source-group limit for audio inputs in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the too many audio 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 (enforcement of the source-group limit for audio inputs), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: keep one audio source in the group or mix sources before they reach Windows Media Encoder. The original too many audio 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 enforcement of the source-group limit for audio inputs. In the representative case where AutoSetFileSource creates an audio source and application code adds a second one, keep the first failing call and its object identity so a later wrapper cannot replace the too many audio evidence.
Test the condition without rewriting the session
- Record
0xC00D1B5C, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture audio source count in the target group and the code path that adds or auto-detects each input. - 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: keep one audio source in the group or mix sources before they reach Windows Media Encoder.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier too many audio state.
Interpret neighboring results carefully
| Result | Why it is a different boundary |
|---|---|
NS_E_UNSUPPORTED_SOURCETYPE | dispatch from the configured source type to an Encoder source plug-in |
NS_E_TOO_MANY_VIDEO | enforcement of the source-group limit for video inputs |
NS_E_NOMATCHING_MEDIASOURCE | selection of a source stream whose media type matches the requested source kind |
Resolution and verification
The direct repair for this occurrence is to keep one audio source in the group or mix sources before they reach Windows Media Encoder. 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 too many audio 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
- 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.