| Previous | Next |
| NS_E_VIDCAPSTARTFAILED | NS_E_VIDSOURCESIZE |
NS_E_VIDSOURCECOMPRESSION
Where the Encoder produces this result
0xC00D1B6A (NS_E_VIDSOURCECOMPRESSION) identifies agreement on output compression or color depth from the video source. The important diagnostic boundary is the Encoder object that validates this state; a later “cannot start encoding” dialog can hide that more precise origin.
A live video source passes through device opening, capture-format negotiation, optional clipping and preview-window setup before an encoder codec accepts the frames in a session that returns this result. Width, height, pixel format and driver state belong to this boundary at the vidsourcecompression checkpoint.
What has already succeeded
Seeing a device in enumeration or obtaining a preview frame does not establish that the requested capture format can be delivered continuously to the encoder in a session that returns this result. In a representative vidsourcecompression case, a camera offers YUY2 but the session requests an unsupported RGB depth directly. The result 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 | requested subtype/FOURCC, bit depth, native device formats and the compressor input requirements |
| Producing object | device moniker, driver version, requested and native width/height, frame rate, BITMAPINFOHEADER compression and bit depth, preview state, source-plug-in result and first driver error |
| 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 vidsourcecompression boundary |
How to read the next observation
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is requested subtype/FOURCC, bit depth, native device formats and the compressor input requirements. It confirms agreement on output compression or color depth from the video source in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the vidsourcecompression 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 (agreement on output compression or color depth from the video source), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: select a source pixel format and color depth accepted by the capture device and downstream codec. The original vidsourcecompression call should then advance past the same checkpoint. |
The operational impact of it is limited to the video capture and compressor negotiation transition that owns agreement on output compression or color depth from the video source. In the representative case where a camera offers YUY2 but the session requests an unsupported RGB depth directly, keep the first failing call and its object identity so a later wrapper cannot replace the vidsourcecompression evidence.
A controlled diagnostic sequence
- Record
0xC00D1B6A, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture requested subtype/FOURCC, bit depth, native device formats and the compressor input requirements. - verify the video capture and compressor negotiation precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison in which only this condition changes: select a source pixel format and color depth accepted by the capture device and downstream codec.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier vidsourcecompression state.
Nearby HRESULTs that mean something else
| Result | Why it is a different boundary |
|---|---|
NS_E_VIDCAPSTARTFAILED | transition of the configured video capture graph into streaming state |
NS_E_VIDSOURCESIZE | negotiation of live capture width and height with the source device |
NS_E_VIDEODRIVER_UNSTABLE | driver state after an unrecoverable capture failure makes further graph use unsafe |
Corrective action at the right layer
The focused correction is to select a source pixel format and color depth accepted by the capture device and downstream codec. A retry is useful only after the recorded vidsourcecompression precondition changes.
Do not keep retrying an unstable capture driver in the same process after preserving the first error; close the graph and test one known-native format in a fresh process in a session that returns it.
Technical references
- IWMEncVideoSource2.Width and live capture sizing.
- BITMAPINFOHEADER structure.
- ICCompressQuery video-compressor format check.
- Retrieving the configured encoder input.
Looking for a different code? Search another status or error code.