REAL good asynth resizers?

[^^-+I4004+-^^]

samples are on

http://free-st.hinet.hr/ikostic3/video_/video.htm

VD's built in resize (prec.bicubic-0.75) beats asynth's (with same settings) and lanczos3....
(if you don't see it right a way try lowering the light on
monitor
or you can blow it up real big (300% or so)...
pay attention to tv-station logo
& subtitles....)

VD's resize is more close to original,asynth's blurs more...
also some problems with lanczos3-> i used it in conjuction
with temp.smoother (from "mpeg2dec.dll")....off course
filtering first,then resizing....and lanczos seems to
change settings while coding.......ie. 1 frame OK,next
one more blurred,etc.
(off course,i sent the "good" one on sample...)

cheers

Ivo

[mtrooper]

Well, I could be entierly wrong, but:
afaik VD implementation of bicubic resize is the same as Avisynth's, so that should give you the same results.
And besides, if I can see correctly your're comparing resize filters on interlaced video, for which avisynth's resize filters weren't made (VD resize filter has option Interlaced resizing, so that it still returns interlaced picture, which is not guareanteed by avisynth filters).

[^^-+I4004+-^^]

i too expected same results,but got different ones!
video is telecided first.......

those things you see aren't combing effects,but interference in
tv-signal itself

-->telecide reconstructed progr.frames without a
glitch........

huh .......i guess i'll stick to VD_

[WarpEnterprises]

When VERTICALLY resizing interlaced video in Avisynth you have to add

SeparateFields()
...Resize
Weave()

When resizing only horizontally (to a different width) this is not necessary.

[^^-+I4004+-^^]

interlaced???
who mentioned resizing interlaced video?
as i've stated lines you see in vidcaps aren't combing,
but interference in videosignal!
(the girl in vidcaps has perfect stillness!)
first i deinterlace (on 720x576 or 704x576) with telecide..(cause it's
film material...)
after that usually temp.smooth
and only THEN is't resizing time...
so you see resizer sees only pure progressive stream....

(hope now it's clear enough....)