digitalFAQ.com Forums [Archives]

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)
-   Avisynth Scripting (http://www.digitalfaq.com/archives/avisynth/)
-   -   Avisynth: MA script for interlaced sources? (http://www.digitalfaq.com/archives/avisynth/6120-avisynth-ma-script.html)

Boulder 10-15-2003 07:56 AM

Avisynth: MA script for interlaced sources?
 
Code:

nf=0

MPEG2Source("path\video.d2v")

Crop(enter your values here, crop height mod 4, width mod 2!)

SeparateFields()
UnDot()
BicubicResize(enter your values here, height/2!)
MergeChroma(Blur(1.5))
MergeLuma(Blur(0.1)) # use only if the video won't get too blurry!
STMedianFilter(4,32,0,0)

SwitchThreshold = (Width<=352) ? 4 : (Width<=480) ? 3 : 2
even=SelectEven().ScriptClip("nf=YDifferenceToNext()"+chr(13)+"nf>=SwitchThreshold?unfilter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))):TemporalSoften(fmin(round(2/nf),6),round(1/nf),round(3/nf),0,2)")
odd=SelectOdd().ScriptClip("nf=YDifferenceToNext()"+chr(13)+"nf>=SwitchThreshold?unfilter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))):TemporalSoften(fmin(round(2/nf),6),round(1/nf),round(3/nf),0,2)")
Interleave(even,odd)
Weave()

AddBorders here
Limiter()

function fmin( int f1, int f2) {
  return ( f1<f2 ) ? f1 : f2
}

This script is meant for interlaced encodes. As I put most of my TV caps on DVD these days, I encode them as interlaced to preserve the details, sharpness and the smooth motion. The even= and odd= lines contain the whole MA portion of the script on the same line. The word wrapping just puts them on several lines.

Spatial filters affect the video more because SeparateFields() splits each frame into two fields, so 720x576 becomes 720x288. That's why I've lowered the STMedianFilter values, MergeLuma may also appear to be too strong. You may want to try replacing STMedianFilter with FluxSmooth. Just don't do any temporal filtering at that point (use FluxSmooth(-1,4) for example)!

DCTFilter can introduce some artifacts near the top and bottom of the video. This can be avoided by cropping slightly. It's probably due to the filters nature, unfortunately I can't give you any better explanations.

This is only a small sample based on Kwag's optimal script. Feel free to bash it around :twisted:

Boulder 10-15-2003 08:21 AM

Some remarks:

SwitchThreshold may need tweaking. Kwag?

kwag 10-15-2003 09:50 AM

Quote:

Originally Posted by Boulder
Some remarks:

SwitchThreshold may need tweaking. Kwag?

Looking at it now :)
Maybe make SwitchThreshold a manual constant, until you get the desired switching value :?:
Just include: ScriptClip("Subtitle(String(nf),1,30)") after your limiter function call. Then you can see the dynamic value of nf as you play your .avs in Vdub or any player, and this way, you can see the activity level and tune the SwithTreshold selection line depending on activity/resolution.

-kwag

Boulder 10-15-2003 10:00 AM

Thanks! I've often wondered how I would see the 'nf' value at each frame..never really got around to check how Subtitle works.

I'm going to capture a TV series tonight and see what I can come up with.

nicksteel 10-15-2003 10:06 AM

Boulder,

Do post your results. I do a lot of MPEG2 captures and would like to try doing interlaced.

Boulder 10-15-2003 10:14 AM

A _very_ quick test on a 720x576 VHS capture shows that the value is around 2.5 - 4.0 when there's little motion and 6.0 - 12.0 when there's motion (not intense but some).

How would I start tweaking the threshold?

*:lol: feeling like a total newbie :lol:*

kwag 10-15-2003 10:36 AM

Quote:

Originally Posted by Boulder
A _very_ quick test on a 720x576 VHS capture shows that the value is around 2.5 - 4.0 when there's little motion and 6.0 - 12.0 when there's motion (not intense but some).

How would I start tweaking the threshold?

*:lol: feeling like a total newbie :lol:*

For that resolution, I would use SwitchTreshold = 4. So only after 4, dynamic blurring starts to be applied.
Or you can expand the line: "SwitchThreshold = (Width<=352) ? 4 : (Width<=480) ? 3 : 2" to include more resolutions :idea: :D

-kwag

audioslave 10-15-2003 05:20 PM

@Boulder

How/where do you get the correct values for Crop and BicubicResize? I'm guessing you're using MovieStacker, but could you please explain where you find the values? :oops:

EDIT: Never mind the BicubicResize question, but I'm still having trouble with getting Crop to work...

Zyphon 10-15-2003 05:50 PM

Thanx 4 the script Boulder looks good. :)

audioslave 10-15-2003 06:22 PM

I simply put my Crop values from MovieStacker's Crop boxes in the script, like this: Crop(668, 428)
But I'm getting an 'invalid arguments to function "Crop"' error in Vdub.
How does this line have to look to be correct :?:

Boulder 10-16-2003 03:32 AM

Quote:

Originally Posted by audioslave
I simply put my Crop values from MovieStacker's Crop boxes in the script, like this: Crop(668, 428)
But I'm getting an 'invalid arguments to function "Crop"' error in Vdub.
How does this line have to look to be correct :?:

When everything else fails, read the docs :lol:

You'll have to state how many pixels you crop. I crop manually, using VirtualDub for help. I've never used any program to get the correct values as I trust my own eyes more.

So, the syntax is Crop(crop_width,crop_height,destination_width,dest ination_height).

Crop(10,24,700,528) would mean that you would crop 10 pixels off the left and right side and 24 pixels off the top and bottom of the clip. The source would be 720x576 in this case (720 - 10 - 10 = 700 and 576 - 24 - 24 = 528).

If you want to crop a different amount of pixels from the sides, you can use Crop(left,top,-right,-bottom).


From the Avisynth docs:

In order to preserve the data structure of the different colorspaces, the following mods should be used. You will not get an error message if they are not obeyed, but it may create strange artifacts.

In RGB:
width no restriction
height no restriction if video is progressive
height mod-2 if video is interlaced

In YUY2:
width mod-2
height no restriction if video is progressive
height mod-2 if video is interlaced

In YV12:
width mod-2
height mod-2 if video is progressive
height mod-4 if video is interlaced

Dialhot 10-16-2003 03:59 AM

Or you can use the avisynth plugin Autocrop that will give you this information visually, on the image.

nicksteel 10-16-2003 07:54 AM

Boulder.................
 
When you get your interlaced script tweaked, could you post it? I'm capturing with a PVR-250 at 720x480.

NickSteel

Boulder 10-16-2003 08:07 AM

Sure thing. I'm currently testing the script with the capture, checking some low-motion scenes and extremely high motion scenes and see how the MA script compares to a script I normally use.

Boulder 10-16-2003 09:29 AM

OK, here are some results:

With the MA script
Code:

nf=0
AVISource("path\clip.avi")
ConverttoYV12(interlaced=true)
SeparateFields()
UnDot()
BicubicResize(656,272,0,0.6)
MergeChroma(Blur(1.5))
MergeLuma(Blur(0.1)) # use only if the video won't get too blurry!
FluxSmooth(-1,7)

SwitchThreshold = (Width<=352) ? 4 : (Width<=480) ? 3 : 2
even=SelectEven().ScriptClip("nf=YDifferenceToNext()"+chr(13)+"nf>=SwitchThreshold?unfilter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))):TemporalSoften(fmin(round(2/nf),6),round(1/nf),round(3/nf),0,2)")
odd=SelectOdd().ScriptClip("nf=YDifferenceToNext()"+chr(13)+"nf>=SwitchThreshold?unfilter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))):TemporalSoften(fmin(round(2/nf),6),round(1/nf),round(3/nf),0,2)")
Weave()

AddBorders(24,16,24,16)
Limiter()
ConverttoYUY2(interlaced=true)

function fmin( int f1, int f2) {
  return ( f1<f2 ) ? f1 : f2
}

Low motion 55 755 504 bytes
High motion 32 993 620 bytes

With a static script
Code:

SeparateFields()
UnDot()
BicubicResize(656,272,0,0.6)
MergeChroma(Blur(1.5))
MergeLuma(Blur(0.1)) # use only if the video won't get too blurry!
FluxSmooth(-1,7)
even=SelectEven().TemporalCleaner(6,11)
odd=SelectOdd().TemporalCleaner(6,11)
Interleave(even,odd)
Weave()

AddBorders(24,16,24,16)
Limiter()

function fmin( int f1, int f2) {
  return ( f1<f2 ) ? f1 : f2
}

Low motion 55 206 840 bytes
High motion 35 406 512 bytes

Encoding is surprisingly slightly faster with the MA script. The result is a bit blurrier but I'm not sure if it's noticable when watched on a TV. The low motion scene was a bit larger with the MA script, but if I had used TemporalCleaner instead of TemporalSoften, I'm sure that the filesize would have been lower than with the static script.

I'm now encoding the whole clip and see how it looks.

nicksteel 10-24-2003 05:33 AM

Boulder,
 
Quote:

Originally Posted by Boulder
OK, here are some results:

With the MA script
Code:

nf=0
AVISource("path\clip.avi")
ConverttoYV12(interlaced=true)
SeparateFields()
UnDot()
BicubicResize(656,272,0,0.6)
MergeChroma(Blur(1.5))
MergeLuma(Blur(0.1)) # use only if the video won't get too blurry!
FluxSmooth(-1,7)

SwitchThreshold = (Width<=352) ? 4 : (Width<=480) ? 3 : 2
even=SelectEven().ScriptClip("nf=YDifferenceToNext()"+chr(13)+"nf>=SwitchThreshold?unfilter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))):TemporalSoften(fmin(round(2/nf),6),round(1/nf),round(3/nf),0,2)")
odd=SelectOdd().ScriptClip("nf=YDifferenceToNext()"+chr(13)+"nf>=SwitchThreshold?unfilter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))):TemporalSoften(fmin(round(2/nf),6),round(1/nf),round(3/nf),0,2)")
Weave()

AddBorders(24,16,24,16)
Limiter()
ConverttoYUY2(interlaced=true)

function fmin( int f1, int f2) {
  return ( f1<f2 ) ? f1 : f2
}

Low motion 55 755 504 bytes
High motion 32 993 620 bytes

With a static script
Code:

SeparateFields()
UnDot()
BicubicResize(656,272,0,0.6)
MergeChroma(Blur(1.5))
MergeLuma(Blur(0.1)) # use only if the video won't get too blurry!
FluxSmooth(-1,7)
even=SelectEven().TemporalCleaner(6,11)
odd=SelectOdd().TemporalCleaner(6,11)
Interleave(even,odd)
Weave()

AddBorders(24,16,24,16)
Limiter()

function fmin( int f1, int f2) {
  return ( f1<f2 ) ? f1 : f2
}

Low motion 55 206 840 bytes
High motion 35 406 512 bytes

Encoding is surprisingly slightly faster with the MA script. The result is a bit blurrier but I'm not sure if it's noticable when watched on a TV. The low motion scene was a bit larger with the MA script, but if I had used TemporalCleaner instead of TemporalSoften, I'm sure that the filesize would have been lower than with the static script.

I'm now encoding the whole clip and see how it looks.

I'm going to capture a marathon run of several Planet of the Apes films with my PVR250 as 720x480 MPEG2's. I would like trying to keep interlaced and encode as 704x480 or 352x480 MPEG2 with SKVCD.

I plan to use DVD2AVI to make d2v and create trim statements with VDUB. I will not create AVI files, but go MPEG2 to MPEG2.

Should I use the first script EXACTLY as listed above (with d2v instead of avi), or would you recommend something else?

J-Wo 10-24-2003 12:30 PM

ooooooohhhhhhhhhhh I am SOOOO confused about the cropping and resizing and addbording bit! I don't think I can handle the "use my eyes" idea because I just don't understand how to change the parameters correctly. If I use Boulder's bicubicresize paraemters and tweak it slightly to be for 704x480 (as opposed to 704x576), it looks like his addborder line is resizing the image too much (i.e. I can see some black bars on the sides).

Is there not an easy way to do this? I rely on Moviestacker so much!!! :oops: I also give AutoCrop a try, which found out that my source has some black bars on the sides. So it recommends a cropping of Crop(8,0,708,480). This just throws everything off for me, so now I have completely NO idea what to do for BiCubicResize or AddBorder. Hoping someone out there can help me!

J-Wo 10-24-2003 10:45 PM

Okay, just so I don't sound like a complete buffoon. I finally figured out how to use any resize values obtained from Moviestacker and make them work with Boulder's script. Whether you choose Overlap or Resize for "Blocks TV-Overscan", take whatever values for AddBorders() and/or Letterbox() and put them at the end of your script. Choose Bicubic precise as your resize method, but you'll have to make some modifications to the figures given. In my example, I have a 740x480 source that I'm encoding at 704x480. So according to Moviestacker, I get:
Code:

BicubicResize(704, 352, 0, 0.6, 0, 0, 720, 480)
AddBorders(0, 64, 0, 64)
LetterBox(0, 0, 16, 16)

But in Boulder's original script he mentioned BicubicResize(enter your values here, height/2!). So I halved 352 and got 176. I also noticed that Boulder doesn't include the last four values for resizing, so the final line becomes:
Code:

BicubicResize(704, 176, 0, 0.6)
AddBorders(0, 64, 0, 64)
LetterBox(0, 0, 16, 16)

In this example, I'm using overscan = 2. If I use resize = 2 then the lines become:
Code:

BicubicResize(672, 168, 0, 0.6)
AddBorders(16, 72, 16, 72)

I hope this explanation might be able to help others. I also found Boulder's script to do an amazing job on my NTSC interlaced dvd source, which was quite grainy/pixelated/noisy in certain scenes. Permutations of the MA script simply never got it right, and this one did the trick. It also lead to almost the same compression, but was way faster. Thanks a load Boulder!

nicksteel 10-25-2003 06:36 AM

When I use MovieStacker v2.0.0 (beta3) for a PVR250 capture of Futurama at 720x480 to produce a KSVCD at 480x480:

MPEG Resizing

Source 720x480 DVD Pal(Unchecked) Anamorphic(Unchecked) ITU=R BT.601-4(Checked)

Film pixel 720x480 0 left border 0 top border

Crop 720x480 accurate Use GripFit(crop/resize)(Unchecked)

Resize 336x446

Destination 480x480 SVCD Anamorphic(Checked) Format conversion(Unchecked)

Blocks TV-Overscan 2 Resize

AviSynth Script

Bicubic precise

LoadPlugin("C:\video\moviestacker\Filters\MPEG2Dec .dll")

Mpeg2Source("H:\fut16\fut16.d2v")
BicubicResize(336, 446, 0, 0.6, 0, 1, 720, 478)
AddBorders(72, 17, 72, 17)

If I half 446 to 223, will not run.

BicubicResize(336, 223, 0, 0.6)

What should BicubicResize line look like for this?

My capture is already YV12. Should I change script in any way?

J-Wo 10-25-2003 09:40 AM

Are you using AviSynth 2.5x? I think Boulder's script requires it.


All times are GMT -5. The time now is 12:28 AM  —  vBulletin Jelsoft Enterprises Ltd

Site design, images and content © 2002-2022 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2022 Jelsoft Enterprises Ltd.