I like avisynth, I am using avisynth+ on windows x64.
I am using it to clean up an interlaced MPEG2.
for now I am using daa3 for removing interlacing

Code:

(nn = c.nnedi3(field=-2,nsize=6,nns=4,qual=2,pscrn=4,fapprox=0))

but I am not yet sure if it is better to use QTGMC (I also tested mcdaa3 by using his daa3mod function but his results were not so good)
I am also doing the best I can to do noise reduction, after some testing

gives the best quality (I also tried knlCL but he makes stains)
I may use some sharpening later but I haven't decided that yet (3 of 4 sharpeners I tested increase noise, the only one who doesn't is MSharpen but has some other small problems)
the result is to be encoded into lossless x264 with:

1. when MCTD is running twopass=true, is it recommended/benefitial to use p=pre ? or is it that twopass already does that ?
2. I know that x264 lossless is lossless regardless of --pass 2/--pass 3 (multipass x264 encoding) and I know that many use --pass 2 to control file size. if I don't care about variances in file size but do care about reducing file size, should I use --pass 2/3 ?
3. is MCTD() (the mod) better than MCTemporalDenoise() ?
4. is QTGMC() better than daa3() ? the source has not only interlacing but also aliasing and flicker (flicker I couldn't find a way to remove without causing other problems

Oops, sorry, you meant result of the client script.
That script was just in question to Feisty2, top right is amplified difference between the two results both with and without Precise=True.
Set Amp=False for non amp'd diff.

EDIT: Top Left=Source, BotLeft=Precise=False, BotRight=Precise=True.

EDIT: A=MCDegrainSharp(2,bsrch=BSRCH,Precise=False)
Above has Frames=2 for both function calls, I usually use 1, but sometimes up to 3.

EDIT: The Amp'ed difference just to make obvious where there are differences, so you can examine those areas more closely.
You could change eg Frames=1 in A and Frames=2 in B and set Precise = False/true *same for both)
to view difference due to only Frames arg. (Below untested)

also what would be the recommended order for the operations ? antialiasing+deinterlacing and noise reduction and sharpening ?
I see it like this:

Code:

AA/DEINT
NR
Sharp

but I suppose it's right to do Sharp before NR to compensate for increased noise from sharp ? QTGMC with noiseprocess can also add noise right so AA/DEINT is always at the top ? I suppose if you sharp before AA/DEINT it could affect for better or worse the AA/DEINT ?

I did many tests, I used QTGMC, AAAmod, sangnom2, nnedi3, maa2, daa3 and mcdaa3: none of them reach remotely close to the artifact reduction/sharpness/interlacing elimination qualities of daa3 for this source anyways. the one that did give very good result is TIVTC, very effective, even better in some areas with horizontal lines.

I have a small problem, the process is very long, so I have idea to run the process on another computer, but the computers are not the same, the computer that runs right now has multimedia instructions AVX+2, SSE 1,2,3,3S,4.1,4.2, but the other computer has SSE 1,2,3,4A without AVX, I am asking because I am afraid to loose precision in the process not important for me speed, does AVX/2 give more precision in registers than SSE registers ?

the one that did give very good result is TIVTC, very effective, even better in some areas with horizontal lines.

Could your source be telecined (23.976 fps -> 29.970 fps conversion)? If the interlacing is due to telecine pulldown all you need to do is match the fields and remove duplicate frames (no heavy processing at all). This is what you call inverse telecine (IVTC). I would say most used IVTC plugins are Decomb (Telecide, Decimate) and TIVTC (TFM, TDecimate). An example:

If the picture still looks interlaced after applying TFM then it's not telecined. If it looks like frames are not in the right order then you should try assuming another field order by calling either AssumeTFF() or AssumeBFF() before TFM, but this shouldn't be necessary if you are importing a .d2v file with MPEG2Source. If after applying the code above interlacing disappears except for only some parts (titles, intros, etc.) then your source is hybrid.

there is significant improvement with the first set of code, then I added TFF but it had little effect, BFF looked the same as without assume
with this code the horizontal lines are significantly reduced and are visible only in fast movements, good catch
I will see what I can do about sample
the problem with daa3 is not his effectiveness at deinterlace/antialias at this he is the best but he leaves some flickering in some areas and if someone can help figure out how to fix it I will give you half of the box office
as you will see soon in the samples, the movie has many problems:
interlacing, aliasing, flickering, noise, 16-235 range which I can't extend to full range, blurry not realy sharp enough
the blurry problem I can live with since I know there is no solution to that, the range problem have no choice but to live with since that also have no solution, but I would like to do anything I can to fix the other problems

im working on a VA panel with 5000 static contrast and standard 80% gamut with less than 5% color error ratio, is nice but is not externally calibrated, he is full 8-bit native panel

Why lossless? Didn't I suggest cutting from the MPG using DGIndex? Much smaller file; much less time to download. I don't much want to wait an hour to download from whatever that place is. There are much better filesharing sites.

Open the MPG in DGindex. Use the [ and ] buttons to isolate a short section. Then File->Save Project and Demux Video.

The live action just looks telecined to me. The CGI is borked. If you're not going to go through and filter it separately, just leave it as it is. It's not worth ruining everything else just to fix it. You can do 2-pass to make a VFR file so you don't decimate those.

Run an analysis pass with:
tfm(d2v="D:\video.d2v",output="tfm.txt").tdecimate(mode=4,output="tdecimate.txt")

i did all this but the output is stuttering, how to fix it ?
does daa3 ruining the other things while fixing the CGI ?
the timecode file is only 300 bytes and have this in it:
Assume 29.970030
# TDecimate v1.0.3 by tritical
# Mode 5 - Auto-generated mkv timecodes file
0,7999,23.976024

and nothing else

I don't have d2v files i used ffmpegsource is that a problem ?

I created d2v files with dgindex but now the avs file when it's running is leaking memory
he also says error: TFM: d2v frame count does not match filter frame count (79465 vs 63572)!

Assuming the output is VFR, would it be better to encode in VFR mode? I kind of recall x264 distributes the bits a bit differently in VFR mode (CRF encoding) as it's frame rate aware, or an I remembering wrong?

The x264 encoder can encode in VFR mode by specifying something like
--tcfile-in "D:\timecodesfile.txt" in the command line.

I use MeGUI for VFR encoding now and then. The timecodes file doesn't need to exist when you add it to the command line and add the encoding job to the queue. It'll be created as soon as the second pass script is run. You just need to plan ahead in respect to naming the timecodes files if you're creating multiple encoding jobs. If the encoder is writing directly to MKV there's no need to worry about muxing with the timecodes file.
Batch=true is an option to be aware of when running both passes in some sort of automated job queue.

I just had another look at the output of daa3, you are right, it does add noise, but plain and simple needi3 looks better than tfm, unlike tfm it doesn't miss some of the interlacing, this explains whay I needed to use such high noise reduction settings, without the noise that is added from daa3 I can cut the noise reduction quantity by half and might as well set twopass to false, this will double the rendering framerate and at the same time increase the quality

I tried to modify the daa3 code and remove the sharpening stage from it:

Code:

shrpD = mt_makediff(dbl,dbl,U=3,V=3)

I think it worked good, but now when comparing to nnedi3, needi3 looks like it preserves many details that daa3 removes
with the reduced noise reduction requirements I set to twopass=false and reduced more the temporal radius to 1, even with the optimistic settings I am using it went up from 0.00/0.01 fps to 0.60 fps, 60 times more speed