You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned, pHintMotionVectorHeap representing the buffer containing the hardware-dependent output of the previous motion estimator operation which may be used for hinting the current operation. First I tried passing motion vector heap obtained after estimating the previous pair of frames, the result did not change a single pixel. Then I thought that maybe it should be used for the case when the flow is estimated in coarse-to-fine manner, so I passed the previous motion vector heap of a smaller size, but the result is the same. Then tried all this on a GPU from another chip manufacturer. No, either. What specific use case should this work for?
The text was updated successfully, but these errors were encountered:
It may significantly depends on the underlying hardware (driver and MPEG encoder ASIC). So better to ask each hardware vendor currently providing support for DX12-ME functionality (NVIDIA, AMD and intel (?)) about if input of MVs as a hints is implemented (and maybe in some chips family and/or drivers etc).
As mentioned, pHintMotionVectorHeap representing the buffer containing the hardware-dependent output of the previous motion estimator operation which may be used for hinting the current operation. First I tried passing motion vector heap obtained after estimating the previous pair of frames, the result did not change a single pixel. Then I thought that maybe it should be used for the case when the flow is estimated in coarse-to-fine manner, so I passed the previous motion vector heap of a smaller size, but the result is the same. Then tried all this on a GPU from another chip manufacturer. No, either. What specific use case should this work for?
The text was updated successfully, but these errors were encountered: