-
Notifications
You must be signed in to change notification settings - Fork 30
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
Request for MScaleVect port #45
Comments
What happens if you try to run Analyse on 8 bit video and Degrain on 16 bit video? |
No errors appear at least. I never thought trying that as it's always been a no-no to mix clips of different formats..
So are you saying that code-wise, it should be safe to go without any problems with scaling values etc.? |
VectorStructure::sad would be corrupted (invalid range). |
Is it something that should be immediately visible or just in some corner cases? I tried looking at different places in that test video but couldn't find anything totally strange. |
In fact, if the whole function seems too big to port, I think the bitdepth scaling would already cover most use cases easily without any noticable quality loss. In UHD resolutions, motion analysis at high bitdepth gets very slow and dct=5 is totally unusable. |
The actual code to do this isn't that complicated, if we use pinterf's version as an example: https://github.com/pinterf/mvtools/blob/mvtools-pfmod/Sources/MScaleVect.cpp Should be easy for anyone to do, but I'll add this to my todo list. Might get to it sometime in 2023... ha |
Implemented as a separate plugin https://github.com/Mikewando/manipulate-motion-vectors |
Would it be possible to have the smart MScaleVect functionality in Vapoursynth's MVTools as well? It can be used to speedup analysing by doing analysis on the original 8-bit clip and then using the vectors in high bit depth degraining etc. It would also make dct=5 usable, which helps with the quality of the vectors. In 16-bit analysis, it tends to slow things down quite a lot.
https://forum.doom9.org/showthread.php?p=1826390#post1826390
The text was updated successfully, but these errors were encountered: