Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Usage

Reply
 
Thread Tools Search this Thread Display Modes
Old 10th July 2009, 16:10   #1  |  Link
nitinpushpan
Registered User
 
Join Date: Jul 2009
Posts: 27
Order of filters in AviSynth.

Is there any specific order for using the filters in Avisynth? I'm not sure whether to use UnDot() filter before or after the spatial temporal smoothers like FluxSmoothST() and Deblock() filter? Please suggest a good ordering for the filters. Also somebody please suggest a better filter that performs the same operation than Undot()?

Last edited by nitinpushpan; 10th July 2009 at 16:47.
nitinpushpan is offline   Reply With Quote
Old 10th July 2009, 17:13   #2  |  Link
Adub
Fighting spam with a fish
 
Adub's Avatar
 
Join Date: Sep 2005
Posts: 2,699
Sure order matters, but it depends on what you want to do with your source. Remember (usually) each filter will filter the output of the line before it.

For example:
Quote:
#Filter 1
#Filter 2
#Filter 3
Filter 1 filters the video first. Filter 2 filters the results produced from Filter 1.
Filter 3 filters the results from Filter 2, which are produced from the output of Filter 1, etc...

For an alternative to undot(), many people use RemoveGrain(2).
__________________
FAQs:Bond's AVC/H.264 FAQ
Site:Adubvideo
Adub is offline   Reply With Quote
Old 10th July 2009, 17:33   #3  |  Link
nitinpushpan
Registered User
 
Join Date: Jul 2009
Posts: 27
So what do you suggest? Should I use it before or after FluxSmoothST()?
nitinpushpan is offline   Reply With Quote
Old 10th July 2009, 20:46   #4  |  Link
Adub
Fighting spam with a fish
 
Adub's Avatar
 
Join Date: Sep 2005
Posts: 2,699
The rule of thumb is always: "Do what looks good to you."

But if you want my professional opinion, UnDot() is usually just used to smooth out the irregular "hot" pixels, so I would usually put it first, or at least high up on the filter list.

The reason is that it doesn't destroy a whole lot of detail, and can it's output can allow for better motion compensation down the line.
__________________
FAQs:Bond's AVC/H.264 FAQ
Site:Adubvideo
Adub is offline   Reply With Quote
Old 10th July 2009, 21:25   #5  |  Link
BigDid
Actually in reserve
 
Join Date: Oct 2004
Posts: 1,605
Quote:
Originally Posted by Adub View Post
...
For an alternative to undot(), many people use RemoveGrain(2).
Hi,

Hmmm, is'nt mode1 the equivalent to undot (but quicker)...?
http://forum.doom9.org/showthread.php?t=106413
http://videoprocessing.11.forumer.co...423cc6a950#148

As for mode2 I find it already more destructive than mode5 but, it is my opinion only...

Did
__________________
Having a problem with AutoGK? Read & use the FAQ & MORE FAQ first
Want to exchange on AutoGK? try doom10.org
In reserve (inactive) for an undefined period of time.

Last edited by BigDid; 10th July 2009 at 21:27.
BigDid is offline   Reply With Quote
Old 10th July 2009, 21:44   #6  |  Link
Adub
Fighting spam with a fish
 
Adub's Avatar
 
Join Date: Sep 2005
Posts: 2,699
It appears you are correct, however, I have always seen people use RemoveGrain(2), and never mode 1. I'm not saying that it's bad to do so, just that it seems to be the general practice to use mode 2.
__________________
FAQs:Bond's AVC/H.264 FAQ
Site:Adubvideo
Adub is offline   Reply With Quote
Old 11th July 2009, 07:19   #7  |  Link
nitinpushpan
Registered User
 
Join Date: Jul 2009
Posts: 27
Thanks guys for the useful advice...
nitinpushpan is offline   Reply With Quote
Old 11th July 2009, 07:40   #8  |  Link
m3mbran3
Registered User
 
Join Date: Jun 2009
Posts: 90
Generally I would do something like

deinterlace
crop
resize
degrain
sharpen

Of course it is all user preference but as some filters don't work well with interlaced content you should deinterlace first (if needed). I also find that sharpening after degraining provides better results too.
m3mbran3 is offline   Reply With Quote
Old 12th July 2009, 02:08   #9  |  Link
10L23r
Registered User
 
Join Date: Apr 2009
Posts: 122
I would do deblock, undot/removegrain, fluxsmooth.

It's mostly "common sense" and experience. Generally, you will want to let each filter have the best input possible. For example, you will not want to resize and then deinterlace/ivtc because the fields will be destroyed.

Here are some general tips:

Don't crop or resize before deblocking. cropping or resizing will shift or blur the boundaries of the blocks, making deblocking less effective.

Cropping/resizing: use "crop(l,t,w,h).xxxresize(x,y)" to remove black borders. use "xxxresize(x,y,l,t,w,h)" if you want to extract a specific part of an image.
Look here: http://avisynth.org/mediawiki/Resize...al_information for more information

Sharpening (usually) amplifies noise, so putting it before a denoiser is (usually) not a great idea.
10L23r is offline   Reply With Quote
Old 16th July 2009, 23:21   #10  |  Link
n0an
Britain's Finest!
 
n0an's Avatar
 
Join Date: Jun 2009
Posts: 143
Quote:
Originally Posted by m3mbran3 View Post
Generally I would do something like

deinterlace
crop
resize
degrain
sharpen

Of course it is all user preference but as some filters don't work well with interlaced content you should deinterlace first (if needed). I also find that sharpening after degraining provides better results too.
Doesn't sharpening in the end produce some noise? I usually use sharpening just after FFT3D(denoising) or degraining and then use a light smoothener or a denoiser to remove the artifacts of sharpening. Does anyone have any better ways?
n0an is offline   Reply With Quote
Reply

Tags
filters, order of filters, undot

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 21:59.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.