This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[INFO] deinterlacing: motion-adaptive vs. motion-compensating
#2
QTGMC by default uses motion compensation (leveraging mvtools) for deinterlacing. (old Avisynth MVBob and MCBob also used motion compensation)
Outside of Avisynth and Vapoursynth an example of a simple motion compensation deinterlacer would be mcdeint from ffmpeg.


Cu Selur

Ps.: Through the torch add-on Hybrid also supports https://github.com/pifroggi/vs_deepdeinterlace and https://github.com/anymyb/MFDIN for deinterlacing, which are additional methods.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Messages In This Thread
RE: deinterlacing: motion-adaptive vs. motion-compensating - by Selur - 13.07.2025, 07:24

Forum Jump:


Users browsing this thread: 1 Guest(s)