Deinterlacing Problem

[XadoX]

i'm having problems to deinterlace this (http://rapidshare.de/files/18837639/temp.m2v.html) video.

I have tried:

1. edeintted = last.AssumeTFF().SeparateFields().SelectEven().EEDI2(field=-1)
TDeint(order=1,edeint=edeintted)

2. tfm(mode=2, sco=0, pp=3)

3. TDeint(order=1)

4. FieldDeinterlace(blend=false)

Generaly the video seems to be deinterlaced corretly, but there a passages which aren't deintelaced the right way. TFM seems to manage it the best but also not 100% correctly at all.

Trie to deintelace the sample @ Frame 200.

[foxyshadis]

The little bits of residual combing on what should be stationary objects? (Caused by the camera moving slightly.) The only way I could get rid of them is to follow the deinterlacer (tdeint or leakkerneldeint) with:

eedi2().lanczosresize(width,height)

Did the job nicely, 's why I like it.

This clip looks like a prime candidate for the BlockTerminator that chainmax and I are working on, and almost finished with. It's slow as hell, but then, that broadcast is crappy as hell.

A fieldmatcher will probably work where all the motion is the same, but I can't see it working in general on a purely interlaced flick.

[XadoX]

if i use it like that:


# SOURCE
DGDecode_mpeg2source("D:\EP09 - Casino Fatal.d2v",info=3)

# DEINTERLACE
TDeint(order=1)

# RESIZING
eedi2().LanczosResize(704,528,12,4,462,568)



i get a wrong image and still these interlaced artifacts.

[foxyshadis]

Well, the first lanczosresize(width,height) is working from double-height, you can't just use your normal end-resize. If you double all the cropping height values it should work though - LanczosResize(704,528,12,8,462,1136). It won't get rid of all the residual combing, but it'll get a lot of it from what I saw.

[scharfis_brain]

mpeg2source("C:\Downloads\forum\xadox\temp.d2v", cpu=6)
crop(10,0,-6,-0,align=true)
tfm(pp=0)
separatefields().eedi2(field=3)
merge(selecteven(),selectodd()).sharpen(0,1)
crop(0,2,0,-2)
lanczosresize(704,528)


this lets you get rid of all stairstepping and combing!

The combing and stairstepping is caused by the bad film to PAL transfer.

Do a simple bob and you'll see immediatelly what is going wrong with it. (the film has been deformed between both fields, so image details aren't in place anymore between two fields of the same Film-Frame!)

[laserfan]

Someday someone is going to build a software package that analyzes-and-processes a video without my having to become a video engineer! I'm retired, my career is over; I don't want to learn another one. These conversions can sometimes get to be mind-boggling!!!

Yeah, I know, if any Tom, Dick, or Harry could do this, then we wouldn't need all y'all's expertise like we do! :p

[scharfis_brain]

Someday someone is going to build a software package that analyzes-and-processes a video without my having to become a video engineer!I doubt that.
Computers are dumb. Totally dumb! And in this discipline they are incredibly fast :(

[Revgen]

I doubt that.
Computers are dumb. Totally dumb! And in this discipline they are incredibly fast :(

Yep, computers make jobs more efficient, but not easier. It's much easier and simpler to talk on a real phone than it is talk on a VOIP line. But it's just not as cost efficient as using the internet.

[XadoX]

hmm the interlaced artifacts are gone, but new are created @ some other areas of the video:
http://img78.imageshack.us/img78/4310/artifacts7qu.th.jpg (http://img78.imageshack.us/my.php?image=artifacts7qu.jpg)

Sample (http://rapidshare.de/files/19265723/EP09_-_Casino_Fatal_cut.m2v.html) from the screenshot.

The same artifacts also where created by:

edeintted = last.AssumeTFF().SeparateFields().SelectEven().EEDI2(field=-1)
TDeint(order=1,edeint=edeintted)

[scharfis_brain]

look into eedi2's readme and tweak its Parameters until these artifacts are gone.