Interlacing Issues

[CodeZTM]

Allrighty...

Here I've been assuming that my script has been de-interlacing my footage, but come to find out (through a few betas here and there to people), it hasn't.

Anyway, I would love some assistance.

I'm using the following script

Code: Select all

mpeg2source("C:\1.d2v")
Tdecimate(mode=4)
Crop(8,0,-8,-0)
LanczosResize(640,480) 
Deblock(quant=25)
Deen("w3d",3,3,5)
Undot()
TemporalCleaner()
aWarpSharp(depth=8)
BiFrost(interlaced=false)
BlendBob

as well as the deinterlace filter in VirutalDubMod.

I've used this and this for references, as well as the doom9 forum. Nothing just seems to scream out what I'm doing wrong, so I thought I would ask.

Here's my footage:


Also, I'd love to ask another question regarding widescreen footage, since I'm totally new to that whole concept as well. X_X

What scriping is needed to take 4*3 AR, 720*480 FS to change it to 16*9 640*352 FS. I think I've got it down, but I'd like to just make sure.

Here's my scripted footage I've got now:

[Kariudo]

Your script isn't doing any deinterlacing atm.
decimate and Tdecimate are meant to delete duplicate frames, your script isn't doing anything to restore the original frames (from the fields), so tdecimate isn't doin much for ya (nor is blendbob).

If you're working with NTSC source, you should probably IVTC (TFM followed by Tdecimate)
another option is to deinterlace with something like leakkerneldeint and then use blendbob (and you might have to clean up with tdecimate afterwards)

you should avoid cropping/resizing until after you take care of the interlacing (I usually just throw it on to the very end of my script)

Maybe you just picked a good frame, but I'm not seeing rainbows on the original footage, so you may want to just get rid of bifrost

I personally don't like awarpsharp, it always seems to really distort the lines (not to mention make them a lot thinner). vmtoon() can be used as just a sharpener, but I prefer LimitedSharpenFaster() for sharpening

[CodeZTM]

Thanks kindly. I've spent almost all of today researching Avisynth, so I'm grateful for your assistance. I'm learning how to toy around with it, so I'm hoping I won't have as many issues in the future. ^_^

[Qyot27]

What scriping is needed to take 4*3 AR, 720*480 FS to change it to 16*9 640*352 FS. I think I've got it down, but I'd like to just make sure.

Code: Select all

Lanczos4Resize(640,480)
Crop(0,64,0,-64)

or

Code: Select all

Crop(0,64,0,64)
Lanczos4Resize(640,352)

Of course, you can play around with the values for y and -y, just so long as they equal out to 128. And you could use any of the available resizers - I just personally tend to default to Lanczos4.

Another tip: if you have to do any smoothing on a source, do so after cropping but before using AddBorders (if you need to use AddBorders, that is). Keeps the smoothing contained to the actual image rather than parts that don't need to be smoothed.

[CodeZTM]

What scriping is needed to take 4*3 AR, 720*480 FS to change it to 16*9 640*352 FS. I think I've got it down, but I'd like to just make sure.

Code: Select all

Lanczos4Resize(640,480)
Crop(0,64,0,-64)

or

Code: Select all

Crop(0,64,0,64)
Lanczos4Resize(640,352)

Of course, you can play around with the values for y and -y, just so long as they equal out to 128. And you could use any of the available resizers - I just personally tend to default to Lanczos4.

Another tip: if you have to do any smoothing on a source, do so after cropping but before using AddBorders (if you need to use AddBorders, that is). Keeps the smoothing contained to the actual image rather than parts that don't need to be smoothed.

Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!

Now I don't have a headache anymore. ^_^

[mirkosp]

Code: Select all

Crop(0,64,0,64)
Lanczos4Resize(640,352)

Shouldn't it be Crop(0,64,0,-64) as well? Sorry if I'm wrong, but I preferred to ask, just in case... [/code]

[Kariudo]

yep, crop syntax is crop(int left, int top, -int right, -int bottom)
it would be really easy to internalize the "-" sign...but it's part of avisynth, so it's probably just easier to play along with it

[Qyot27]

Code: Select all

Crop(0,64,0,64)
Lanczos4Resize(640,352)

Shouldn't it be Crop(0,64,0,-64) as well? Sorry if I'm wrong, but I preferred to ask, just in case... [/code]

Yeah, I forgot it on that one.

[NekoMayumi]

it would be really easy to internalize the "-" sign...but it's part of avisynth, so it's probably just easier to play along with it

No it wouldn't. If the last two parameters are positive it takes those as width/height.

So Crop(0,64,0,64) on a 720x480 stream would output 720x64.

[Kariudo]

all you'd have to do is put top=-top and left=-left in the code...