Plain deinterlacing or Bob+SelectEvery: what do you prefer and why?

[Blue_MiSfit]

@Steve,

Are you multithreading with x264? Probably, just wanted to check

@radar,

Your source looks like pure interlaced NTSC - probably originating on DV. Any deinterlacer is worth trying. If you want to do a format conversion (to PAL, or any resizing at all), then bobbing (double rate) is required. Here's a good place to start with a personal favorite of mine (good balance of speed and quality)

return 29.97fps (same rate)

mpeg2source("C:\radars test\VTS_01_1.d2v")

AssumeBFF()
tdeint(mode=2)

return 59.94fps (bobbing)

mpeg2source("C:\radars test\VTS_01_1.d2v")

AssumeBFF()
tdeint(mode=1)

Replace the d2v path with your own project of course

MVBob should work very nicely on that as well (of course!). Worthy contenders are also KernelDeint, TomsMoComp, etc...

~MiSfit

[radar]

hi Blue_MiSfit,do i just load tdeint and try your script.

[Blue_MiSfit]

Well, I'm assuming that you have AviSynth installed, and that TDeint is in your plugins folder.

You're not being too clear about your level of understanding

And no, you will have to make SOME modifications to my script, like the path to your D2V project. If you don't know how to make a D2V project - get DGIndex. It's a nice utility for getting MPEG-2 from multiple VOBs into one coherent stream that AviSynth loves.

Again, what is your end goal?

~MiSfit

[radar]

i have very little understanding on using filters.i do have avisynth loaded and have many filters in my plug in.(TDeint).

im using dvdrebuilder with the filters.i know how to set paths(loadplugins).what i have trouble with is what you use for a script?also what plugins to use?is thier a order that you use when setting the paths for each plugin you use?

thanks for the help...

[steve77]

@Blue_MiSfit: Yes I'm setup on 2 threads. x264 isn't so slow on my machine, I'm sure it's the filters I'm using.

I'm just making sure that everything is OK.

[Kamui-]

Im getting error:

RemoveGrain: invalid mode 20

For a second I thought I read that someone had the error msg somewhere so I went through all the posts 4 times and still havnt found it yet @@, I'm prolly getting old or blind or both =X

Script as follow:

loadplugin("C:\Avs filters\tdeint_25_dll_20060410\tdeint.dll")
loadplugin("C:\Avs filters\MaskTools-v1.5.6\masktools.dll")
loadplugin("C:\Avs filters\mvtools-v1.6.2\mvtools.dll")
loadplugin("C:\Avs filters\masktools-v2.0a30\mt_masktools.dll")
loadplugin("C:\Avs filters\EEDI2v091\eedi2.dll")
loadplugin("C:\Avs filters\removegrain_25_dll_20050501\RemoveGrainSSE3.dll")
loadplugin("C:\Avs filters\removegrain_25_dll_20050501\repairsse3.dll")
loadplugin("C:\Avs filters\reduceflicker\ReduceFlickersse3.dll")
loadplugin("C:\Avs filters\medianblur\medianblur.dll")
import("C:\Avs filters\MCBob_v03c.avs")

Using AVS 2.56 and I have AvsRecursion.dll in /system32

Solution: Yes it was the removegrain, I think I've dled 3 different ver and the one on SeeSaw page worked quite nicely.

[Pookie]

Your version of RemoveGrain is the culprit.

[Livesms]

Looks like McBob sounds better then any other deinterlace, but here is my samples

Original - McBob 0.3 - MvBob
Strange color lines with McBob 0.3 and absolutely clear picture with MvBob. Why?

[foxyshadis]

The frequency pattern is present in the original, but not nearly as strong. Some component of mcbob must be amplifying it, hmm. You might want to use Defreq/Fanfilter either before or after in order to remove it, as well as the luma frequency going in the other direction.

[Livesms]

Originally Posted by foxyshadis

The frequency pattern is present in the original, but not nearly as strong. Some component of mcbob must be amplifying it, hmm. You might want to use Defreq/Fanfilter either before or after in order to remove it, as well as the luma frequency going in the other direction.

Can you give an example you see for my case?

[morsa]

Well, in fact I've been having lots of problems with Mcbob and the chroma channel.
Everytime I have some fast motion scenes ( like a soccer match) I get some color ghosts for the ball.
The effect is like a faint color copy of the yet to come next frame.
Anybody else with the same situation?

BTW, I guess it would be much better to continue discussions about MCbob in its own thread

http://forum.doom9.org/showthread.php?t=124636

[wonkey_monkey]

Can you post your script or a sample original frame? Perhaps you did a converttoyv12 without specifying interlaced=true, or perhaps the fields were never completely separate in the source.

David

[Didée]

Thinking over it, it's quite possible that such chroma ghosts might arise: I remember to have used a fixed luma->chroma linking in some parts of the script, for the ease of things. (Can't remember to have seen such ghosts from MCBob, but that's no argument.)

A sample with a few frames showing the problem would be a good idea.

[morsa]

Right now I'm just trying to isolate the problem.Many different things to check.It is from an HDV source (Sony), so indeed one possibility is that the crappy realtime Mpeg2 compression is ***** the chroma fields as David pointed out.

The only thing that I can't understand is why those ghosts seem to not appear if I directly deinterlace the stuff using Smart Deinterlacer inside Vdub workflow.
The problem is that I can't post that stuff because it is not mine.It is from somebody else's project.
Anyway I managed to have the least noticeable ghosts (but they're still there).I will search for the original script, so you can tell me If I'm doing some nasty things.
Thank you as always.

[scharfis_brain]

the artifacts are already present in the source.
just replace mcbob() with a simple bob() and you'll see.

so mcbob isn't the one to blame.

[Livesms]

Originally Posted by scharfis_brain

the artifacts are already present in the source.
just replace mcbob() with a simple bob() and you'll see.

so mcbob isn't the one to blame.

and how can i remove this artifacts?

[scharfis_brain]

either
- heavy temporal blurring of the chroma planes,
- some spatial wavelet (or fourier) denoising
or
a combination of both.

but I am not sure.

Better ask this in another (new) thread, as it doesn't blong to mcbob() anymore.

[morsa]

Anyway, one thing that is easily reproducible is this:

Whenever you have some kind of fast moving object (example: windshield wipers) you get as a result the deinterlaced wiper with some ghosting (just the chroma part) from the image behind them.
I guess this could be related to what Didee above told about the chroma copy.

[Terka]

Could mvbob/mcbob use yadif deinterlacer?

[Didée]

It could, but what for? Quality won't increase, speed increase would be academic ...