How to Deinterlace using Motion Compensation?

[Undead Sega]

I dont knwo if this is right right place to post this but i was wondering how do you deinterlace footage using Motion compensation?

now, i know ur probably thinking why not use other mothods like Bob, Weave, Blend and so on? well, from what ive read, Motion Compensation tends to give results superior to other methods.

also, if anyone has read 100fps website, he comes to the fact that Motion Compensation retains full resolution and interlaces with accuracy if not, then fully.

http://www.100fps.com/

i am aware of the software TomsMoComp filter, which i use forever, but the only problem with it is that is will only accepy the YUV or YV12 colour spaces. another problem i have with it is, when it deinterlaces, it for some odd reason leave a 'coloured ghosting' among its objects which sort of irratates me but otherwise it does the best job of deinterlacing ive ever seen and im sure alot of you will agree with me.

so i was wondering, besides from TomsMoComp, is there any other Motion Compensation deinterlacing methods out there? of course besides purchasing a TERANEX

i would really appreciate it if anyone can help me out here with this.

i wil look forward seeing your replies.

Cheers.

[manono]

also, if anyone has read 100fps website, he comes to the fact that Motion Compensation retains full resolution and interlaces with accuracy if not, then fully.

Not quite, but then that sentence of yours I just quoted doesn't really make much sense. Static areas of the frame retain the full resolution, The parts in motion get interpolated in one way or another. And I wouldn't pay much attention to the 100fps site. Some of what he says is plain wrong.

Anyway MVBob and MCBob are among best Motion Compensated deinterlacers in the AviSynth world. But they're so slow as not to be really practical for every day usage.

Now, if you want Motion Adaptive, then Yadif, LeakKernelDeint, or TDeint are good and much faster.

Here's a deinterlacer comparison:

http://heptium.sh.cvut.cz/~integra/deint/

Other deinterlacers have been introduced since that page was created.

[Undead Sega]

i see then, but i forgot to mention, the reason why i use Motion Compebnsation is because it is the best way for em to help recover or rid of interlacing artifacts on 'Palverse' or Pal footage that for some odd reason contains interlace when recorded prgressively.

but about MVBob and MCBob, what kind of Motion Compensation do they use? or is it just purely Motion Compensated?

as for speed, i am running on an Intel Core 2 Dual E6600 2.4GHz with Crucial Ballistix 2GB DDR2-RAM.

[Soopafresh]

Both MV and MC bob use the detection and compensation functions found in the incredible, but single core only plugin called MVtools.dll . So even with a dual-quad-eight core, the deinterlacing performance is severely hindered by the limitations of MVtools.

I like Yadif a lot, and there's also a new deinterlacer/resizer called nnedi which is also quite good: http://forum.doom9.org/showthread.php?t=129953


Post 10 seconds or so of your source media if you can. Might be interesting to test.

[Undead Sega]

well, i use TomsMoComb settings to deinterlace PAL sources (1, 0, 1).

thats all whats needed to deinterlace PAL, nothing heavy or over deinterlacing which results picture degrading and that it is unecessary.

can i achieve these kind of settings with MV and MC bob?

[Soopafresh]

You'll never finish an encode with MC or MV bob, unless you go on holiday while you run the deinterlacers

At least give Yadif a try. The results can be really good.

TomsMoComp is a fine deinterlacer, but five years have passed since it was last updated. Lots of enhancements have gone on in the deinterlacing world.

You can do some fast comparisons of deinterlacers via Avidemux2

[Undead Sega]

very interesting results i see, especially on the 4th page i think, with the lampost, but i think he used a combination with NNEDI (if thats what u were refering to?)

so may i ask as well, both TomsMoComb and NNEDI are both MoCombs that operate exactly the same? besides the algorithm? or something else perhaps? like a different type of Motion Compensation?

[manono]

I repeat Soopafresh's request for a sample. Movies by definition aren't interlaced. You shouldn't need to use a deinterlacer at all. What makes you say it's interlaced?

the reason why i use Motion Compebnsation is because it is the best way for em to help recover or rid of interlacing artifacts on 'Palverse' or Pal footage that for some odd reason contains interlace when recorded prgressively.

It could just have phase-shifted fields and deinterlacing would be the worst thing you could do, where all it might need would be a simple Telecide() from Decomb, or TFM() from TIVTC. Or maybe it's field blended from a bad NTSC2PAL conversion, and you'll need an unblender such as Restore24 or MRestore, both much better than deinterlacing.

All we need is 10 seconds or so. Open a VOB in DGIndex, use the [ and ] buttons to isolate a small section, and then "Save Project and Demux Video". Upload the small result somewhere and post the link here.

[Undead Sega]

thats the one 'Phase-Shifted fields' i dont quite understand why that happens!

anyways, long before this i have read about it, and i was recommended SmartDeinterlace which was ought to do the job, but i was very unhappy with the results when i came across TomsMoComb, thus using a MoComb filter to do the deinterklacing and that somehting like NNEDI has Anti-aliasing, which helps greatly on those shifted fields that creates jagged lines.

i looked on those sites on Yadif and NNEDI but i cant work it out precisely and might need help on it. also with MCBOB which i would like to do. why does everythng have to be in the colour space of YUV?

[jagabo]

thats the one 'Phase-Shifted fields' i dont quite understand why that happens!

It's trival:

Standard definition video is trasmitted as a series of fields, not frames. When computers capture those field they package pairs of them together as frames.

Say the TV station is broadcasting top field first. Given progressive film frames 1, 2, 3, 4... you will see an alternating sequence of top and bottom fields on an SD TV:

1t 1b 2t 2b 3t 3b 4t 4b...

Remember you only see one field at a time on an SD TV, never an entire frame.

A capture device might start capturing with a top field then add the next bottom field to fill out the frame:

1t+1b 2t+2b 3t+3b 4t+4b...

Viewed as frames on the computer they will look just like the original progressive film frames.

But if the capture device starts by capturing a bottom field then adding the next top field:

1b+2t 2b+3t 3b+4t 4b+5t...

The original pairs of fields from the source are now split between consequtive frames -- phase shifted fields. All you have to do to fix this is split the fields apart then recombine them back in-phase.

[Undead Sega]

well this is where Motion Compensation comes in nicely, as it looks at the previous, current and next frame which is actually a field of a previous frame or current frame, and that it can accurately use the information on that to create a progressive scan.

correct me if im wrong on that, im still figuring out this and that.

[manono]

correct me if im wrong on that, im still figuring out this and that.

OK, you're wrong. Besides being much slower, motion compensated deinterlacing is still deinterlacing, no matter how good it is. What you want is a field matcher that will realign the fields properly. Like Telecide or TFM.

To check if you have shifted fields, first look at the frames. If they appear interlaced, next separate the fields with:

SeparateFields()

Open the video in VDub(Mod) and step through it a field at a time. If the fields come in pairs (each unique field followed by a duplicate field), and aren't blended/ghosted, then your problem is phase-shifted fields and it can be quickly and easily fixed.

[Undead Sega]

im using Telecide now and again, what settings do i use for phase-shifted fields'?

[manono]

AssumeTFF#if it's really TFF
Telecide(Guide=2)

It's all in the Decomb Reference Manual:

For simple PAL guidance (tries to maintain lock to the field phase), set guide=2.

[Undead Sega]

ahh okay then.

but for now, i am wanting to try and use NNEDI, but i dont know how to get it working.

can someone give me the right code for it please?

would really appreciate it. thanks.

[manono]

nnedi()

But you don't need it if you really have shifted fields. I wasn't much impressed with it anyway. I was using it as a bobber, and thought Yadif to be better, and nnedi was about 1/6th the speed of Yadif. What is it with you and deinterlacers anyway? You deinterlace as a last resort. And if for DVD, you don't ever deinterlace. Well, just about never.

[Undead Sega]

Okay, i got NNEDI working and it took almost 4 hours for a 1 hour video into HUFFYUV AVI.

the results are more detailed and sharper than TomsMoComb, but it suprisingly resulted with aliasing or jagged edges. i might have to use an Antialiasing filter to help that, then maybe the rsults will be better. any suggestions?

also, i now would want to use MCBob, and i got the avs of it, but it is massive and contains loads of stuff that ic ant even figure out. can someone help with MCBob with the script? i hear and read it gives the best quality deinterlacing and results.

thanks.

[manono]

Not I, sorry. I haven't much use for deinterlacers that encode at less than 1fps.

[Soopafresh]

Not I, sorry. I haven't much use for deinterlacers that encode at less than 1fps.

LOL. Well said. Break out the calendar.