i use
TIVTC and FDecimate, they are both adaptive to different framerates and levels of interlacing. Normal TFM results in aliasing and artifacts, but TIVTC does not.
kickass331 wrote:i use
TIVTC and FDecimate, they are both adaptive to different framerates and levels of interlacing. Normal TFM results in aliasing and artifacts, but TIVTC does not.
mirkosp wrote:kickass331 wrote:i use
TIVTC and FDecimate, they are both adaptive to different framerates and levels of interlacing. Normal TFM results in aliasing and artifacts, but TIVTC does not.
I'm going to assume that FDecimate was a typo and just ask you if you realise that TFM *is* the field matcher in TIVTC, and you are confusing it with plain old telecide, which btw is fine as long as you know how to handle it...
Mister Hatt wrote:>implying anything neuron2 codes is worth using
(☞゚∀゚)☞ O U
TBH, Telecide is better than TFM when you are doing 100% manual IVTC I find, because TFM tries to be clever and messes you up. On some funky sources though it is needed. Rarely have I found the need though. By manual I mean writing out OVR files or using YATTA.
That out of the way, if you use TIVTC/FDecimate, you really don't know how to IVTC by hand. You also have no idea about what framerate things should be, and are a fucking retard. inb4Kariudo edits this out.
Users browsing this forum: No registered users and 1 guest