Simpsons - TFM vs QTGMC

[protectron]

Cool, thanks. Also like this poster, my GPU usage averages at about 30% with RealCUGAN.
https://forum.videohelp.com/threads/4093...-hybrid%29

Any idea why?

---

DDD and DeF look horrendous lol

[protectron]

I became disillusioned with RealCUGAN. It looks a little too unnatural and where are there animation errors like colors outside of lines the mistakes are amplified (it was running too slow anyway).

No Resizer


RealCUGAN


I've decided to run two AA filters (DAA and EEDIAA) on TIVTC, darken the lines, and call it a day (for now).

If anyone has a better method for deinterlacing, please comment.

[protectron]

UPDATE: I figured it out. Running Stab before TFM fixes the bad deinterlacing. There must have been so much jitter that TFM thought the frames were interlaced.
Looks perfect now running TFM Mode 1.

[protectron]

@Selur is it generally better in this case to use TDecimate Mode 1 or Mode 7 at 23.976 fps?

[Selur]

About Stab:
Stab is a filter meant for progressive content so when you move it above the deinterlacers / field-machters, you force Hybrid to either:
a. separate the fields
or
b. deinterlace the content
based on what is configured under Filtering->Vapoursynth->Script->Filter interlace handling.
The default is 'separate fields'. I suspect that in some place the field order is switched or the fields a field is either moved up/down, so it makes sense that Stab might help there to compensate that shift.
I even suspect that it will compensate the normal up/down shift between upper and lower fields.

is it generally better in this case to use TDecimate Mode 1 or Mode 7 at 23.976 fps?

7 is more suited if the pull down pattern might change. (often due to bad edits during authoring/creation of the source)

Cu Selur

[Selur]

Correction the default isn't 'separate fields', but 'QTGMC(preset="fast")'.
Thus, Stab might not be the fix, but simply applying QTGMC with same frame rate output might be what you are doing to fix your problem.
=> you might want to check what you are actually doing. (seems like there is a bug in the progressive filtering when TFM is used before deinterlacing)

Cu Selur

[protectron]

I just checked what the "Filter interlace handling" value and it was set to QTGMC fast. I did not change it manually.
Did it change automatically to accommodate the Stab order?

Also I'm not sure what that parameter means. Is QTGMC running before Stab and then again after Stab during TIVTC?

---

Stab before TFM + Filter Interlace Handling (FIH) QTGMC seems to be the only combo that fixes the bad interlacing.
However, looking deeper I found that it breaks the intro, which is progressive content, like you said. In S02E05 it breaks a different progressive scene.

So I guess my solution doesn't work perfectly after all lol.

Bad deinterlacing on progressive sequence (Stab + FIH QTGMC)

[protectron]

Ok so I've made this post under the wrong assumptions. Checking the source material, the bad deinterlaced frames I thought were from TFM are actually baked into the source material.

I'm now running EEDIAA before TFM and now everything looks good; bad source frames and progressive sequences. I moved Stab back to the default position.

Two example frames from source: