Realtime mpeg 2 capture with latest mainconcept (1.4.2)

[SatStorm]

I just did some tests with 1.4.2.
Great application indeed, great realtime mpeg 2 capture with my bt878 card and my nvidia one!

But I can't understand one thing: If I set "deinterlace", how it does the job? I mean, version 1.4.1 looked like doubling a field so to mach a frame (the usual trick). The picture degration was noticable.
But with this version (1.4.2), I can't really tell... Or they make it better, or they do some other kind of deinterlace!
Why to use deinterlace you might ask?
Because I'm a victim of the notorious field distortion problem at the bottom of the picture when I capture realtime with MC 1.4.1 (it happens on some cards, mostly nvidia). So, I use that option (deinterlace) when I had to convert something fast & dirty to mpeg 2. But with the new version (1.4.2), something changed on this (for better). What is your objervations on this?
Also, who can explain me how exactly mainconcept 1.4.2 perfoms deinterlace? What technic this program at this version use?

Overall, I have to admit that I'm impressed with mc 1.4.2 in general. I hope TMPGenc plus 3 gonna show some improvement when it's going to release, because otherwise, I feel that they gonna loose me from costumer....

[FOO]

So what do the deinterlaced frames look like ?
No lines on motion ?

[SatStorm]

In my eyes, the picture looks something like what the PAL frame restorer filter do on any interlace source on virtualdub. (Delays fields so to mach a frame)
Or it does that, or it does something like a 2:2 Inverce telecine proccess (this is the PAL inverse telecine method, which only dscaler do from what I know)
Or simply, my eyes trick me!

That's why I'm asking about it. Which are your objervations on this fuction?

[FOO]

I don't have MC installed , and all I have is a ATI capture
I'll go find it.

[lordsmurf]

I've noticed that too. I haven't had much time to dedicate to it recently. I'm in the middle of an MC guide, but some of the settings give unusual results.

[SatStorm]

I'm sure that it doesn't "double' one field as version 1.4.1. It does something else and the results are better. But what it does exactly? Here is the question!

[SatStorm]

For bt8xx(x) users:
First go:
Capture > setup > Video capture device > output size 768 x 576
Then go:
Capture > setup > capture > config > Video Settings > Frame size 352 x 576

Set a bitrate like 1750 - 2800 - 5000 (2 Pass VBR)

Grabb realtime to mpeg 2.

Go back but set frame size 704 x 576

Set a bitrate like 2000 - 4000 - 7000

Result: Even if you set up for output 352 x 576 or you set up 704/720 x 576 the picture is exactly the same

If you repait the test with 1.4.1 there is a difference

[SatStorm]

Well, the tests ended for this round...

Always set Capture > setup > Video capture device > output size 768 x 576
On all cases , you don't have statering problems on whatever framesize you encode and expecially for the bt8xxx cards, the picture is noticable better.

If I only have noticed that before...