Deinterlacing help

[Blaze_Heatnix]

I thought about learning how to deinterlace properly with Avisynth since I haven't been doing it correctly, poited out by a few people. I have been using AssumeTFF() and Seperatefields() in conjunction of course, followed by a Lanczosresize upscale to 640x480.

So I guess that isn't the way to do it :rolleyes:

I will include a sample clip of what most of my source videos are like. I want to take it and deinterlace from 60 fields to 60 frames per second (well technically it isn't exactly 60, but close) without killing the quality like AssumeTFF.seperatefields plus the upscale does. I have absolutely no clue how to do it properly sadly. Any help is appreciated.

http://www.megaupload.com/?d=EW21UJO2

[Motenai Yoda]

nnedi3 should work

[aegisofrime]

Is this your desired result?

http://www.mediafire.com/?n8b1yek1leuhtml

[Boulotaur2024]

Wasn't there a search function in the past ?

[Blaze_Heatnix]

Is this your desired result?

http://www.mediafire.com/?n8b1yek1leuhtml

Thanks for this aegisofrime, but there is a subtle bobbing in the background as well as chroma ghosting so no I can't go with that one. Sorry.

[Blaze_Heatnix]

Wasn't there a search function in the past ?

Search function? I'm sorry but I don't get what you mean :p

[Hagbard23]

Blaze - it makes no sense to open a new thread for a beaten-to-death-topic like Deinterlacing. This question has been 1000x answered, to speak just about our forum and not others.

Please use the search function - switch on just one braincell and type in: ->"Deinterlacing"<- - you should get 100eds of Threads here at doom9 - as well as a bunch of guides in the Doom9 Guide Section.

Questions like those are driving me crazy.

Back 2 Topic:

Use QTGMC - if you mind thinking a littlebit, then you might find the thread alone.

[Blaze_Heatnix]

Blaze - it makes no sense to open a new thread for a beaten-to-death-topic like Deinterlacing. This question has been 1000x answered, to speak just about our forum and not others.

Please use the search function - switch on just one braincell and type in: ->"Deinterlacing"<- - you should get 100eds of Threads here at doom9 - as well as a bunch of guides in the Doom9 Guide Section.

Questions like those are driving me crazy.

Back 2 Topic:

Use QTGMC - if you mind thinking a littlebit, then you might find the thread alone.

Well really there is hardly any need for childish attitude. I hate to say it, but i'm relatively new to forums so I still don't quite get what goes where among other things. But whatever man, if that's how it is then you should have just said "You can search specifically about deinterlacing if used the search function" or something. Or maybe I made this thread because I wanted to know how to deinterlace my specific source video as well as to learn some new things in the process. After all, that's not wrong no matter how many threads there are.

Furthermore, I have no idea how this "QTGMC" works so you've lost me.

[Hagbard23]

Omg....:confused:

Please follow the following advice:

->Click "Search" in the upper region of your Doom9 window
->Type in: "QTGMC"
->READ
->Thats it - youre done

P.S.: The only one who is behaving childish is -unfortunately- you...

Sorry, but that's the way it is. Folks before me told you to use the search funtion - you didn't...childish - isn't it?

Good luck in finding someone teaching you the ABC...

BTW: Using the Search Function is one Rule of our Forum - nothing new and nothing too hard for newbies..isn't it...you should have read the rules before opening a new thread...

BTW2: Your way to do deinterlacing is a regular one...some people still use that kind of deinterlacing and they will for good...unless a better, new method is found. The Majority of people use deinterlacing plugins, such as YADIF, TDeint or (Q)TGMC. There are very fast ones, and ones for very good quality, but they have all their disadvantages. For exactly that reason some people still use your method, which isn't that false at all, since it eliminates all combing in a relatively good speed.

Is that un-childish enough for you taste...? If you want to learn more, you HAVE to use the Search Function and/or Google. Hundreds of Thousands of People had the same question before you.

[Blaze_Heatnix]

Just because you may be smarter than me doesn't mean you can act pointlessly irrational. All I want to do is learn to deinterlace this clip specifically, and going up and down the forums looking for something like that is like a needle in a haystack. Something is wrong with you, and it is because of people like you that I have no interest in forums because those people give said forums a bad rep. I get the fact that you are indeed trying to help me out. But talking to me in such a way make you look bad, regardless of what you think is right or not, and you can deny it all you want, but it won't change the fact. Why is it bad to post a new thread like this when it has overall differences with what a person is looking for or trying to understand?

Oh and just an aside, the reason I won't use QTGMC is mainy because it does the same thing as other, less complex deinterlacers can.

[Hagbard23]

Just because you may be smarter than me doesn't mean you can act pointlessly irrational.
What -exactly- is irrational? Tell me more... ;)

All I want to do is learn to deinterlace this clip specifically, and going up and down the forums looking for something like that is like a needle in a haystack.
defititely not true - you want a standard-conversion...1000nds of people done it before you...your situation is a standard situation solved many many times.

Something is wrong with you, and it is because of people like you that I have no interest in forums because those people give said forums a bad rep.
No - i'm just fine...indeed i can laugh ... i'm feeling just good. And: Check my posts and you'll learn more...

I get the fact that you are indeed trying to help me out. But talking to me in such a way make you look bad, regardless of what you think is right or not, and you can deny it all you want, but it won't change the fact.
My talking is (compared to watchdog Ghitulescu) just normal...nothing offending...

Why is it bad to post a new thread like this when it has overall differences with what a person is looking for or trying to understand?
Because it breaks the rules... ;) Think about it twice and you'll understand

Oh and just an aside, the reason I won't use QTGMC is mainy because it does the same thing as other, less complex deinterlacers can.
That is your problem.
In Fact QTGMC can do much more...but as long as you do not check it out, you'll never know..

And:

Please read the Doom9 Guides about deinterlacing...your (standard) situation is described very good.

[Blaze_Heatnix]

If you want to know what Irrational means, google it. Unlike you, I won't make fun of you just because you don't know what it means.

But fine with me. I'm glad you had a laugh, because if I recall, you said "Questions like those are driving me crazy." If they realistically drove you crazy then there is indeed something wrong with you, letting something so meager get to you.

Anyway, I'll do you a favor and take your advice instead of Trolling. I can indeed figure it out, after all. What simpleton wouldn't be able to, right?

[Hagbard23]

Okay...i will do YOU a favor and give you this:

http://www.100fps.com/

Please read it carefully - nearly everything you may want to know is described very good...even to newbies.

You can read here for further information about DVD-Backups:

www.doom9.org

You can read here a very good guide:

http://neuron2.net/LVG/interlacing.html

Or here:

http://www.helpedia.com/guides/Deinterlacing-guide4-page1.html

Something about Telecine-Process and Interlacing as well:

http://www.doom9.org/ivtc-tut.htm

And last but not least the guide of the Deint-Guru SCHARFIS-BRAIN (in german):

http://home.arcor.de/scharfis_brain/ExotischesInterlacing/

And here some Video Guide to deinterlacing:

http://www.youtube.com/watch?v=JkQDuqZaQAI

Would THAT be satisfying to you? Or do you really want, that i tell all the stuff described in those guides again? Only for your person? I do not want to do that, i hate double/triple/quadriple... work..it is just sufficient to tell it once...

And: Doom9 has a good reputation, just BECAUSE we take the rules some kind of strict - otherwise every week someone like you will ask the same question and that will do a hell of a chaos out of the forums...do you understand it now? It is nothing personal - i didn't want to hurt your feelings, just tell you how it normally goes.

And that you are not in the condition to use the search function is strange enough...don't tell me something is wrong with ME, when it is with you... ;)

P.S.: The highest quality (subjective) deinterlacer for Avisynth is at the moment TGMC/QTGMC with some kind of NEEDI, it is too new to be described in the guides, but they are described very good inside their own threads here at doom9...

[Inspector.Gadget]

Oh and just an aside, the reason I won't use QTGMC is mainy because it does the same thing as other, less complex deinterlacers can.

If you know so much about deinterlacing, why didn't you do it in a remotely sensible way the first time around before screwing with SeparateFields() and trying to blame it on MeGUI? And why start a whole new thread to continue essentially the same discussion?

[Didée]

Same quote -
Oh and just an aside, the reason I won't use QTGMC is mainy because it does the same thing as other, less complex deinterlacers can.
I'm not going to say that Q/TGMC is the ultimate answer to deinterlace this footage, because of the particularities of non-natural content.

But be assured, Q/TGMC does a quite few things that no other deinterlacer currently can do. (On planet Avisynth, at least.)
_____

However, from a diffeent point of view, you're perfectly correct: Q/TGMC does exactly the same trivial stuff as any other deinterlacer. Namely: it deinterlaces. :D

[Blaze_Heatnix]

If you know so much about deinterlacing, why didn't you do it in a remotely sensible way the first time around before screwing with SeparateFields() and trying to blame it on MeGUI? And why start a whole new thread to continue essentially the same discussion?

It was MeGUI, otherwise I wouldn't have said so. You now have a source to download. Do me a favor and download it and use it with MeGUI with Avisynth script:

avisource("video")
assumetff.separatefields
lanczosresize(640,480)

Come back and tell me what you got out of it, then you will know why I want to know about deinterlacing.


Ok now, let me ask this. What if I used this script:

avisource("video")
TDeint(mode=1,order=1,mthreshL=0,mthreshC=0,type=0,mtnmode=1,sharp=true)

That seems to look fine, without any chroma ghosting or bleeding. But it bobs. Is there a way to have that same output without bobbing?

Ok look, all I'm going for here is basically the same thing as assumetff.separatefields+lanczosresize(640,480) but without bobbing. That is basically all. I never intended to start any nonsence with you guys. I just hate being talked down to when the same thing could be said without any insensible behaviour overall. Christ, if you guys feel I'm offending you still, I'm sorry >_>

[Hagbard23]

I just hate being talked down to when the same thing could be said without the assholish behaviour overall. Christ, if you guys feel I'm offending you still, I'm sorry >_>

Be Careful, what you say, little boy...or you get banned...

For TDEINT : set mode=0 for same rate output...

For BOBBERS:
you can use all bobbers, with either "SelectEVEN()" or "SelectODD" afterwards....simple, but working...(prof. name: "Discard-Deinterlace")

Your method does nothing else, than converting Fields into Frames. Therefor you get a 2xRate output (25i to 50p , or 30i to 60p). You HAVE to select one frame per cycle out to get same rate output (25i to 25p or 30i to 30p). I think that basically was your mistake. Separatefields alone is not sufficient for same-rate-output.

If both fields(of a interlaced frame) have same quality, then it doesn't matter, wether you use SelectEVEN or SelectODD. But there are scenarios, in which one field has worse quality. In that case you have to select the better one...


BTW: I am much too friendly, if i consider, what you wrote just one post ago...keep in mind, that the tone makes the music..

[Blaze_Heatnix]

Fixed that sentence, apologies. So anyway, you say to use selecteven or odd after the deinterlacer. That halves framerate. Honestly, I'm mostly uneducated with bobbing deinterlacing since I've been blending fields for ages until I found about assumetff.separatefields. That's what confused me most with deinterlacers, since they all bob if you want to keep full 60 frames, as far as I can tell.

Also regarding your last edit, I am not trying to keep same rate. Did you see my sample video? I need double rate from it =\

[Hagbard23]

That seems to look fine, without any chroma ghosting or bleeding. But it bobs. Is there a way to have that same output without bobbing?

i do not understand you...bobbing means: Double-Framerate...

you say: i do not want to bob...

now you say: i want double-framerate

WHAT exactly do you want?

Thats the reason i advised you to read the guides...it is important to understand the terminology... ;)...

I stronly recommend you to use QTGMC, because i think, that is what you want...you can't get better quality...

[Blaze_Heatnix]

i do not understand you...bobbing means: Double-Framerate...

you say: i do not want to bob...

now you say: i want double-framerate

WHAT exactly do you want?

Thats the reason i advised you to read the guides...it is important to understand the terminology... ;)...

I'm trying to say that I need double framerate, meaning yes, I guess I need to bob deinterlace, however, I don't want the result of this to bob. Meaning, I want double rate without the picture bobbing up and down. The way you're talking now sounds like having double rate without the picture bobbing as a result isn't possible...

Don't get me wrong. If I have to use QTGMC, I will try it, but I feel for this particular source, I don't need to go so high with my options for deinterlacers to get a desired result.

[Didée]

bobbing means: Double-Framerate...
Not originally, that's just naming for convenience.

When separating fields (with or w/o resizing), then the resulting frames will bob up-down-up-down. And that's the sole origin of the name "bob-deinterlacing". ;)


Blaze_Heatnix: if you want to try tdeint with less bobbing, set the mthreshL/mthreshC parameters to non-zero values. Default for both is '6' (iirc), try values from 4 to 12.

Also try Yadif.

Better don't try QTGMC, because it's so useless and does nothing that any other bob/deinterlacer could also do. :p ;)

[Blaze_Heatnix]

Blaze_Heatnix: if you want to try tdeint with less bobbing, set the mthreshL/mthreshC parameters to non-zero values. Default for both is '6' (iirc), try values from 4 to 12.

Also try Yadif.

Better don't try QTGMC, because it's so useless and does nothing that any other bob/deinterlacer could also do. :p ;)

lol you guys really want me to use that QTGMC huh? Well, like I said, I will but only if absolutely necessary.

But anyway, If I change the value of mthreshL/C there is artifacts left behind. I can't have that.

[aegisofrime]

Blaze_Heatnix, FYI that little file I uploaded for you was done with QTGMC. I didn't see any problems with Chroma, but if you do you might have to tweak the settings a bit. I use it for film sources with minimal tweaking so I don't know how to handle video game sources.

[Inspector.Gadget]

It was MeGUI, otherwise I wouldn't have said so. You now have a source to download. Do me a favor and download it and use it with MeGUI with Avisynth script:

avisource("video")
assumetff.separatefields
lanczosresize(640,480)



I get 640x480 output at 60000/1001 progressive in both MeGUI and when previewing in Media Player Classic Home Cinema, as expected. Of course, I used correct Avisynth syntax as excerpted below. If you somehow wound up with "240x480 or something and the video is super sped up" it was your error. MeGUI has had many bugfixes and sets its own variables in Avisynth only in the limited case of remembering anamorphism to be retained on later muxing of re-encoded video.

DirectShowSource("C:\x3.avi", audio=false)
AssumeTFF()
SeparateFields()
LanczosResize(640,480)
Info()

[Gavino]

I'm trying to say that I need double framerate, meaning yes, I guess I need to bob deinterlace, however, I don't want the result of this to bob. Meaning, I want double rate without the picture bobbing up and down.
The simplest possible way to do that is just to use the internal Bob (http://avisynth.org/mediawiki/Bob)() filter.

AviSource("video.avi")
Bob()

This basically does the same as your SeparateFields.LanczosResize (although using BicubicResize), except that an allowance is made for the different vertical alignment of odd and even fields during the resize, eliminating the 'bobbing' effect. It's very simplistic compared to more 'intelligent' deinterlacers, but for some sources it may be 'good enough'.

[Blaze_Heatnix]

Blaze_Heatnix, FYI that little file I uploaded for you was done with QTGMC. I didn't see any problems with Chroma, but if you do you might have to tweak the settings a bit. I use it for film sources with minimal tweaking so I don't know how to handle video game sources.

Ah... Well, I just tryed QTGMC as well... I noticed it looked similar to the file you sent me so I figured that's what it was. I said Chroma Ghosting before, but I meant color bleeding.

Well here's something I should mention, I need to know a deinterlacer that works outside of YV12 colorspace. If you deinterlace anything in YV12, well... There is bleeding and that, imo is unacceptable =\

[Inspector.Gadget]

If you deinterlace anything in YV12, well... There is bleeding and that, imo is unacceptable =\

Also incorrect. If this were true every DVD-to-X procedure that involved deinterlacing would produce obvious artifacts.

[Didée]

lol you guys really want me to use that QTGMC huh?
No, not really. Just pulling your leg. Actually, the sample of aegisofrime shows that QTGMC has its own problems with this kind of source - there's lots of residual field bobbing. (Interestingly, it's also there with the repair-thingy completely deactivated, which is mysterious. Stuff to investigate.)

Simple:

AviSource("thesource.avi")
AssumeTFF()
Yadif(mode=1)


With better interpolation:

AviSource("thesource.avi")
AssumeTFF()
YadifMod(mode=1,edeint=NNEDI3(field=-2))

[Blaze_Heatnix]

I get 640x480 output at 60000/1001 progressive in both MeGUI and when previewing in Media Player Classic Home Cinema, as expected. Of course, I used correct Avisynth syntax as excerpted below. If you somehow wound up with "240x480 or something and the video is super sped up" it was your error. MeGUI has had many bugfixes and sets its own variables in Avisynth only in the limited case of remembering anamorphism to be retained on later muxing of re-encoded video.

DirectShowSource("C:\x3.avi", audio=false)
AssumeTFF()
SeparateFields()
LanczosResize(640,480)
Info()

And this is AFTER encoding?

[Inspector.Gadget]

What? I'm using your HuffYUV file as input and previewing in Avisynth. Encoding shouldn't make any difference because frames are delivered to the renderer appearing as they do when passed to an encoder.

[Blaze_Heatnix]

What? I'm using your HuffYUV file as input and previewing in Avisynth. Encoding shouldn't make any difference because frames are delivered to the renderer appearing as they do when passed to an encoder.

I know what you mean, really I do. Encode it with x264 with mp4 as the format.

[Inspector.Gadget]

Just did it with a test render with an arbitrary video input. No issue.

[Blaze_Heatnix]

No, not really. Just pulling your leg. Actually, the sample of aegisofrime shows that QTGMC has its own problems with this kind of source - there's lots of residual field bobbing. (Interestingly, it's also there with the repair-thingy completely deactivated, which is mysterious. Stuff to investigate.)

Simple:

AviSource("thesource.avi")
AssumeTFF()
Yadif(mode=1)


With better interpolation:

AviSource("thesource.avi")
AssumeTFF()
YadifMod(mode=1,edeint=NNEDI3(field=-2))

Huh? That's wierd... It sayd "dont know what yadif means"

...and yes I have it downloaded and etc.

[Blaze_Heatnix]

Just did it with a test render with an arbitrary video input. No issue.

What the... Now I'm confused. This is MeGUI 0.3.5.0? That has to be since auto updating mines doesn't go past 0.3.5.0...

[Didée]

Yadif cannot be auto-loaded from the plugins directory. You have to load it manually with Load_stdcall_plugin("X:\path\to\yadif.dll")

[Blaze_Heatnix]

Yadif cannot be auto-loaded from the plugins directory. You have to load it manually with Load_stdcall_plugin("X:\path\to\yadif.dll")

Ohhh I see. Well yadif bobs, but yadifmod curiously bobs only what moves it seems. I'm starting to think maybe I should just stick with separatefields :(

Additionally, now I'm curious as to why MeGUI encodes my video oddly and not Inspector Gadget... I guess I need to point out that I know absolutely nothing whatsoever about MeGUI other than how to encode something.

[Inspector.Gadget]

What the... Now I'm confused. This is MeGUI 0.3.5.0? That has to be since auto updating mines doesn't go past 0.3.5.0...

MeGUI0.3.5.28 x64 using the Development server.

However, your problem is not MeGUI-related. What you've bumped into is a condition I was finally able to reproduce: recent builds of x264 automatically weave input detected as interlaced content with separated fields, instead of simply dumping them to output as a renderer would. This is why you came out with 640x960i60fields output instead of 640x480p60frames. All the software works as intended, because the code that achieves this result is within x264 instead of MeGUI or Avisynth. When fed content that's been flagged in a silly way, x264 has no way of knowing that the flags are incorrect.

This is exactly why a real deinterlacer is the better option, because it leaves x264 with frame-based progressive input.

[Didée]

The darn footage has halved vertical resoltion anyway.

AssumeTFF().SeparateFields().PointResize(width,height).AssumeFramebased()

Purrfect. The poorest and theoretically worst of all possible bob-deinterlacing methods ... practically delivers the best possible result in this case.

Hilarious.

[Blaze_Heatnix]

MeGUI0.3.5.28 x64 using the Development server.

However, your problem is not MeGUI-related. What you've bumped into is a condition I was finally able to reproduce: recent builds of x264 automatically weave input detected as interlaced content with separated fields, instead of simply dumping them to output as a renderer would. This is why you came out with 640x960i60fields output instead of 640x480p60frames. All the software works as intended, because the code that achieves this result is within x264 instead of MeGUI or Avisynth. When fed content that's been flagged in a silly way, x264 has no way of knowing that the flags are incorrect.

This is exactly why a real deinterlacer is the better option, because it leaves x264 with frame-based progressive input.

Aha... That explains it. Man what a bummer.

Now that leaves a deinterlacer... What one could I possibly use that does double frame rate without bobbing the picture.

[bcn_246]

(Q)TGMC is, pretty unquestionably, the best quality deinterlacer around. However, I would make sure you try some of the following (faster) deinterlacers first.

* TomsMoComp
* LeakKernalDeint
* TDeint
* YadifMod (the reason you got the loading error was because you had the original Yadif, which is a 'C' plugin). I have had alot of success using 'YadifMod(edeint=NNEDI2)'

What one could I possibly use that does double frame rate without bobbing the picture.
When you say you don't want bobbing do you mean you dont want double framerate (in which case, just add either 'Decimate(2)' or 'SelectEven()' after QTGMC), or that your output the picture is actually 'bobbing' (jumping up and down by 1 line)?

If your source is upsized from half-resolution maybe using NNEDI2 on-its-own would yield good results?

Ben

[Blaze_Heatnix]

The darn footage has halved vertical resoltion anyway.

AssumeTFF().SeparateFields().PointResize(width,height).AssumeFramebased()

Purrfect. The poorest and theoretically worst of all possible bob-deinterlacing methods ... practically delivers the best possible result in this case.

Hilarious.

lol That is indeed perfect, and basically what I have been using all this time (now you know why). But now, how am I supposed to run that in MeGUI?

[Blaze_Heatnix]

Before using (Q)TGMC (which is, pretty unquestionably, the best quality deinterlacer around) try some of the following (faster) deinterlacers.

* TomsMoComp
* LeakKernalDeint
* TDeint
* YadifMod (the reason you got the loading error was because you had the original Yadif, which is a 'C' plugin). I have had alot of success using 'YadifMod(edeint=NNEDI2)'


When you say you don't want bobbing do you mean you dont want double framerate (in which case, just add either 'Decimate(2)' or 'SelectEven()' after QTGMC), or that on your output the picture is actually 'bobbing' (jumping up and down by 1 line)?

Ben

By bobbing I meant that I DO want double rate but at the same time, I DON'T want the video jumping up and down by one frame. Is there some sort of "jumping removal" to kind of produce a steady picture?

[Didée]

But now, how am I supposed to run that in MeGUI?
How? Erh, by writing that line into the script?


Just a thought, the resolution could be improved greatly by using eedi2 (or eedi3) for anti-aliasing.

pointbob - - - - - - - - pointbob + eedi2 (with contrasharpening)
http://img338.imageshack.us/img338/9586/pointbob.th.png (http://img338.imageshack.us/i/pointbob.png/) http://img151.imageshack.us/img151/5549/pointbobeedi2.th.png (http://img151.imageshack.us/i/pointbobeedi2.png/)

One can like it, or one can prefer to keep the original chunky retro look. It's a matter of taste.

[Blaze_Heatnix]

How? Erh, by writing that line into the script?


Just a thought, the resolution could be improved greatly by using eedi2 (or eedi3) for anti-aliasing.

pointbob - - - - - - - - pointbob + eedi2 (with contrasharpening)
http://img338.imageshack.us/img338/9586/pointbob.th.png (http://img338.imageshack.us/i/pointbob.png/) http://img151.imageshack.us/img151/5549/pointbobeedi2.th.png (http://img151.imageshack.us/i/pointbobeedi2.png/)

One can like it, or one can prefer to keep the original chunky retro look. It's a matter of taste.

Oh... Well I'll be =\

So I guess adding assumeframebased was a sideshow to get MeGUI to encode it properly or something? Eh, Well I guess I should stop talking about it since it works now.

I find that abolutely hysterical that such a simple solution was completely overlooked, when I was, all this time, using almost the same script. Thank you very much. All goes to show that some things are better off being deinterlaced the old fashioned way, so to speak.

[bcn_246]

You could also try using the AntiAliasing script posted a while ago by Didee (http://forum.doom9.org/showthread.php?p=553304#post553304) after pointbob instead of EEDI2...

- Ben

[Blaze_Heatnix]

Thanks guys. I'm actually comfortable with the standard look, but I also like how smooth the terrain in particular looks with the extra filters. I'll try some of them out.

[Hagbard23]

ah..too late...

[Boulotaur2024]

Just a thought, the resolution could be improved greatly by using eedi2 (or eedi3) for anti-aliasing.

pointbob - - - - - - - - pointbob + eedi2 (with contrasharpening)
http://img338.imageshack.us/img338/9586/pointbob.th.png (http://img338.imageshack.us/i/pointbob.png/) http://img151.imageshack.us/img151/5549/pointbobeedi2.th.png (http://img151.imageshack.us/i/pointbobeedi2.png/)

Didée, could you please post the script you used :D ?

:thanks:

[Didée]

Don't have the script with me ... but iirc it went like this:
AviSource("x3.avi")
AssumeTFF().SeparateFields().PointResize(width,height).AssumeFramebased()
pointbob = last
eedi2(field=-1,maxd=4)
sbr()
BicubicResize(width,height,-1,1,0,0.5,width,height)
repair(sharpen(1),pointbob,1)
return(last)
#------------------------------
function sbr(clip c) {
rg11 = c.removegrain(11,-1)
rg11D = mt_makediff(c,rg11)
rg11DD = mt_makediff(rg11D,rg11D.removegrain(11,-1)).mt_lutxy(rg11D,"x 128 - y 128 - * 0 < 128 x 128 - abs y 128 - abs < x y ? ?")
c.mt_makediff(rg11DD,U=2,V=2)
}

[creaothceann]

Yadif cannot be auto-loaded from the plugins directory. You have to load it manually with Load_stdcall_plugin("X:\path\to\yadif.dll")

... which can be done in an .avsi script. :)

That's why there's a directory "packages" in my AviSynth directory, which contains several versions of filters in their own subdirectories if required (together with their documentation and other distributed files).