bilu
28th August 2003, 18:53
Hi,
I usually don't encode anime but I've been making tests for the last two months. I have a problematic Neo Genesis Evangelion clips that never worked so good with Uncomb/Decimate or Telecide/Decimate as it is now working with SmartDecimate, which leaves combs behind but has no backward match or blended fields match stuttering problem.
I have been testing a lot of deinterlacers as post-processors for SmartDecimate.
FieldDeinterlace blurs too much when blend=true.
FD(blend=false),DGBob,KernelDeint,TomsMoComp all had the same problem: jagged edges, like lower resolution.
Having read this on your TomsMoComp readme:
For Avisynth only, a value of -1 is supported. In this case the TomsMoComp filter will not deinterlace but instead assume you already have progressive frames but want to double the vertical size. I found by accident that this could give slightly better apparent detail than regular scaling algorithms and is useful for low bit rate captures that are hard to IVTC/deinterlace or where you have just kept the even fields for some other reason. I'm considering making a DirectShow version of this to be run at display time, or possibly adding it to ffDshow.
And tried:
b=DGBob(FOrder(),mode=1)
SeparateFields()
SmartDecimate(24,60,b,0.50)
TomsMoComp(FOrder(),-1,0)
SeparateFields()
SelectEven()
The moving parts looked far better than any other deinterlacer I tried, like better resolution, but the static parts looked worse.
Would you consider making a static protection threshold like the one in KernelDeint? ;)
Bilu
I usually don't encode anime but I've been making tests for the last two months. I have a problematic Neo Genesis Evangelion clips that never worked so good with Uncomb/Decimate or Telecide/Decimate as it is now working with SmartDecimate, which leaves combs behind but has no backward match or blended fields match stuttering problem.
I have been testing a lot of deinterlacers as post-processors for SmartDecimate.
FieldDeinterlace blurs too much when blend=true.
FD(blend=false),DGBob,KernelDeint,TomsMoComp all had the same problem: jagged edges, like lower resolution.
Having read this on your TomsMoComp readme:
For Avisynth only, a value of -1 is supported. In this case the TomsMoComp filter will not deinterlace but instead assume you already have progressive frames but want to double the vertical size. I found by accident that this could give slightly better apparent detail than regular scaling algorithms and is useful for low bit rate captures that are hard to IVTC/deinterlace or where you have just kept the even fields for some other reason. I'm considering making a DirectShow version of this to be run at display time, or possibly adding it to ffDshow.
And tried:
b=DGBob(FOrder(),mode=1)
SeparateFields()
SmartDecimate(24,60,b,0.50)
TomsMoComp(FOrder(),-1,0)
SeparateFields()
SelectEven()
The moving parts looked far better than any other deinterlacer I tried, like better resolution, but the static parts looked worse.
Would you consider making a static protection threshold like the one in KernelDeint? ;)
Bilu