Log in

View Full Version : NTSC->PAL problem with lines


kle500
2nd November 2004, 12:30
I am using Xesdeeni scripts for NTSC->PAL standards conversion, since his first script.
I allways convert Interlaced xxx NTSC dvd's to PAL interlace, for viewing on TV only.
But i allways have trouble with lines, on movement, or on (fade-in, fade-out from black or to black), whenever i use the defaults of any deinterlacer, examples below.
I remember that many people had the same problems with default settings of SmoothDeinterlace like:

SmoothDeinterlace(doublerate=true,tff=true)
but with the following moddifications, the picture was fine:

SmoothDeinterlace(doublerate=true,tff=true,lacethresh=1,staticthresh=10,showlace=false)

Allthough xesdeeni mentioned that there was no need for such modifications, i found no other way to overcome this problem.
Notice that since i first envolved in standards convertion via computer, i have made hundreds of re-formats using XP pro.
Lately i saw xesdeeni, mentioned about using different deinterlacer, such <KERNELBOB>, being faster,
so i gave it a try and found it to be a lot faster from SmoothDeinterlace... but, the lines where there.
No matter what thresholds i put, in some scenes i see lines.

Notice that i use Procoder express for encoder, cause it handles interlace matterial better than any other encoder and is also
much better in handling low bitarates.
So i tryied feeding it a simple ntsc file (without conversion script), to see the results.
The results where very good, without lines, but the encoding was very slow.
But if i feed an avs script like this:

ConvertToYUY2(interlaced=true)
SmoothDeinterlace(doublerate=true,tff=true,lacethresh=1,staticthresh=10,showlace=false)
LanczosResize(720,576)
ConvertFPS(50)
SeparateFields()
SelectEvery(4,0,3)
Weave()

i have an increase in speed
the conversion this way is more sharp, with a little more vissible trails in fast movement (especially in vertical movements)

Some friend said that Procoder 2, is way faster in standards conversion than Express, so i had to try.
I visited him, so i could see what was the speed increase, ofcource i installed to his machine procoder express, to see the difference.
Results: PC2 was 2x than PCE, but the conversion from PC2, had the same lines i see using all deinterlacers.
Notice that both PC2 and PCE, where using simple NTSC script (so i could see the programs conversion quality and speed).

Now, are everybody dealing with standards conversion (especialy NTSC->PAL interlace), have the same problems with lines?

I hope there must be some solution on this, cause i can't beleive that people dealing with interlace standards conversion, haven't seen this problem.
Bellow are some captures from the same frame of the video, using different deinterlacers, there is also the original NTSC frame,
and the frame (smoothdeinterlace with mod) is using:
SmoothDeinterlace(doublerate=true,tff=true,lacethresh=1,staticthresh=10,showlace=false)

Thank's
#AVS1

ConvertToYUY2(interlaced=true)
SmoothDeinterlace(doublerate=true,tff=true)
LanczosResize(720,576)
ConvertFPS(50)
SeparateFields()
SelectEvery(4,0,3)
Weave()


#AVS2
ConvertToYUY2(interlaced=true)
KernelBob(order=1)
LanczosResize(720,576)
ConvertFPS(50)
SeparateFields()
SelectEvery(4,0,3)
Weave()


#AVS3
ConvertToYUY2(interlaced=true)
DGbob(1)
LanczosResize(720,576)
ConvertFPS(50)
SeparateFields()
SelectEvery(4,0,3)
Weave()

#AVS4
ConvertToYUY2(interlaced=true)
SmoothDeinterlace(doublerate=true,tff=true,lacethresh=1,staticthresh=10,showlace=false)
LanczosResize(720,576)
ConvertFPS(50)
SeparateFields()
SelectEvery(4,0,3)
Weave()

Xesdeeni
4th November 2004, 17:16
Fades are a particular problem with deinterlacers, from what I've seen. But you shouldn't seem lines elsewhere. Please go ahead and send your images if you can't post them, and I'll take a look.

BTW, there is a bug in SmoothDeinterlacer that requires an additional SeparateFields()/Weave() as a work-around. But this wouldn't explain the same symptom with KernelBob().

Xesdeeni
(Xesdeeni2001 on the yahoo server)

kle500
4th November 2004, 20:19
There is no difference either, by using the:
SeparateFields()
Weave()
before the smoothdeinterlacer.
As i mentioned before, the only way to get rid of these fade lines during movement, is by modifying the smoothdeinterlacer.
I wish i could do the same with Kernelbob, cause is a lot faster, but it seems that whatever threshold i use to kernelbob the output has fade lines (by using high values to threshold), or flickering in static video frames.

Thank's for your reply.

P.S.
What i don't understand, is why PROCODER 2 produces the same problem in fade-in fade-outs, but not in PROCODER EXPRESS... strange