| Previous | Next |
| VFW_E_VMR_NOT_IN_MIXER_MODE | VFW_E_VMR_NO_DEINTERLACE_HW |
VFW_E_VMR_NO_AP_SUPPLIED
Meaning
Windows documents VFW_E_VMR_NO_AP_SUPPLIED as “The application has not yet provided the VMR filter with a valid allocator-presenter object”. Here, the VMR is used in renderless mode before the application supplies a valid allocator-presenter object.
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 mode and renderer version.
- Evidence 2: allocator-presenter object identity and lifetime.
- Evidence 3: AdviseSurfaceAllocator or notification-interface result.
Relevant contract
Start with the renderer, graphics driver, display connection and negotiated surfaces.
Conditions that can produce it
- Cause 1: renderless mode was selected without AdviseSurfaceAllocator.
- Cause 2: the allocator-presenter object was released too early.
- Cause 3: the presenter implements the wrong VMR interface generation.
Correction strategy
- Action 1: create and register the correct allocator-presenter before connection.
- Action 2: hold it for the renderer lifetime.
- Action 3: match VMR-7 and VMR-9 interface families exactly.
Example incident
A VMR-9 is switched to renderless mode but the application passes a VMR-7 allocator interface; using the matching VMR-9 presenter resolves it.
Retry and recovery
Retry rule: Retry after a valid allocator-presenter is registered and the renderless graph is rebuilt if connection already failed.
How it differs from nearby results
VFW_E_VMR_NOT_IN_MIXER_MODE concerns multi-stream composition; it concerns the application-owned presentation path required by renderless mode.
Official Microsoft references
Looking for a different code? Search another status or error code.