| Previous | Next |
| VFW_E_CERTIFICATION_FAILURE | VFW_E_VMR_NO_AP_SUPPLIED |
VFW_E_VMR_NOT_IN_MIXER_MODE
Meaning
Windows documents VFW_E_VMR_NOT_IN_MIXER_MODE as “The VMR has not yet created a mixing component. That is, IVMRFilterConfig::SetNumberofStreams has not yet been called”. Here, a mixer-specific VMR method is called before SetNumberOfStreams has created and enabled the mixing component.
Relevant contract
Start with the renderer, graphics driver, display connection and negotiated surfaces.
Conditions that can produce it
- Cause 1: the application assumes the VMR starts in mixer mode.
- Cause 2: configuration occurs after input pins are connected.
- Cause 3: a renderer rebuild loses the prior stream-count setting.
Evidence worth preserving
Record lengths and hashes instead of raw content when the incident includes display identifiers, protected-content state, driver details and media paths.
- Evidence 1: VMR-7 or VMR-9 identity.
- Evidence 2: SetNumberOfStreams call and result.
- Evidence 3: input connection order and current stream count.
Correction strategy
- Action 1: configure the VMR before connecting its inputs.
- Action 2: set an explicit stream count for mixing scenarios.
- Action 3: reapply configuration after creating a new renderer instance.
Retry and recovery
Retry rule: Retry after the VMR has entered mixer mode and the relevant mixer interface is reacquired.
How it differs from nearby results
VFW_E_VMR_NO_AP_SUPPLIED concerns renderless-mode allocator-presenter setup, while it concerns the missing mixing component.
Example incident
An overlay application calls IVMRMixerControl9 on a freshly added VMR-9 without setting the stream count; configuring two streams first removes it.
Official Microsoft references
Looking for a different code? Search another status or error code.