KDVD: to Denoise or Not to Denoise (Split) - Page 2

Boulder · #21 09-09-2005, 03:08 PM

It shouldn't be like that as Avisynth always assumes "last" at the beginning.

That is: a,b,c,d and e are not connected to each other, they get the video as it is directly after xxxSource().

Dialhot · #22 09-09-2005, 03:44 PM

Quote:

Originally Posted by Boulder

It shouldn't be like that as Avisynth always assumes "last" at the beginning.

Exactly.

Quote:

That is: a,b,c,d and e are not connected to each other, they get the video is it is directly after xxxSource().

That is not like I understand this.
last is the result of the last command that produced a clip.
So last = b after the first line, then last = c, then last = d.
If you want to force each LremoveDust to affect a, you have to use "a" as first parameter.

But what I read in the doc seems to say you are right :

Quote:

variable_name = expression

In this example expression is evaluated and the result is assigned to variable_name.

Very important is the common shortcut form:

expression

In this case, expression is evaluated and the result is assigned to the special clip variable last.
This is the same as

last = expression

last is set only if no other variable is used. I discovered something.

Boulder · #23 09-09-2005, 04:05 PM

You'll see the behaviour already from the overlayed subtitle. If "a was last" for b etc., all the subtitles would be overlayed over each other.

It's also fast to check

Code:

a=LeakKernelDeint(order=1).Greyscale()
b=LeakKernelDeint(order=1)
Interleave(a,b)

and see what that does: every other frame is b/w, every other coloured.

Dialhot · #24 09-09-2005, 04:23 PM

Quote:

Originally Posted by Boulder

You'll see the behaviour already from the overlayed subtitle. If "a was last" for b etc., all the subtitles would be overlayed over each other.

You're right, I never thought about that

I always use :

Code:

video=xxxsource(...)
a=video.filter()
b=video.otherfilter()
interleave(a,b)

Boulder · #25 09-09-2005, 04:29 PM

Your version is just as right as mine, it just takes longer to type. Just like in programming, many ways to do the same thing

supermule · #26 09-09-2005, 09:04 PM

Quote:

Originally Posted by Boulder

The higher the limit, the closer the output gets to a regular RemoveGrain(mode=17), which is way too blurry for my taste.

What limit value (i.e. 4,5,6,7) makes it exactly like mode=17, if you are aware. Why I am asking is since I want to do a balance between Quality and size according to my preferences

.

EDIT: In the tests that I made I realised that increasing the limit from 1 to 4 does not bring considerable difference in the compressions but do bring in noticable difference in the Quality of the encode. Probably since I am already using limitU=255 so no more compression can be achieved.

Code:

return LimitChange(rg, input, limit, limitU=255)

I guess limit=1 or limit=2 are the ones that will work for most of us.

Boulder · #27 09-10-2005, 01:53 AM

Quote:

Originally Posted by supermule

Quote:

Originally Posted by Boulder

The higher the limit, the closer the output gets to a regular RemoveGrain(mode=17), which is way too blurry for my taste.

What limit value (i.e. 4,5,6,7) makes it exactly like mode=17, if you are aware. Why I am asking is since I want to do a balance between Quality and size according to my preferences

.

I don't know, and it's actually impossible to know as the process depends on the current frame.

Quote:

EDIT: In the tests that I made I realised that increasing the limit from 1 to 4 does not bring considerable difference in the compressions but do bring in noticable difference in the Quality of the encode. Probably since I am already using limitU=255 so no more compression can be achieved.

Code:

return LimitChange(rg, input, limit, limitU=255)

I guess limit=1 or limit=2 are the ones that will work for most of us.

You are using the limit for luma only, chroma smoothing is not limited, hence limitU=255. Chroma can be processed more aggressively before it comes noticable.

supermule · #28 09-17-2005, 10:41 AM

Quote:

Originally Posted by Boulder

Quote:

Originally Posted by nicksteel

So, I should

Mpeg2Source("C:\capture\capture.d2v",idct=7)

Telecide/Decimate

LRemoveDust_YV12(17,1)

Resize
ConverttoRGB24()
Addborders()

Yes.

Hi Boulder,

Do you think adding STmedian() filter would further help along with Lremovedust for non-DVD sources.

Whats ur opinion

incredible · #29 09-17-2005, 11:25 AM

We only can suggest if we know whats the kind of that source?
Its an avi? If yes what kind of AVI? A hollywoodmovie? If yes, a capture?

Boulder · #30 09-17-2005, 11:42 AM

Regardless of the source, I wouldn't add any filters in addition to LRemoveDust.

supermule · #31 09-17-2005, 12:51 PM

Quote:

Originally Posted by Boulder

Regardless of the source, I wouldn't add any filters in addition to LRemoveDust.

Does that mean that in your opinion Lremovedust handles pretty well, what STmedian is supposed to do for the source ????

Prodater64 · #32 09-17-2005, 01:31 PM

How would it be the script using gripcrop?

kwag · #33 09-17-2005, 02:01 PM

Quote:

Originally Posted by supermule

Do you think adding STmedian() filter would further help along with Lremovedust for non-DVD sources.

I hope when you mean "non-DVD sources" you are refering to captures, and not AVI (DivX/XviD) sources

-kwag

Boulder · #34 09-17-2005, 03:10 PM

Quote:

Originally Posted by Prodater64

How would it be the script using gripcrop?

Uhm, just place the three thingies, GripCrop, GripSize and GripBorders where they belong and remove all other items that crop, resize and add borders. SansGrip's functions are just different ways of doing the same thing.

supermule · #35 09-17-2005, 09:26 PM

Quote:

Originally Posted by kwag

Quote:

Originally Posted by supermule

Do you think adding STmedian() filter would further help along with Lremovedust for non-DVD sources.

I hope when you mean "non-DVD sources" you are refering to captures, and not AVI (DivX/XviD) sources

-kwag

Yes, how can I forget the forum rules!!!!!!

,

supermule · #36 09-17-2005, 09:32 PM

Quote:

Originally Posted by Boulder

Quote:

Originally Posted by Prodater64

How would it be the script using gripcrop?

Uhm, just place the three thingies, GripCrop, GripSize and GripBorders where they belong and remove all other items that crop, resize and add borders. SansGrip's functions are just different ways of doing the same thing.

Hi,

Can you post a sample script using the three, I cant find no help in the filter.

Boulder · #37 09-18-2005, 01:18 AM

GripCrop equals Crop, GripSize equals xxxResize, GripBorders equals AddBorders. The parameters have been explained a thousand times so I'm not going to do that now, the search will help you. The official GripFit thread started by SansGrip contains all the necessary information.

Prodater64 · #38 09-18-2005, 05:44 AM

Quote:

Originally Posted by Boulder

GripCrop equals Crop, GripSize equals xxxResize, GripBorders equals AddBorders. The parameters have been explained a thousand times so I'm not going to do that now, the search will help you. The official GripFit thread started by SansGrip contains all the necessary information.

I think he asked for filter position in the script.

Boulder · #39 09-18-2005, 05:48 AM

The positions are exactly the same as with normal cropping, resizing and adding borders, no reason for any other order. One crops, one resizes and one adds the borders, the only difference is that the calculations are done internally and the user doesn't need to figure the values out.

Prodater64 · #40 10-09-2005, 04:07 PM

When to use lremovedust_yv12(17,1) and when ...(17,2)?

Could somebody post a latest optimal script in that section please?
(Also Im wondering why Dialhot scripts are not in that section)