Conversion from 704x576(interlaced) to 352x288

[joe355]

Which whould be the best option: BilinearResize only, or deinterlace first then BilinearResize?

[Schlumpf]

How about: SeparateFields().SelectEven().HorizontalReduceBy2() ?
You shouldn't introduce field-blendings when you don't want/have to.

[Shalcker]

Aren't ReduceBy2() sufficient in this case? It'll do almost exactly the same thing as SeparateFields().SelectEven().HorizontalReduceBy2() - drop 3 pixels out of 4 without any blending.

Either that or deinterlace and resize. Certainly no bilinear resize without deinterlacing first since that will introduce blended fields.

[Leak]

Originally posted by Shalcker
Aren't ReduceBy2() sufficient in this case? It'll do almost exactly the same thing as SeparateFields().SelectEven().HorizontalReduceBy2() - drop 3 pixels out of 4 without any blending.

No, as ReduceBy2 will blend odd and even lines while reducing vertically, thus causing ghosting with interlaced video material.

np: B. Fleischmann - Take Your Time (Welcome Tourist)

[yup]

joe355 try this script work slow than previous, but quality image better and smoother

TomsMoComp(0,15,0)
Unfilter(0,-15)
Crop(8,0,704,576)
ReduceBy2()
LetterBox(16,16,16,16) #if You make VCD for show on TV not PC
yup

[trbarry]

I don't really recomment any TomsMoComp SearchEffort parm greater than 5 anymore because it causes stray pixel artifacts for some reason. So above you might substitute TomsMoComp(1,5,0), or, if you are following it with UnFiler anyway then add the vertical filter parm as TomsMoComp(1,5,1).

But a faster way with almost as good results would be to just use YV12InterlacedReduceBy2() instead of TomsMoComp in this case.

- Tom