Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

D3D12_VIDEO_MOTION_ESTIMATOR_INPUT.pHintMotionVectorHeap use case #842

Open
artths opened this issue Oct 2, 2023 · 1 comment
Open

D3D12_VIDEO_MOTION_ESTIMATOR_INPUT.pHintMotionVectorHeap use case #842

artths opened this issue Oct 2, 2023 · 1 comment
Labels

Comments

@artths
Copy link

artths commented Oct 2, 2023

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?

@DTL2020
Copy link

DTL2020 commented Apr 1, 2024

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants