| Previous | Next |
| NS_E_TIMECODE_REQUIRES_VIDEOSTREAM | NS_E_INVALID_INTERLACEMODE |
NS_E_NO_MBR_WITH_TIMECODE
Where the Encoder produces this result
0xC00D1BDA (NS_E_NO_MBR_WITH_TIMECODE) identifies generated timecode is combined with multiple-bit-rate audiences. The important diagnostic boundary is the Encoder object that validates this state; a later “cannot start encoding” dialog can hide that more precise origin.
Encoder timecode is tied to a video stream, source capabilities and a selected SMPTE mode in a session that returns this result. Device-control time values include frame-rate and frame-count information, while generated timecode adds compatibility constraints for multiple source groups and MBR profiles.
What has already succeeded
A source can produce video frames but still lack usable device timecode or violate the topology required for generated timecode in a session that returns this result. In a representative no mbr with timecode case, an MBR profile is selected after timecode was enabled. 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 | AudienceCount, timecode mode and output topology |
| Producing object | EnableTimecode flag, StartingTimecode, SMPTE mode, frame rate, drop-frame setting, source support, source-group count, audience count and first timecode sample |
| 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 no mbr with timecode boundary |
How to read the next observation
| Observation | How to interpret it |
|---|---|
| Observation that supports it | The decisive evidence is AudienceCount, timecode mode and output topology. It confirms generated timecode is combined with multiple-bit-rate audiences in the same object generation. |
| Observation that points to an earlier failure | The recorded values satisfy the no mbr with timecode 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 (generated timecode is combined with multiple-bit-rate audiences), but a codec, archive or broadcast sink then fails in a subsequent stage. |
| Verification after correction | Apply this isolated change: use a single audience for generated timecode or disable the feature. The original no mbr with timecode call should then advance past the same checkpoint. |
The operational impact of it is limited to the smpte timecode generation and validation transition that owns generated timecode is combined with multiple-bit-rate audiences. In the representative case where an MBR profile is selected after timecode was enabled, keep the first failing call and its object identity so a later wrapper cannot replace the no mbr with timecode evidence.
A controlled diagnostic sequence
- Record
0xC00D1BDA, it, the Encoder version and the exact API call or property access that returned it. - Export the current
.wmeor.prxconfiguration, then capture AudienceCount, timecode mode and output topology. - verify the smpte timecode generation and validation precondition without changing the source, profile and output sink at the same time.
- Run one controlled comparison in which only this condition changes: use a single audience for generated timecode or disable the feature.
- After the change, recreate the affected Encoder object rather than assuming the existing graph discarded its earlier no mbr with timecode state.
Nearby HRESULTs that mean something else
| Result | Why it is a different boundary |
|---|---|
NS_E_TIMECODE_REQUIRES_VIDEOSTREAM | timecode generation is enabled in an audio-only profile |
NS_E_INVALID_TIMECODE | parsing or range validation of the configured starting timecode |
NS_E_NO_SMPTE_WITH_MULTIPLE_SOURCEGROUPS | generated or source timecode is requested in a session with multiple source groups |
Corrective action at the right layer
The focused correction is to use a single audience for generated timecode or disable the feature. A retry is useful only after the recorded no mbr with timecode precondition changes.
Do not convert timecode to wall-clock strings before preserving the raw frame count, frame-rate code and drop-frame mode in a session that returns it.
Technical references
- WMTIMECODE device-control structure.
- WMEncoder.StartingTimecode.
- WMEncoder.EnableTimecode.
- Detecting profile compatibility.
Looking for a different code? Search another status or error code.