TFM bug

[Katie Boundary]

When TFM detects a frame as interlaced, and deinterlaces them by pulling pixels from the Clip2 parameter, it doesn't just check and replace pixels from that frame's "guest" field. It replaces pixels from the "home" field too. Does anyone know of a workaround for this?

[hello_hello]

How is that a bug? It takes pixels from two fields to cause combing. If it only replaced the pixels in the even (or odd) scanlines instead of both, there'd probably still be combing.

Edit: Another thought...
If you're using a lossless bobber to create the de-interlaced clip, where the original scanlines are output untouched, does it matter if pixels are also taken from the lossless scanlines?
When the bobber doesn't output lossless scanlines, you'd probably want TFM to take pixels from both.