unable to deinterlace

[carlo_0000]

megui is unable too deinterlace some of my videos

i olso restored the old dgindex but no change

.avs :

DGDecode_mpeg2source("D:\Cascada.-. Never.Ending.Dream.d2v",info=3)
ColorMatrix(hints=true)
edeintted = last.AssumeTFF().SeparateFields().SelectEven().EEDI2(field=-1)
TDeint(order=1,edeint=edeintted)
crop( 14, 80, -16, -76)

LanczosResize(720,400) # Lanczos (Sharp)
#denoise

what's wrong in this setting ?

http://perso.latribu.com/tribu/mkv/bug1.JPG
http://perso.latribu.com/tribu/mkv/bug2.JPG

[carlo_0000]

this is the original with no netting

http://perso.latribu.com/tribu/mkv/original.JPG


i tryed some manual setting (chose film in place than interlaced)

DGDecode_mpeg2source("D:\Cascada.-. Never.Ending.Dream.d2v",info=3)
ColorMatrix(hints=true)
tfm(order=-1).tdecimate()
crop( 14, 80, -16, -76)

LanczosResize(720,400) # Lanczos (Sharp)
#denoise

output is better

http://perso.latribu.com/tribu/mkv/film.JPG


but what is film ? i know only progressive & interlaced
and what is field order top field first

thanks

[Atak_Snajpera]

try to use
tdeint(order=1,mthreshL=0)

[Hyper_Thread]

There is a option missing in ColorMatrix, use ColorMatrix(hints=true,interlaced=true) in your first script, that should fix the problem.
This issue with colormatrix is already fixed in MeGUI v.0.2.5.1005.

[carlo_0000]

thanks for help
i going to install the megui 0.2.5.1

i tryed but the output is still the same

DGDecode_mpeg2source("D:\Cascada.-. Never.Ending.Dream.d2v",info=3)
ColorMatrix(hints=true,interlaced=true)
edeintted = last.AssumeTFF().SeparateFields().SelectEven().EEDI2(field=-1)
TDeint(order=1,edeint=edeintted)
crop( 14, 80, -16, -76)

LanczosResize(720,400) # Lanczos (Sharp)
#denoise

i tested with mthreshL=0
this is ok
thanks
the output looks good

[foxyshadis]

mthreshL=0 is a bad idea, generally, it reduces resolution the same as if you'd cut one field and resized up. (It'd be a lot faster that way too.) A higher mthresh is important for keeping a lot of vertical resolution.

Most likely you just have the wrong field order. If analysis gave you the wrong one, it'd be nice to have the source so that we could test against it and find out why. If you turned deinterlacing on yourself, then most likely you gave it the wrong order, try switching to BFF. (order=0 in tdeint.)

[Atak_Snajpera]

@foxyshadis
I've noticed that TDeint(order=x,mthreshL=0) can give you even more details than TDeint(order=x) plus of course all annoying artifacts are gone. I'm really curious how are you going to explain that? :)

source video
http://www.archive.org/download/jvc_hd7/hv20_05.m2t.mpg

ScreenShots in PNG
HV20_source.PNG - http://www.mediafire.com/?4x9cg4olrzl
order0.PNG - http://www.mediafire.com/?3ziyhjjjyny
order0_mthreshl0.PNG - http://www.mediafire.com/?edmvyyb2dxu
order1.PNG - http://www.mediafire.com/?2izxp5jmvxt
order1_mthreshl0.PNG - http://www.mediafire.com/?41u2xmym4nx

Ps. Compare details on pavement

[~bT~]

^ nice one. I'm gona have to go with you on that. :)

[foxyshadis]

Indeed, but like I said, it'd be much faster to just bob() it in that case. (I can see why TDeint would be confused, even to me it looks like a checkerboard pattern. It's one of those manual override sections. Other deinterlacers tended to do even worse, though.) I suppose the vertical detail isn't enormously important, particularly with a slightly shaky camera, but that's your choice. I'd rather minimize the dumb-bobbed look where possible.