Deint vs. SmoothDeinterlace. Which is better

[WesW]

I have been trying deint, and it doesn't seem to affect the footage at all.
This is the last setting I tried:
deint=TDeint(mode=2,mthreshL=1,mthreshC=1,mtnmode=3,blim=100)

As you can see, I had the thresholds set to their lowest level, and there was still do noticeable improvement to the footage.
SmoothDeinterlace, otoh, can take the same rip and completely eliminate the interlacing, though I had to set its lace threshold down to 4, from its default of 24.
Smooth can't be used with YV12 footage, however, so what am I missing with Deint?

[Zarxrax]

That line on it's own does nothing. If you took that from the beta version of the guide, you might want to try reading over it more closely.

[WesW]

That line on it's own does nothing. If you took that from the beta version of the guide, you might want to try reading over it more closely.

Here is the section of the guide I was working from. Please tell me what I missed?

"When you have a source where looking for progressive frames is mostly futile, it is often best to just attempt to deinterlace the source. There are many different ways to deinterlace things and, like many things, the best method will depend on your source.

TDeint() - Tdeint is a deinterlacer that uses motion adaptation and all kinds of interesting interpolation tricks. This is a really excellent deinterlacer and worth trying.

At the default settings, this does a pretty nice job at deinterlacing by interpolating the fields, but this can leave jagged lines in the video. I also highly recommend you try this filter with the following settings: TDeint(mode=2, mtnmode=3, blim=100)

This filter has a lot of different options and modes which cause it to deinterlace in different ways. I highly recommend you check out the documentation on it and experiment to see what works best for your particular source. "

Or I guess you might be referring to this part, which is for post-processing, which is not the point where I am at. I also have no need to IVTC, which is what this section is talking about, and therefore should not be required reading. (Bolds are my addition.)

1) Try to IVTC anyway (might work pretty well)

It may be that your video is edited together in such a simplistic way that IVTC will be just as good now as it would have been working on the original source. It's not very likely, but it's possible. If you are going to use this method, a basic script like this will do:

deint = TDeint(order=1, mode=2, mtnmode=3, blim=100) #order=0 for bottom field first
TFM(order=1, cthresh=4, slow=2, clip2=deint) #order=0 for bottom field first
TDecimate()
If you have PAL footage, omit the TDecimate() part. If you are using NTSC, you can still try omitting the TDecimate() line and see if you like the result better. You really should try both ways (but never leave the TDecimate in if you have PAL footage!).

This script basically tries to match fields as best as it can, and deinterlaces the parts it cant match by blending the fields together. Notice that the order parameter, where you specify the field order is required. Order=1 means top field first, and order=0 means bottom field first.

I realize that the guide is offically a beta- I've worked on a few betas of my own over the years- and that it's going to have some omissions, and this is an omission that needs to be corrected.

[Kariudo]

the reason that the line starts with "deint=" is because it's being used by TFM on the next line (of that example scrript)
since you aren't using TFM in your script, you should remove the "deint="

[WesW]

Or, perhaps you're referring to this section of the guide:

When you have a source where looking for progressive frames is mostly futile, it is often best to just attempt to deinterlace the source. There are many different ways to deinterlace things and, like many things, the best method will depend on your source.

LeakKernelDeint(order=1, threshold=10) - This is a pretty nice deinterlacer, and I highly recommend it for editing directly from AVS files, because it is quite fast. This filter requires that you manually specify the field order. You should know this from back on the analyzing your footage page.

TDeint() - Tdeint is a deinterlacer that uses motion adaptation and all kinds of interesting interpolation tricks. This is a really excellent deinterlacer and worth trying. This filter should automatically detect the field order, assuming it follows an MPEG2Source command, but you can also specify it manually with the order parameter.

[WesW]

the reason that the line starts with "deint=" is because it's being used by TFM on the next line (of that example scrript)
since you aren't using TFM in your script, you should remove the "deint="

Ok, thanks for the help.
There are definitely some sections of the guide that still need work. There are items crucial to understanding what's going on that are just thrown in amongst pure theory sections which should be just fyi, such as the line that mentions that anime is usually made at 12fps and copied up to 24fps, and therefore non-computer animation is most always telecined up to 29.97.

Since most shows these days use at least some computer animation, there needs to be additions which specifically talk about this situation. As it is now, your average noob has to try and glean information from sections which are talking about other things.