Pre-Created AVS Scripts

[eadsja]

I thought we could create a thread where we keep out AVS Scripts that we have used to garnish good results when prossessing our footage to our oh so lovely visual level's of excellence.

Suggested Format-


-SOURCE-
AMV Title
Box version: [ntsc-pal-film]
Aspect Ratio: [16:9 - 4:3}
(Other source comments go here)

-RESULT-
Final Resolution: [888X888]
DAR or PAR of final resolution - 1:1 PAR or 16:9 True Aspect Ratio...
FPS Output - 888FPS
Edditor: What you geared the AVS to be used for (Premier, WMM2 etc)
Remarks: Brief Description of the good points to this particular script.

---------Script------------

And this is where you cut and paste your avsynth script here with the exception of

["source"], ipp4, rgp true)

For the first line in order to allow people to have hard drive privacy.

----------END-------------

I think that this would be an awesome resource. We would just have to make certain that one of the rules to this thread is that we are not allowed to go off on tangents. As soon as I get the kinks out of my Lodoss AVS script I will post it and get this thing rolling (if no one else jumps in).

Please post only working scripts. If there is a known detail flaw in the script (but you belive it to be a workable flaw) make note of it, as someone who had da UBER skills may be able to modify it.

[Qyot27]

There already is a resource for this at AMVWiki.org.

[Scintilla]

Specifically, you might want to take a look at <a href="http://www.amvwiki.org/index.php/Record ... ">Kalium's suggestion for Record of Lodoss War</a>.

[eadsja]

Script wise, it's a lot simpler, and it doesn't adress some of the points I am trying to hit. Macroblocking is worse than the script I am working on, and the temporal clean - well, there is none.... Or if the Deen is set up to temporal cleaner - I ain't seeing the results. It's not the quality I am looking for. Right now I am trying to solve that annoying Crawling background colors without smoothing things so much that I loose details...

Must - be - anal - retentive...

I'm only going to allow myself one more shot to do this project justice...

[eadsja]

This is sooooo close. I've managed to hold onto detail and get this thing 70% smoothed propperly. I had to use two smoothers and the temporal smoothers are causing more problems than fixing them. I've still got 'odd' color graduations when I get near the edges of the characters (but it is not bluring any of my edges).

The deen is taking the macroblocking down significantly, but I was wondering if there were any suggestions on how I can bring it down the rest of the way.

That and I still have what looks like blended footage... But I think that 'jumpy' ghost video is actually from my processor having a f*** heart attack, I did not notice the ghost images when the screen was playing at full frames, and they are all relatively minor (echos, rather than full blown ghosts.) But then again, I could be wrong.

Any suggestions? Have I built this thing completely wrong?



mpeg2source("[lodoss oav source",ipp=true,cpu=6)
ConvertToYV12(interlaced=true)
KernelDeint(order=1,threshold=0)
mftoon(strength=150)
VagueDenoiser(threshold=0,method=1,nsteps=6,chromaT=0,interlaced=false)
deen("a2d",2,4,4)
tweak(sat=1.2)
Crop(8,4,-12,-0)
LanczosResize(640,480)
AssumeFPS(29.97)
#ConvertToRGB32(interlaced=false)

[Scintilla]

That and I still have what looks like blended footage... But I think that 'jumpy' ghost video is actually from my processor having a f*** heart attack, I did not notice the ghost images when the screen was playing at full frames, and they are all relatively minor (echos, rather than full blown ghosts.) But then again, I could be wrong.

Best way to check that is probably to view it in VirtualDub(/Mod) and scan through the frames looking for the ghosts. If they don't show up there, you're good.

ConvertToYV12(interlaced=true)

Unnecessary -- the MPEG-2 stream is already in YV12.

KernelDeint(order=1,threshold=0)
mftoon(strength=150)
VagueDenoiser(threshold=0,method=1,nsteps=6,chromaT=0,interlaced=false)
deen("a2d",2,4,4)

You might want to consider putting mftoon after the smoothers. Vague and Deen are pretty good about respecting edges.

And "threshold=0"? I suggest 2 or greater for an old source -- 0 would do almost nothing, wouldn't it?

AssumeFPS(29.97)

Unnecessary -- the MPEG-2 stream is already at 29.97fps.

Anyway, if it's macroblocking you're looking to whack, I suggest taking a look at this filter: <a href="http://www.funknmary.de/bergdichter/pro ... SmoothD</a>
(Unfortunately it's not listed on http://www.avisynth.org/warpenterprises yet, but everything you need should be on the project page.)

I was pleasantly surprised at how effective it was at removing block/mosquito noise and increasing compressibility on my latest video; and like VagueDenoiser (and unlike Deen), it avoids washing out the footage.

[trythil]

Script wise, it's a lot simpler, and it doesn't adress some of the points I am trying to hit. Macroblocking is worse than the script I am working on, and the temporal clean - well, there is none.... Or if the Deen is set up to temporal cleaner - I ain't seeing the results. It's not the quality I am looking for. Right now I am trying to solve that annoying Crawling background colors without smoothing things so much that I loose details...

Must - be - anal - retentive...

I'm only going to allow myself one more shot to do this project justice...

If you ever get it into a state you can accept, be sure to append it to the Record of Lodoss War article on amvwiki.

[eadsja]

After talking it over with Kalium for a little bit... And scrounging the video for a while longer, I've got this script here...


***********
mpeg2source(........LodossA.d2v",ipp=true,cpu=4)
KernelDeint(order=1,threshold=0,sharp=true,twoway=true,linked=true)
Unblend()
Decimate(4).Decimate(3)
Crop(8,4,-12,-0)

VagueDenoiser(threshold=4,method=0,nsteps=6,chromaT=0,interlaced=false,wavelet=2)

deen("w3d",4,5,9)
mftoon()
LanczosResize(640,480)

******************

Of course I still need to add the RGB conversion at the end of the script. I noticed that when I used the unblend\decimate function I found in the guide my ghost images were significantly reduced. With that decimate function, I am not de-interlacing twice am I? Am I F**-ing up my frame rates from the original 30?

The watered down deen really seems to work well with vauge de-noiser and creates some clean - crisp images. And I don't think I am trying to overmuscle it like I was with my earlier script. I realize that the filters are all slow, but I am using bait and switch. So I can afford to be patient...

With the bait and switch in mind... Do I need to keep the decimate with the deinterlace to make certain I am grabbing the same frames when I switch avs files?

Also, this is a bit of a stranger question... But I am colorblind (shades) - Does Lodoss really need color tweaking? I can't tell the difference between tweak 1.2 and normal... but I can see the difference between 1.5 and normal... It just feels like color distinction is more washed the more you tweak it. Any suggestions for some simple image adjustments either for contrast and the what not for this amv? My eyes are useless when It comes to subtle changes...

[trythil]

With the bait and switch in mind... Do I need to keep the decimate with the deinterlace to make certain I am grabbing the same frames when I switch avs files?

Yes. If the frame rate and frame content isn't (roughly) the same between AVISynth script and temporary file then the switch method is useless.

Also, this is a bit of a stranger question... But I am colorblind (shades) - Does Lodoss really need color tweaking? I can't tell the difference between tweak 1.2 and normal... but I can see the difference between 1.5 and normal... It just feels like color distinction is more washed the more you tweak it. Any suggestions for some simple image adjustments either for contrast and the what not for this amv? My eyes are useless when It comes to subtle changes...

A good way to tweak brightness/contrast/saturation/etc is to find some objective color standard (i.e. not your own eyes) and tweak your source until it is in line with that standard.

One way that works to tweak brightness is to find a white point -- if you're not overly concerned with range clamping, a pure white square in RGB space works -- and then find a spot in the anime that is supposed to also be pure white. Then take a frame grab, run a color-picker tool over it, and determine how far off it is. Calculate the difference and Tweak only enough to make those points the same.

This is obviously very crude, but I hope it makes the point.

There exist other objective methods of matching color -- probably the most popular in the film world is GretagMacbeth's ColorChecker -- but those assume that you're going for color calibration of EVERY tool in your pipeline, and I'm not really sure if something like the ColorChecker is really appropriate for postproduction correction anyway.

[eadsja]

Okay, Thanks for the response, and I will try your objective color manipulation, but I have two questions?

What is range clamping (or - why should I 'not really worried about...")

And two, how do I do the color and contrast calculations using Tweak? How do I understand how to move the RGB numbers from my white source to match the numbers for a proper RGB pure white?

Is there an explination guide on how to do this allready?