| Previous | Next |
| NS_E_TRANSFORM_PLUGIN_INVALID | NS_E_INVALID_VIDEO_WIDTH_FOR_INTERLACED_ENCODING |
NS_E_EDL_REQUIRED_FOR_DEVICE_MULTIPASS
The failing boundary in the Encoder object model
The useful reading of NS_E_EDL_REQUIRED_FOR_DEVICE_MULTIPASS (0xC00D1BE7) is not merely the standard message shown above. It locates device-based two-pass encoding lacks the required nonempty edit decision list inside tape-device control and edit decision lists.
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 this result. The capture device and the control device must refer to the same usable hardware path at the edl required for device multipass checkpoint.
Evidence that separates this code from a wrapper error
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 this result. For example, a live tape device is set to two-pass mode without defining repeatable capture segments. 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 | pass count, device-control state, EDL path and entry count |
| 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 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 edl required for device multipass boundary |
Interpret the next measurement
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is pass count, device-control state, EDL path and entry count. It confirms device-based two-pass encoding lacks the required nonempty edit decision list in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the edl required for device multipass 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-based two-pass encoding lacks the required nonempty edit decision list), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: enable device control and provide an EDL with at least one valid entry. The original edl required for device multipass call should then advance past the same checkpoint. |
The operational impact of it is limited to the tape-device control and edit decision lists transition that owns device-based two-pass encoding lacks the required nonempty edit decision list. In the representative case where a live tape device is set to two-pass mode without defining repeatable capture segments, keep the first failing call and its object identity so a later wrapper cannot replace the edl required for device multipass evidence.
Test the condition without rewriting the session
- Record
0xC00D1BE7, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture pass count, device-control state, EDL path and entry count. - 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: enable device control and provide an EDL with at least one valid entry.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier edl required for device multipass state.
Interpret neighboring results carefully
| Result | Why it is a different boundary |
|---|---|
NS_E_DEVICECONTROL_UNSTABLE | control plug-in reports the tape device is no longer in a reliable command state |
NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL | device control is attached to a source that is not a capture device |
NS_E_END_OF_TAPE | tape transport reaches the recorded end or no usable tape is present |
Resolution and verification
The direct repair for this occurrence is to enable device control and provide an EDL with at least one valid entry. 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 edl stage.
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 it.
References for the boundary
- 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.