Deinterlaced is not progressive... why?

Well, I haven't used tmpgenc in ages and am not sure how it decides whether an avs input is interlaced or progressive considering there is no way to know without actually examining the stream (there is no internal property that distinguishes interlaced/progressive). Though, since it detects the LeakKernelBob() output as progressive, you could most likely add AssumeFrameBased() after TDeint() to have it behave the same way. LeakKernelBob() invokes AssumeFrameBased after itself, which sets the field order to BFF and sets vi.FieldBased(false). TDeint does not invoke AssumeFrameBased after itself but does set vi.FieldBased(false), so possibly tmpegenc's decision depends on the field order. Anyways, try using AssumeFrameBased after TDeint and see what happens. Finally, why does it matter what tmpgenc thinks it is as long as you know what it is? Also, if you want bobbed output with TDeint, as you will be getting with LeakKernelBob(), you need to set mode=1.

I guess. <shrug> For TMPGEng Xpress, when I drop an mpeg-2 (or .avs file) into the source window, it pops up a dialog box telling me what type of stream it is. It's important because if it thinks it interlaced, it will deinterlance itself. I don't know how it gets this info--I'm the newbie here ;)--but if I open up my original, it guesses right (interlaced, TTF), and if I open up a known progressive stream, it guesses right. If I open up a KernelBob'ed stream, it guesses right. So I guess you are just saying to ignore TMPGEng's guess and set it to progressive manually? (There's the option to do that, BTW.) Remember, since my goal is to produce a progressive mpeg-2 to burn to DVD, I have to set the output to progressive mode. Since AviSynth is already deinterlacing the original mpeg-2, having TMPGEng deinterlace it again seems odd to me, particularly when it shouldn't be possible to deinterlace something twice. (I know it does something if I leave the input setting to "interlaced" because it takes longer to encode.) Also, if I open up the avs scripts in VirtualDub, the frame count is doubled for the LeakKernelBob() stream. (I guess that is just the "bobbing"--I stress again that I'm a newbie, so forgive my ignorance. So I guess my next question is should I use LeakKernelBob() or just LeakKernelDeint() if my only goal is to convert my original interlaced mpeg-2 to a progressive mpeg-2? (Again, disregard the ramification of the loss in color quality. THis is just to test picture definition when viewed on my progressive input TV.)

I think what you want is same framerate deinterlacing and not bobbing (bobbing turns each field into a frame so the # of frames is doubled and the fps is also doubled). So use either LeakKernelDeint() or TDeint(mode=0,...). stickboy pointed out that tmpgenc decides interlaced/progressive based on framerate, so it will get it wrong in this case. You will need to set that property and field order manually.

Okay, I'll give it a shot and see what happens. Thanks, everyone, for your help! :)