Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
6th July 2009, 04:33 | #61 | Link | |
Registered User
Join Date: Apr 2009
Posts: 122
|
Quote:
|
|
7th July 2009, 17:33 | #62 | Link | |
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
Quote:
By the way, I have one example where it seems like EEDI2 gives better results than NNEDI2. The first screenshot is with the former, the second with the latter: Yep, it's that clip again . I assume that due to the unique nature of both the source and the script, it's not just the switch from EEDI2 to NNEDI2 that causes the differences. In fact, the script might only work with EEDI2. In any case, I can provide you with a clip (or the whole video, it's ~160MB) and the script if you want.
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it. Last edited by Chainmax; 7th July 2009 at 17:50. |
|
7th July 2009, 23:03 | #64 | Link |
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
That's not the only difference. Look closely at the microphone: the lines on the EEDI2 version are completely straight (and the edges themselves are sharper), whereas the ones in the NNEDI2 version aren't.
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it. Last edited by Chainmax; 7th July 2009 at 23:05. |
8th July 2009, 03:05 | #66 | Link |
契約者
Join Date: Jun 2008
Posts: 1,576
|
I like EEDI2 result. On NNEDI2 screenshot these additional details are less noticeable than microphone (where eedi2 shows better result). In motion these details probably can't be noticed at all, while jagged lines - easily. I wonder how NNEDI2 looks on Anime compared to eedi2...
|
8th July 2009, 03:54 | #67 | Link |
Registered User
Join Date: Mar 2009
Posts: 166
|
EEDI2 is the smoother deinterlacer, so if you can deal with the slight loss of detail it is definitely the way to go.
NNEDI2, on the other hand, is the far superior upsizer, hands down. Last edited by shoopdabloop; 8th July 2009 at 03:58. |
8th July 2009, 06:50 | #69 | Link |
Registered User
Join Date: Mar 2009
Posts: 166
|
Chainmax, could you upload a clip of the unfiltered source? A small one.
Unless there are other filters that are somehow causing the poor deinterlacing in both cases, perhaps it would be best to go with MCBob or TempGaussMC. I would like to try out various deinterlacers on the source myself. Last edited by shoopdabloop; 8th July 2009 at 06:53. |
8th July 2009, 09:14 | #71 | Link | |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 5,391
|
Quote:
It's okay if you like EEDI2 better in some parts, but one should note that at the same time EEDI2 *fails* in other parts.
__________________
- We´re at the beginning of the end of mankind´s childhood - My little flickr gallery. (Yes indeed, I do have hobbies other than digital video!) |
|
8th July 2009, 11:57 | #72 | Link |
Registered User
Join Date: Feb 2004
Posts: 1,348
|
A good interpolator will only blur/antialias/lowpass to the extent that must in order to remove aliasing. EEDI2 is far too aggressive for even the most aliased source achievable using a competent processing chain. nnedi(1/2) are extremely good at processing sources containing medium to high aliasing that is still more or less recoverable, but are not very good on sources with low/no aliasing (too slow for, if anything, likely reduced quality).
I should note at this point that most good sources will have some aliasing. Killing all aliasing in a signal will take too much of said signal to the grave with it, wheather through blurring or ringing, the damage is more or less the same. If your source is butchered : eedi2 If your source is on the sharp side of good quality : nnedi If your source is blurry : high quality linear resampling Obviously there are gaps between the categories, they fall to personal taste. |
8th July 2009, 19:30 | #73 | Link | |
Registered User
Join Date: Dec 2003
Location: MO, US
Posts: 999
|
I put up version 1.4. Same as the standalone nnedi2.dll that I posted before, except that it adds another nsize value (nsize 0,1 in v1.3 are now 1,2).
Quote:
@Chainmax If you can provide a sample that would be great. As mentioned already, there is always a tradeoff between eedi2/nnedi2. |
|
9th July 2009, 05:44 | #74 | Link |
Huh?
Join Date: Sep 2003
Location: Uruguay
Posts: 3,103
|
[EDIT]Link to the full video
shoopdabloop: the source is progressive, the EDI interpolators are used as a resizing method and to diminish aliasing actually. Here's a clip of the source, which most of you guys will recognize . It contains the intro and the scene where the screenshots were taken from. Bear in mind it's encoded on Microsoft Video 1, in order to be able to work with it you'll have to load the file in VDub and make a lossless encode out of it, as AFAIK Avisynth cannot load it. The script used is, again, familiar to most of you guys: Code:
f=4 AVISource("X:\wherever\MakingGK-LssLss.avi",audio=false) a=last a.converttoyv12() nnedi2_rpow2(qual=3,rfactor=2,cshift="spline36resize") pointresize(a.width*f,a.height*f) vf=last.mvanalyse(isb=false,blksize=16, truemotion=true) vb=last.mvanalyse(isb=true,blksize=16, truemotion=true) vf1=last.mvanalyse(isb=false,delta=2,blksize=16, truemotion=true) vb1=last.mvanalyse(isb=true,delta=2,blksize=16, truemotion=true) xf1=last.mvflow(vf1,thSCD1=9999) xf=last.mvflow(vf,thSCD1=9999) xb=last.mvflow(vb,thSCD1=9999) xb1=last.mvflow(vb1,thSCD1=9999) interleave(xf1,xf,last,xb,xb1) temporalsoften(2,40,50,mode=2) x=selectevery(5,2) x.converttorgb() xa=pointresize(a.width*2,a.height*2).converttoyv12().nnedi2_rpow2(qual=3,rfactor=2,cshift="spline36resize") xb=crop(1,1,0,0).addborders(0,0,1,1).converttoyv12().pointresize(a.width*2,a.height*2).nnedi2_rpow2(qual=3,rfactor=2,cshift="spline36resize") x=merge(xa,xb) xvf=x.mvanalyse(isb=false,blksize=16, truemotion=true) xvb=x.mvanalyse(isb=true,blksize=16, truemotion=true) xvf1=x.mvanalyse(isb=false,delta=2,blksize=16, truemotion=true) xvb1=x.mvanalyse(isb=true,delta=2,blksize=16, truemotion=true) xxf1=x.mvflow(xvf1,thSCD1=9999) xxf=x.mvflow(xvf,thSCD1=9999) xxb=X.mvflow(xvb,thSCD1=9999) xxb1=x.mvflow(xvb1,thSCD1=9999) interleave(xxf1,xxf,x,xxb,xxb1) temporalsoften(2,255,255,mode=2) selectevery(5,2) Spline36Resize(512,384) Levels(0,1,245,16,235) FFT3DFilter(sigma=6,plane=3,bw=32,bh=32,bt=3,ow=16,oh=16) Tweak(sat=1.3) dull=last sharp=dull.LimitedSharpenFaster(Smode=4,Strength=200) Soothe(sharp,dull,25) c=last GrainU=c.UtoY().AddGrain(4,0,0) GrainV=c.VtoY().AddGrain(4,0,0) Return ytouv(GrainU,GrainV).MergeLuma(c).gradfun2db(thr=2.4).gradfun2db().AddGrain(10,0,0)
__________________
Read Decomb's readmes and tutorials, the IVTC tutorial and the capture guide in order to learn about combing and how to deal with it. Last edited by Chainmax; 26th July 2009 at 08:26. |
29th July 2009, 20:53 | #77 | Link | |
Registered User
Join Date: Jul 2007
Posts: 552
|
Quote:
Probably, you are wrong and PADDQ is SSE2 instruction. |
|
29th July 2009, 21:33 | #79 | Link |
Registered User
Join Date: Jul 2007
Posts: 552
|
http://www.intel.com/Assets/PDF/manual/253667.pdf says it's SSE2. So I would trust Intel documentation more than NASM.
|
|
|