New Sharpening Function from Didée -'SeeSaw'

[TheRainmaker]

MeGui:
Progressive
DGindex:
Interlaced
AvSP:
I couldn't get info... :( something is wrong i thing)
How can you do in AvSP?


If you want to truly experience the crystal clarity principle, raise the slimit, or make it limitless

Are you sure...? :)
What is the limit of slimit paramater?
Or which one is able 60 or 70?
What is your prefer sets?

I wanna get acceptable rip from DVD... If i get better quality more than DVD source that is enough... :p

Thanks for your more tips... :)

[Terranigma]

MeGui:
Progressive
DGindex:
Interlaced
AvSP:
I couldn't get info... :( something is wrong i thing)
How can you do in AvSP?


If you want to truly experience the crystal clarity principle, raise the slimit, or make it limitless

Are you sure...? :)
What is the limit of slimit paramater?
Or which one is able 60 or 70?
What is your prefer sets?

I wanna get acceptable rip from DVD... If i get better quality more than DVD source that is enough... :p

Thanks for your more tips... :)
This's what I was telling someone the other day. That megui sometimes reports some sources as progressive when it's really interlaced. Always Trust Dgindex :)
In avsp.. Open your script, add info, then hit "f5". You might have to specify an external media player as well such as mpclassic.

Yes i'm sure.
I'm not sure about the limit, but I assume it's 100. (Perhaps Didée could clairfy)
Raise it to levels that satisfies you. You pick the limit. I keep it near 60-70 myself. :devil:

[TheRainmaker]

This's what I was telling someone the other day. That megui sometimes reports some sources as progressive when it's really interlaced. Always Trust Dgindex :)
In avsp.. Open your script, add info, then hit "f5". You might have to specify an external media player as well such as mpclassic.

Yes i'm sure.
I'm not sure about the limit, but I assume it's 100. (Perhaps Didée could clairfy)
Raise it to levels that satisfies you. You pick the limit. I keep it near 60-70 myself. :devil:
This one in GSpot:
http://img374.imageshack.us/img374/8053/gspotge0.th.jpg (http://img374.imageshack.us/my.php?image=gspotge0.jpg)
In AvsP with MPClassic:
http://img374.imageshack.us/img374/5582/adszrj4.th.jpg (http://img374.imageshack.us/my.php?image=adszrj4.jpg)
(I didn't see any info about progressive/interlaced)

I am gonna crazy... :confused:
Cause Dgindex says for all my dvd's: interlaced
i never saw progressive on there!
You checked output video...There is no problem i think but,do i have to add deinterlace plugin as like TomsMoComp?
Or what is suggestion for deinterlace?

[Terranigma]

I am gonna crazy... :confused:
Cause Dgindex says for all my dvd's: interlaced
i never saw progressive on there!

Dgindex is correct because it checks flags to determine if a source is interlaced or not.

From gspot, I/L is highlighted. That means it's interlaced. Just because a clip displays it's using the interlaced flag, doesn't mean it needs to be deinterlaced. If the frames looks like they're progressive, then leave them as is and encode as progressive.

And yea, you're right about info not displaying whether something is interlaced, excuse me there :/

[TheRainmaker]

Dgindex is correct because it checks flags to determine if a source is interlaced or not.

From gspot, I/L is highlighted. That means it's interlaced. Just because a clip displays it's using the interlaced flag, doesn't mean it needs to be deinterlaced. If the frames looks like they're progressive, then leave them as is and encode as progressive.

And yea, you're right about info not displaying whether something is interlaced, excuse me there :/

So i didn't see any problem in output video and i'll not add deinterlace filter too...:)
I never know that and good to know when i get preview in AvsP with info() end of the line:
CPU detected x87 MMX ISSE SSE SSE2 SSE3

That means my CPU is suitable for SSE3 so i can use RemoveGrainSSE3 instead of RemoveGrain... :)


I'll try more practice with my DVD with your suggestions...

Thanks a lot...

[foxyshadis]

Playing with sstr too much without balancing other parameters isn't a great idea; it can cause weird artifacts, with jarring transitions from smooth to crackling, or at least won't scale the way you expect from something named "strength". There's a reason it says "# Sharpening strength (don't touch this too much)".

The sdamplo parameter also strongly effects the amount of sharpening, and bias, slimit, and szp will all effect the nature of the output.

[TheRainmaker]

Playing with sstr too much without balancing other parameters isn't a great idea; it can cause weird artifacts, with jarring transitions from smooth to crackling, or at least won't scale the way you expect from something named "strength". There's a reason it says "# Sharpening strength (don't touch this too much)".

The sdamplo parameter also strongly effects the amount of sharpening, and bias, slimit, and szp will all effect the nature of the output.
Thanks for this good tip... :)

But when i leaved alone with default sets i got blurid output...
Please tell me which sets is touchable for sharpness?
Also 3.0 is not good idea for sstr parameter?

[Terranigma]

Thanks for this good tip... :)

But when i leaved alone with default sets i got blurid output...
Please tell me which sets is touchable for sharpness?
Also 3.0 is not good idea for sstr parameter?

foxyshadis's just warning us that setting the sharpening strength (sstr) too high will cause unexpected results. 3.0 with a super sampling factor of 1.25 is fine. But don't increase it much higher than that, or at all :)

[Seraphic-]

Is the version of SeeSaw.avs on page one the most up-to-date version or is there a newer version that is recommended? I'm thinking of giving this 'SeeSaw' sharpening tool a go as it seems to be designed to work well for what I need, which is re-sharpening a source that is somewhat blurred after a resizing for 16:9 wide-screen. However, I see most of the result images are from live-action sources. Will this work well for 3D Rendered Graphics?

The top image is with no sharping after resize and the below is with the internal sharping tool in VirtualDub at level 15 after resize.
Question: (How does the internal sharpener of VirtualDub compare to Avisynth based ones? The VirtualDub one seems to over-sharpen my sources when set to anything over 20.)
http://www.seraphicgate.com/1.png

[foxyshadis]

Didée's are designed specifically to avoid that halo around edges. Other generic sharpens (like the built-in one or the warpsharp unsharpmask) will give you the halo, since they're the same old thing and vdub and photoshop have.

LimitedSharpenFaster will halo if you push it too hard, but it sharpens much much more first. And SeeSaw never will in my experience; instead, it creates aliasing (like xsharpen), which tends to look better for cartoons and CG. But in normal use you won't ever see this.

Here's the seesaw scripts: http://forum.doom9.org/showthread.php?p=920642#post920642

Those are both the same image, btw. :p

[Seraphic-]

Didée's are designed specifically to avoid that halo around edges. Other generic sharpens (like the built-in one or the warpsharp unsharpmask) will give you the halo, since they're the same old thing and vdub and photoshop have.

LimitedSharpenFaster will halo if you push it too hard, but it sharpens much much more first. And SeeSaw never will in my experience; instead, it creates aliasing (like xsharpen), which tends to look better for cartoons and CG. But in normal use you won't ever see this.

Here's the seesaw scripts: http://forum.doom9.org/showthread.php?p=920642#post920642

Those are both the same image, btw. :p

Thanks for the link, if I get a chance later today I'll give it a try. But what you said about it adding some "aliasing" makes me wonder if it will make the image too jagged around the edges.

Oh, that is the same frame, but like I said, the top has no sharpening and the bottom has some from the internal sharpener of VirtualDub (compare the two images and their text). As you can see, I don't need much correction for my source, just to re-sharpen after the resize.

[Terranigma]

SeeSaw never will in my experience; instead, it creates aliasing (like xsharpen), which tends to look better for cartoons and CG.
Ahh, So you're saying that aliasing is a good thing for Animes/Mangas?
So that means I should keep the ssx ,ssy parameters at the default value since it doesn't avoid, but create aliasing? :p

[foxyshadis]

Not that it's good, just that it's less ugly than huge halos around every line. Raising ss does prevent aliasing, but also places an upper limit on the possible sharpening; since the resolution is finite, the only way to raise local contrast (sharpen) is to move adjacent pixels further from each other. Aliasing means they separate into immediate plateaus, haloing means they boost every transition regardless of what's beyond. There isn't really any other way of sharpening.

You can raise the resolution permanently (dest_x and dest_y) to achieve more sharpening without aliasing/ringing, but at the cost of more storage, of course.

[Didée]

Oh my ... two days not here, and things go like this.

I used that script but nothing has changed in output movie!
It same as before one
I think SeeSaw script and others not worked!

...

SeeSaw(ssx=1.25,NRlimit=0, NRlimit2=5, Sstr=2.0, Szp=1, Slimit=50, Sdamplo=6, Spower=0, bias=0, sootheT=0, SdampHi=52)

No surprise. Who was the jester telling you those totally fu**ed-up settings? They're so insanely screwed from sanity, it's hard to believe ...

Szp=1 : drives sharpening strength way beyond sanity.
Default is 16. Useful is 8 ~ 64.

Slimit=50 : no harm, but you really don't want pixels that are sharpened by that much ...

Spower=0 : Wohaaargh!! By this you turn SeeSaw into a borked joke! For some plugin writers, "power" eventually might be just a "cool" denomination. When I name it "power", then the meaning is "power" in the mathematical sense, i.e. (value)^(power).
Never ever set this to zero. (x^0 == 1, no matter what value x is. Unusable for processing...)

bias=0 : Oh well. That's a good way to exclude as much detail as possible from sharpening.


SeeSaw's default values surely are not "the best" for each&every source. But they are a *reasonable* starting point.

[Terranigma]

Oh my ... two days not here, and things go like this.



No surprise. Who was the jester telling you those totally fu**ed-up settings? They're so insanely screwed from sanity, it's hard to believe ...

Szp=1 : drives sharpening strength way beyond sanity.
Default is 16. Useful is 8 ~ 64.

Slimit=50 : no harm, but you really don't want pixels that are sharpened by that much ...

Spower=0 : Wohaaargh!! By this you turn SeeSaw into a borked joke! For some plugin writers, "power" eventually might be just a "cool" denomination. When I name it "power", then the meaning is "power" in the mathematical sense, i.e. (value)^(power).
Never ever set this to zero. (x^0 == 1, no matter what value x is. Unusable for processing...)

bias=0 : Oh well. That's a good way to exclude as much detail as possible from sharpening.


SeeSaw's default values surely are not "the best" for each&every source. But they are a *reasonable* starting point.

Didée I think he/she took a page from my book, which I took a page from Jeremy Duncan. The settings can be found
Here (http://forum.doom9.org/showthread.php?p=873467#post873467)

Could you give us some good initial settings to start with besides the default values? :p

[Pookie]

Terranigma - The first post in the thread (page 1) has a example setting that should demonstrate the SeeSaw effect without overdoing things. Of course, your source video will dictate the settings when you use SeeSaw. The before and after pic I posted on page 1 is that source using those particular settings. DegrainMedian was the denoiser.

I'm working on the Wiki doc for SeeSaw right now and I'll include some info Didée sent a while back about what the major parameters actually do.

[Terranigma]

Thanks Pookie, I'll be looking forward to that wiki :D
Edit: Pookie, I just tried your results on the first page and I like it much more than Jeremy Duncan's :)

[Pookie]

Jeremy focuses on realtime playback. Might look different on his equipment/eyes.

[Terranigma]

Yea i've noticed. Would be great to see an optimized .dll version of it.

[TheRainmaker]

DidéeCould you give us some good initial settings to start with besides the default values?
Yes! I really wonder that after reading of Didée's post, if someone says here best values of them...I know it depends to your source...
Slimit? Spower? Bias? etc...
I tried many rips and spent much more time to get real SeeSaw sharpening...
Many questions if compare to with SeeSaw avs:
SeeSaw(ssx=1.25(1.35)(?),NRlimit=0(2-3)(?), NRlimit2=5, Sstr=2.0(1.5)(?), Szp=1(16(8~64)(?), Slimit=50(5)(?), Sdamplo=6, Spower=0(4-5)(?), bias=0(49-50>)(?), sootheT=0(49)(?), SdampHi=52(24>)(?))

[foxyshadis]

Well, one option is to get avsp. Create a user slider set (sorry, too pressed for time to make one for you) with all the parameters, and then just tweak them however you like so you can see exactly what they do. I've come to understand more than one formerly mysterious filter that way.

[TheRainmaker]

Well, one option is to get avsp. Create a user slider set (sorry, too pressed for time to make one for you) with all the parameters, and then just tweak them however you like so you can see exactly what they do. I've come to understand more than one formerly mysterious filter that way.
Thanks for your reply...
Is AvsP giving realtime results for what looks like output without encoding?

[foxyshadis]

Yes, everytime you adjust a slider it refreshes the screen. (Not quite fast enough to refresh instantly, ala photoshop.)

[Jeremy Duncan]

Oh my ... two days not here, and things go like this.



No surprise. Who was the jester telling you those totally fu**ed-up settings? They're so insanely screwed from sanity, it's hard to believe ...

Szp=1 : drives sharpening strength way beyond sanity.
Default is 16. Useful is 8 ~ 64.

Slimit=50 : no harm, but you really don't want pixels that are sharpened by that much ...

Spower=0 : Wohaaargh!! By this you turn SeeSaw into a borked joke! For some plugin writers, "power" eventually might be just a "cool" denomination. When I name it "power", then the meaning is "power" in the mathematical sense, i.e. (value)^(power).
Never ever set this to zero. (x^0 == 1, no matter what value x is. Unusable for processing...)

bias=0 : Oh well. That's a good way to exclude as much detail as possible from sharpening.


SeeSaw's default values surely are not "the best" for each&every source. But they are a *reasonable* starting point.

Thanks for pointing those errors out, Didée.

I redid it. Have a look.

SeeSaw(NRlimit=0, NRlimit2=5, Sstr=1.70, Szp=1, Slimit=50, Sdamplo=29, Spower=1, sootheT=0, SdampHi=35)

Thanks for making Seesaw.

[Jeremy Duncan]

Here's some pictures I took comparing different Seesaw configurations, the New Limitedsharpenfaster config I made today, and one that just uses resizing with no filters.

I've included the FFDshow settings used for each picture.

Link is about 30 MB (http://rapidshare.com/files/22623284/Pictures.zip.html)

Thanks again for your time in making Seesaw, Didée.
Take the time to compare the work I've made using your lsf and seesaw code.

[salman1]

how to use seasaw filter and where could i dl it thx a lot and is that better than everything

[Boulder]

Did you happen to read this thread which actually discusses the usage?

[dvdfernandes]

LoadPlugin("C:\Program Files\GordianKnot\AviSynthPlugins\MaskTools-v1.5.8\MaskTools-v1.5.8\MaskTools.dll")
LoadPlugin("C:\Program Files\GordianKnot\AviSynthPlugins\mvtools-v1.6.2\mvtools.dll")
LoadPlugin("C:\Program Files\GordianKnot\AviSynthPlugins\masktools-v2.0a30\mt_masktools.dll")

LoadPlugin("C:\Program Files\GordianKnot\AviSynthPlugins\RemoveGrain\RemoveGrain.dll")
LoadPlugin("C:\Program Files\GordianKnot\AviSynthPlugins\RemoveGrain\Repair.dll")
LoadPlugin("C:\Program Files\GordianKnot\AviSynthPlugins\RemoveGrain\RemoveGrainSSE3.dll")


LoadPlugin("C:\Program Files\GordianKnot\AviSynthPlugins\degrainmedian\degrainmedian.dll")

Import("C:\Program Files\GordianKnot\AviSynthPlugins\SeeSaw\Seesaw.avs")

a= last
b=a.degrainmedian(mode=3)
SeeSaw(a,b, NRlimit=3, NRlimit2=4, Sstr=1.5, Slimit=5, Spower=5, Sdamplo=6, Szp=16)

It does not work... Am I missing somethig

The error that comes out is

"script error: Ther is no function named "mt_makediff"

I've been reading this thread for a while but can't seem to find the answer.

Thx in advance!

[Didée]

MaskTools v2 does not work with Avisynth v.2.5.5 - it "doesn't exist", even if imported. Needed is at least Avisynth v.2.5.6. It was mentioned even today, here (http://forum.doom9.org/showthread.php?t=123908).

[Pookie]

how to use seasaw filter and where could i dl it thx a lot and is that better than everything:goodpost:

[fight2win]

dude help me out with one thing, with seesaw and compressibility of even more than 140 percent, i get noise and artifacts, is there any way of fine tuning seesaw to get rid of those artifacts??? source is retail dvd9 and encoder is megui-xvid_encraw....

[Terranigma]

dude help me out with one thing, with seesaw and compressibility of even more than 140 percent, i get noise and artifacts, is there any way of fine tuning seesaw to get rid of those artifacts??? source is retail dvd9 and encoder is megui-xvid_encraw....
Have you tried using seesaw with soothe? It helps with the artifacts, set soothe to around 3%

e.g. using the above seesaw settings

dull= last
sharp = dull.SeeSaw(NRlimit=3, NRlimit2=4, Sstr=1.5, Slimit=5, Spower=5, Sdamplo=6, Szp=16)
Soothe(sharp, dull, 3)

[Didée]

@ Terranigma: that's a funny comment. SeeSaw does have Soothe integrated already, by the "SootheT" parameter (temporal soothing); in contrast to the standalone function, it even offers the possibility of "double soothing" by using negative values for SootheT.
Additionally, by "SootheS" it offers the the spatial soothe-down of sharpening known from LimitedSharpen(soft=x).
So no need to combine SeeSaw with Soothe. It's in the package from the start.


@ fight2win:
You have to balance out denoising and sharpening, and there's no general rule for how to achieve that. Basically, you need to use a denoiser that's capable of removing the artefacts that are present in the source. Then, you have to adjust SeeSaw's sharpening settings to needs - remember that SeeSaw performs sharpening on an intermediate clip which is somewhere inbetween "original" and "denoised" (percentual mix, controlled by "bias"). So, given that your denoiser is sufficient, you have to make bias just so big that artefacts creeping through can be sufficiently reduced by the later soothing, which you have to adjust, too.

[Terranigma]

Didée, Yes I know that. I was going to change SootheT to 0 (to speed up processing). Anyways, what would be the benefit of using double-soothe that's in seesaw over the Soothe Script (Using Soothe from the script seems to speed up things a lot) ?

[Didée]

Didée, Yes I know that. I was going to change SootheT to 0 (to speed up processing). Anyways, what would be the benefit of using double-soothe that's in seesaw over the Soothe Script (Using Soothe from the script seems to speed up things a lot) ?
The difference of "normal" soothing vs. "double" soothing is (kind of) similar to TemporalSoften(radius=1) vs. TemporalSoften(radius=2), with the target being the "effect-of-sharpening".


I was going to change SootheT to 0 (to speed up processing)
When in a couple of months I'm back into things, I'll try to finally do the MV-version of SeeSaw. After all, that's what it was planned to be from the very start.
In that case, many "speed questions" will get irrelevant ... in particular, questions about realtime-usage. :)

[3ngel]

@Didee
When in a couple of months I'm back into things, I'll try to finally do the MV-version of SeeSaw. After all, that's what it was planned to be from the very start.
Didee, can you try to stay in YUY2 colorspace? YV12 sometimes (as if you remember i already posted) gives gradients problems (and yes i remember you posted a trick to take the chroma from the unSeesawed clip but that's not the same :)).

[Didée]

Didee, can you try to stay in YUY2 colorspace? YV12 sometimes (as if you remember i already posted) gives gradients problems (and yes i remember you posted a trick to take the chroma from the unSeesawed clip but that's not the same :)).
Well ... usage of mt_LutXY is an elementary part in most of my scripts, and MaskTools do not support YU2 colorspace ...

But I don't see a problem in this case: the denoising you can do before SeeSaw, and during the sharpening stage, SeeSaw does not touch chroma at all. So there is no "loss of functionality" when merging in the desired chroma after SeeSaw.
Of course this kind of handling could be integrated directly, e.g. LimitedSharpen does it like that.

[3ngel]

Mmm, so you say SeeSaw doesn't touch chroma...
So the LutXY functions are related only to sharpening?
In this case i could modify (for my use) SeeSaw in order to remain in YUY2 until the sharpening stage, then to YV12?
Moreover i've read into another thread that the latest alpha version of AVS support (or it has to support?) YV16 (=YUY2) and Manao posted a 2.6 masktools.dll, at this point i've not uderstood if that AVS 2.6 actually support YV16 and the mt26.dll does support YV16 itself. Do you know something?

[Didée]

Mmm, so you say SeeSaw doesn't touch chroma...
So the LutXY functions are related only to sharpening?
[Looks into SeeSaw script] Ermmmh ... partly.
Sharpening only works on luma. For chroma, the difference (original-denoised) is taken, and limited by NRdiff, too. From this point of view, SeeSaw indeed *does* touch chroma.

Mind that SeeSaw was posted quite early, so it's still a bit inmature with its options. For ex., regarding chroma, there are at least the possibilities
- use original chroma
- use denoised chroma as-is
- use denoised chroma, plus limiting

but currently there's no knob to choose between them ... the last one is used, silently. ;)


Moreover i've read into another thread that the latest alpha version of AVS support (or it has to support?) YV16 (=YUY2) and Manao posted a 2.6 masktools.dll, at this point i've not uderstood if that AVS 2.6 actually support YV16 and the mt26.dll does support YV16 itself. Do you know something?
No, I missed that one. Fine if there is progress on the AS 2.6 front, but until it enters beta stage, it's not for me. No time to climb through bare brickwork, sorry.

[3ngel]

[Looks into SeeSaw script] Ermmmh ... partly.
Sharpening only works on luma. For chroma, the difference (original-denoised) is taken, and limited by NRdiff, too. From this point of view, SeeSaw indeed *does* touch chroma.

Eheh, ok. Then i'll live with it until (hopefully soon) AVS will support officially YV16 and hopefully Manao and you modify the script accordingly :)

[foxyshadis]

I had some sample code to do a YUY2->YV16 plugin (and YV24), but never finished it because I was more interested in 16-bit. The basic premise was packing it all into the luma plane and setting it to height*width*2 of the original (*3 for YV24). It wouldn't work for spatial processing, but I just thought of adding a 4- or 8-pixel buffer between them so that it wouldn't hurt. Since there's also no Y8, space for chroma planes is wasted, but... *shrug*

You could do the same thing (without padding) now with this:
StackVertical(Greyscale(),UToY(),VToY())
Then some trickery with crop to split it on the other side.

[Jeremy Duncan]

Didée,

No more realtime Seesaw ? The MV version will be turtle slow ?

I'm a optimist. So I'm not sure of what you meant about the realtime comment in post 435.

[JarrettH]

Didee :cool:

dull = ColorMatrix(Mode="Rec.601->Rec.709",scaling=2,threads=2)
sharp = dull.MT("SeeSaw(NRlimit=0, NRlimit2=5, Sstr=1.70, Szp=1, Slimit=50, Sdamplo=29, Spower=1, sootheT=0, SdampHi=35)",3)
Soothe(sharp, dull, 5)

So I can remove the Soothe line and changing to sootheT=5 would have the same effect?

[Boulder]

SeeSaw's Soothe is not the same as the standalone function. I think the difference has been explained in detail somewhere in this thread.

[JarrettH]

I did read back a bit and all I got was T=temporal S=spatial

[Didée]

dull = ColorMatrix(Mode="Rec.601->Rec.709",scaling=2,threads=2)
sharp = dull.MT("SeeSaw(NRlimit=0, NRlimit2=5, Sstr=1.70, Szp=1, Slimit=50, Sdamplo=29, Spower=1, sootheT=0, SdampHi=35)",3)
Soothe(sharp, dull, 5)

So I can remove the Soothe line and changing to sootheT=5 would have the same effect?
Well, yeah ... using SeeSaw with "external" soothing was a "carrying sand to the beach"-invention by Jeremy. :p ;)


In "standalone" Soothe, in a temporally mood I had decided to make the parameter "keep", i.e. how much of the original sharpening to keep at least. Hence, 0=maximum soothing (no minimum sharpening to keep), 100=minimum soothing (keep all sharpening).

When building SeeSaw, I found it's a bit unintuitive this way, and reversed the meaning to "strength-of-soothing". Hence, in SeeSaw, sootheT=0 means minimum soothing (do no soothing, keep all sharpening), sootheT=100 means maximum soothing (no minimum sharpening to keep).


So, to achieve the same effect, remove the Soothe line, and set sootheT=95. (95 = 100-5)

[Jeremy Duncan]

Good stuff.

Comparison pictures. Updated April 30, 2007 (http://rapidshare.com/files/28815879/Pictures.zip.html)

Basic resize used Lanczosresize in avisynth, and colormatrix.

________ Basic ________
I added the Queue output samples part
This version is using the newest FFdshow.

Codecs: All Supported
Blur & NR: denoise3d: Luma: 0.00, Chroma: 2.00, Time: 3.00, HQ Checked
Avisynth: YV12 checked, Add FFdshow Video source checked

ColorMatrix(Mode="Rec.601->Rec.709",scaling=2,threads=2)

Resize & aspect:
Multiply by 2.000
No aspect ratio correction checked
Lanczos
Taps: 2
Luma Sharpen: 0.90
Queue & Output: Queue output samples checked
Output: YV12 checked

________ LimitedSharpenFaster ________

Codecs: All supported
Blur & NR: denoise3d: Luma: 0.00, Chroma: 2.00, Time: 5.00, HQ Checked
Avisynth: YV12 checked, Add FFdshow Video source checked

SetMemoryMax(1024)
ColorMatrix(Mode="Rec.601->Rec.709",scaling=2,threads=2)
Lanczosresize(1680, 1050)
MT("LimitedSharpenFaster(ss_x=1.0, ss_y=1.0, Smode=3, strength=250, overshoot=1)",3)

Queue & Output: Queue output samples checked
Output: YV12 checked

________ SeeSaw Avisynth ________

Codecs: All supported
Avisynth: YV12 checked, Add FFdshow Video source checked

FluxSmoothT(3)
ColorMatrix(Mode="Rec.601->Rec.709",scaling=2,threads=2)
MT("SeeSaw(NRlimit=0, NRlimit2=5, Sstr=2.40, Szp=1, Slimit=50, Sdamplo=16, Spower=1, sootheT=95, SdampHi=39)",3)
lanczosresize(1280, 800)

Queue & Output: Queue output samples checked
Output: YV12 checked

[sujit]

Yes, that's about the same as mine. Just PM me if you need more help.


Spline36Resize(1440,608) # Blow up the image so denoising will look more natural.

fft3dfilter(sigma=5,plane=0)
fft3dfilter(sigma=6,plane=3)

a = last
b=a.degrainmedian(mode=1).cnr2()
SeeSaw(a,b, NRlimit=6, NRlimit2=7, Sstr=1.5, Slimit=6, Spower=8, Sdamp=5, Szp=16)

Spline36Resize(720,304) #Reduce Size back to NTSC DVD spec
addborders(0,88,0,88)


This is something new to me (upsize and then denoise). So, in general, is it a good idea to upsize before denoise?

Thanks:)

[Porsche_fan]

Well I have been through this thread twice and the only thing I know for sure is that Didée is as funny to read as he is smart.:) That and the advantages of SeeSaw is easily nullified if you play with the parameters too much.


Actually, I think I have a basic understanding of how SeeSaw works. I really like the default settings for the most part, although there are times when I’d like to tweak it a bit. I thought it best to start varying slightly from these defaults, however, I am still new at reading scripts and I am not really sure if I understood correctly what are SeeSaw’s default settings.


I went through and tried to pull them out but I noticed for example that Didée indicates, in this thread, that the default setting for Szp is 16…yet the way I read it I got 18 (16+2). Could someone either help me with the defaults or explain how to read them. Here is my interpretation of the default settings. SeeSaw(ssx=1.0,ssy=1.0,NRlimit=2,NRlimit2=3,Sstr=1.5,Slimit=4,Spower=4,Szp=18,SdampLo=5,SdampHi=24,bias=49,Smode=11,sootheT=49,sootheS=0)


Thanks

[hannah]

First of all thanks to Didée for this script. I am applying to the badminton games I filmed in my Panasonic NV GS 180 mini DV camcorder. I had been successful in applying the seesaw script on these videos and had very good outcome. I have read this whole thread probably 3 times now however having difficulties finding a post explaining all the parameters in seesaw. Understand that this script is still in development however an explanation of all the parameters will be really helpful. Can someone please direct me to the post if it is already explained somewhere?

Cheers