| Previous | Next |
| MF_E_SESSION_PAUSEWHILESTOPPED | MF_E_INVALID_WORKQUEUE |
MF_E_FORMAT_CHANGE_NOT_SUPPORTED
Interpret the result in the pipeline
MF_E_FORMAT_CHANGE_NOT_SUPPORTED means the proposed media type is individually supported, but the object cannot switch to it during the current stream or lifecycle.
The result comes from the transform, source reader, sink writer, or stream negotiating a dynamic media-type change. A representative case is resolution changes midstream and the decoder supports both sizes only when configured before streaming starts.
Evidence to preserve
the old and new major/subtype GUIDs, frame size, rate, channel layout, stream flags, MFT messages, and whether the object advertises dynamic changes.
Key observations
Minimal experiment
- Record and verify: the old and new major/subtype GUIDs, frame size, rate, channel layout, stream flags, MFT messages, and whether the object advertises dynamic changes.
- Run the controlled comparison: configure the target type before streaming in a new object and compare that result with the attempted midstream change.
Similar messages, different conditions
| HRESULT | Meaning in the standard description |
|---|---|
MF_E_DRM_UNSUPPORTED | No DRM support is available. |
MF_E_UNAUTHORIZED | This operation is not authorized. |
MF_E_OUT_OF_RANGE | The value is not in the specified or valid range. |
Here, MF_E_INVALIDTYPE means the type itself is unacceptable, not merely the timing of the transition.
Targeted recovery
For this occurrence, stop and rebuild the affected branch with the target type, or use a component that supports dynamic format changes.
Authoritative references
Looking for a different code? Search another status or error code.