| Previous | Next |
| NS_E_INVALID_NONSQUAREPIXEL_COMPAT | NS_E_CANNOT_GENERATE_BROADCAST_INFO_FOR_QUALITYVBR |
NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL
Where the Encoder produces this result
0xC00D1BDE (NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL) identifies device control is attached to a source that is not a capture device. For NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL, the important diagnostic boundary is the Encoder object that validates this state; a later “cannot start encoding” dialog can hide that more precise origin.
Windows Media Encoder device control coordinates a capture source with a control plug-in, tape transport, mark-in/mark-out entries and an edit decision list in a session that returns NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL. The capture device and the control device must refer to the same usable hardware path at the invalid source with device control checkpoint.
What has already succeeded
Video capture can remain available while the separate control plug-in loses transport control, so a device-control failure is not automatically a capture-format failure in a session that returns NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL. In a representative invalid source with device control case, a file source is paired with a tape-control plug-in. The NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL observation should be tested at the producing object instead of being treated as a general codec or operating-system failure.
State snapshot to capture
| Field | What to preserve |
|---|---|
| Decisive values | source scheme/type, control plug-in and device identity |
| Producing object | control plug-in CLSID, controlled device identifier, transport state, tape presence, EDL entry count, mark-in/mark-out values, seek result, source-group binding and disconnect event |
| Session correlation | the same source-group generation, audience index, object identity and callback sequence that produced NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL |
| Lower-level evidence | the first COM, driver, file-system or codec HRESULT observed before the Encoder mapped the condition to NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL |
| Controlled comparison | a known-good session that changes only the setting named in the invalid source with device control boundary |
How to read the next observation
| Observation | How to interpret it |
|---|---|
| Observation that supports this result | The decisive evidence is source scheme/type, control plug-in and device identity. It confirms device control is attached to a source that is not a capture device in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the invalid source with device control 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 (device control is attached to a source that is not a capture device), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: bind the control plug-in to its capture device or disable control. The original invalid source with device control call should then advance past the same checkpoint. |
The operational impact of NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL is limited to the tape-device control and edit decision lists transition that owns device control is attached to a source that is not a capture device. For NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL, it does not, by itself, prove that every input is corrupt, every codec is missing or the complete Windows Media installation is unusable. In the representative case where a file source is paired with a tape-control plug-in, keep the first failing call and its object identity so a later wrapper cannot replace the invalid source with device control evidence.
A controlled diagnostic sequence
- Record
0xC00D1BDE,NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture source scheme/type, control plug-in and device identity. - For
NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL, verify the tape-device control and edit decision lists precondition without changing the source, profile and output sink at the same time. - Run one controlled comparison in which only this condition changes: bind the control plug-in to its capture device or disable control.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier invalid source with device control state.
Nearby HRESULTs that mean something else
| Result | Why it is a different boundary |
|---|---|
NS_E_END_OF_TAPE | tape transport reaches the recorded end or no usable tape is present |
NS_E_DEVICECONTROL_UNSTABLE | control plug-in reports the tape device is no longer in a reliable command state |
NS_E_ACTIVE_SG_DEVICE_CONTROL_DISCONNECTED | the control device for the active source group disconnects while capture is active |
Corrective action at the right layer
For NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL, the focused correction is to bind the control plug-in to its capture device or disable control. A retry is useful only after the recorded invalid source with device control precondition changes.
Do not rewind, eject or overwrite the tape before recording the failing EDL entry and current timecode; that changes the evidence used to reproduce the seek or end-of-tape condition in a session that returns NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL.
Technical references for NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL
- WMEncEditDecisionList.Item.
- WMTIMECODE device-control structure.
- IWMEncSource.MarkOut.
- Preparing a source group for encoding.
Looking for a different code? Search another status or error code.