Quantcast Mencoder: Filters, Crop, Resize? - digitalFAQ.com Forums [Archives]
  #1  
05-02-2004, 11:15 AM
Prodater64 Prodater64 is offline
Free Member
 
Join Date: Mar 2003
Location: Palma de Mallorca - España
Posts: 2,925
Thanks: 0
Thanked 0 Times in 0 Posts
Quote:
Originally Posted by Incredible
EVEN if autocrop works great in mencoder, you stll have to implementate a automatic calculation routine like in Moviestacker to receive perfect crop/resize/expand parameters for macroblock based images and for shure on individual sized Avi inputs MEGA Work !
So its very easy to use moviestacker and get the needed crop/resize values wich can be easely used in mencoder by Cropxx:yyy:y and scale xxx:yyy -- adding borders will then be done by Expandxx:yyy
Must we to set resize functions in avs and in mencodeme too, or it is enough set it only in mencodeme?
What about filters that are better placed after crop/resize, and viceversa?
Can "expand" be placed at the end of mencoder command line?
Reply With Quote
Someday, 12:01 PM
admin's Avatar
Site Staff / Ad Manager
 
Join Date: Dec 2002
Posts: 42
Thanks: ∞
Thanked 42 Times in 42 Posts
  #2  
05-02-2004, 01:08 PM
digitall.doc digitall.doc is offline
Free Member
 
Join Date: Jul 2003
Location: Valencia (España)
Posts: 741
Thanks: 0
Thanked 0 Times in 0 Posts
Prodater,
if you crop/resize within avs script, you don't need to do it again in mencoder. If you take a look at makeAVIS template in mencodeme, it has no crop/scale parameter (if I remember well). You would be doing it twice.
About your two last questions, here I post a filter chain I posted in loooong mencoder sticky:
Code:
-vf yuvcsp,crop=688:560:18:2,scale=336:272:0:0:60,il=d,unsharp=l3x3:0.6,hqdn3d=3:6:8, 
unsharp=l3x3:-0.7:c3x3:-1.5,noise=2uh,il=i,expand=352:288:-1:-1,hue=0.0:0.5
As you see filters are set after crop/scale (as in vmesquita templates). From our experience with avisynth and MA script, some filters do better before resizing (in MA unsharp mask, and undot-> spatial, are before resizing). And if I remember well, temporal filters are better placed before resizing (some help here please). But with mencoder we have a lot to learn yet. By now, they're placed after resizing...
But if your source is interlaced, you'd better deinterlace before filtering, and then reinterlace, as in the code I post.
Related to expand ("AddBorders"), it comes at the end of filter chain, but in the -vf filter chain. Not at the end of mencoder command-line.

Congratulations: I see you're helping people a lot in spanish forum. I hope that will make it as interesting as it used to be.
Reply With Quote
  #3  
05-02-2004, 01:37 PM
Prodater64 Prodater64 is offline
Free Member
 
Join Date: Mar 2003
Location: Palma de Mallorca - España
Posts: 2,925
Thanks: 0
Thanked 0 Times in 0 Posts
Quote:
Originally Posted by digitall.doc
Congratulations: I see you're helping people a lot in spanish forum. I hope that will make it as interesting as it used to be.
Thanks for that digitall.doc.
And thank you a lot for your very good previous explanation.
Reply With Quote
  #4  
05-02-2004, 03:33 PM
incredible incredible is offline
Free Member
 
Join Date: May 2003
Location: Germany
Posts: 3,189
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via ICQ to incredible
(EDIT1: Updated to also Deinterlace/IVTC filter howto)
(EDIT2: a PERFECT link to a page where mencoder filters are already testet!!!!)

Here it goes:

As told very good above by Digitall.doc its very easy to make a "personal" template for mencoderME or also for manual batches by just a .bat.
(Digi.doc, I just add some things that others can see the thing a bit more "splitted" )

The approach of mencoder and avisynth in its filter performing and how they have to follow to each of them is the same as known from avisynth.

Why?

Because .... no matter if mencoder or avisynth .. both do get a source to handle and both do got filters with the same sense (noise, tempo/spat-filters, croppers, resizers and so on.

so lets take a deep look in the mentioned line above
Quote:
-vf yuvcsp,crop=688:560:18:2,scale=336:272:0:0:60,il=d ,unsharp=l3x3:0.6,hqdn3d=3:6:8,
unsharp=l3x3:-0.7:c3x3:-1.5,noise=2uh,il=i,expand=352:288:-1:-1,hue=0.0:0.5
Lets do list these filters in a logic as if we do have a simple avisynth syntax:


1 yuvcsp - clips the luma range to CCIR 601 specs. in avisynth called Limiter()

2 kerndeint=15:0:1 - (added here for explan.) do you got an interlaced source? So apply the deinterlacer here!

3 pp=hb:100:100/vb/dr - (added here for explan.) a postprocessing on the source like BlindPP(CPU=6) cause it also derings!

4 crop=688:560:18:2 - it speaks for itself and gots the same logic/syntax as avisynths crop() function

5 scale=336:272:0:0:60 lets scale to 336x272 where afterwards borders around will be added as here the width is not full 352 that means here the overscan area is cropped!

6 hqdn3d=10:0:5 - now we do the Spatio/temporal filtering ... this hqdn3d is like a 3d filter (deen("c3d") i.E.) where 10=y spatial, 0=c spatial and 5= Temporal filtering of the source. You also can set this filter before the scaler and do your own tests how it will result better.

7 unsharp=13x3:0.6 - Do you know unfilter() and its sharpen/soften?? Well

8 noise=2uh - Put some Noise like Blockbuster

9 expand=352:288 .. and finally we do add the borders.
(Above there's a hue=xxx applied after expand=xxx which is (IMHO) not right as we should do all our image processing BEFORE adding the borders

And here for all "freaky" testers a summary of mencoders pp=xxx (Postprocessing) options:



PS Also do have a look at "our best friend" the manual of mencoder/encoding:
http://www.mplayerhq.hu/DOCS/man/en/...RING%20OPTIONS

Added1: Here you find an explanation of how to find out in which state your source is (interlaced/telecined/progressive) .... and howto filter(deinterlace or IVTC) and afterwards encode them correctly:
http://www.mplayerhq.hu/DOCS/HTML/en...-telecine.html

Added2: Look at this site where many mencoder filters are already tested, incl. Pics - a we do like that
http://www.wieser-web.de/MPlayer/
Reply With Quote
  #5  
05-02-2004, 04:02 PM
Prodater64 Prodater64 is offline
Free Member
 
Join Date: Mar 2003
Location: Palma de Mallorca - España
Posts: 2,925
Thanks: 0
Thanked 0 Times in 0 Posts
Super.
Thank you.

Reply With Quote
  #6  
05-02-2004, 04:06 PM
digitall.doc digitall.doc is offline
Free Member
 
Join Date: Jul 2003
Location: Valencia (España)
Posts: 741
Thanks: 0
Thanked 0 Times in 0 Posts
Better explained, this way. Thank you Inc.
I've been thinking to start a thread called something like "avisynth translated into -vf mencoder", and I'll do when I have more to say , but I see you (and sure many others) will be very helpful with this matter.
Quote:
Originally Posted by incredible
3 pp=hb:100:100/vb/dr - (added here for explan.) a postprocessing on the source like BlindPP(CPU=6) cause it also derings!
A doubt here: what are the min/max (0/255?) values for hb and vb?, why just higher values for horizontal?, are negative values accepted, and what's it meaning?. How do we translate this figures in avisynth ones (or opposite)? (you see, newb questions )
Quote:
9 expand=352:288 .. and finally we do add the borders.
(Above there's a hue=xxx applied after expand=xxx which is (IMHO) not right as we should do all our image processing BEFORE adding the borders
He, he, of course, your right. Better expand in the end (as I told Prodater). It was a mistake.

BTW: is there any change in internal mencoder filters (added new filters, new parameters, or whatever)?. Man_page looks the same related to this question.
Reply With Quote
  #7  
05-02-2004, 04:13 PM
incredible incredible is offline
Free Member
 
Join Date: May 2003
Location: Germany
Posts: 3,189
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via ICQ to incredible
As I saw at mplayerHQ/and here, ... ivtc is fixed if I understood that right.
Also KernDeint known as Kerneldeint from avisynth was ported, BUT all these deinterlacers do not work smart! ok they do work blending or interpolating ... but maybe Im wrong and have to have a closer look.

According to PP.

Well as also BlindPP(CPU=6) gots more detailed options like BlindPP("xxoxo",.....) etc., ... so you should have also a look at the mpeg2dec3.ll readme document to see the logic as in here are also thresholds/strengths possible.

Sorry for not detailered explanations, but Im soooooo tired as I got a full PureBasic Weekend behind me ...

PS: I also had the Problem like VMesquita to get the latest CVS snapshot compiled for Athlon .... I hope they do fix that!

@ Prodater or Vmesquita

We should rename this Thread to "Filters, Crop, resize etc. using Mencoder" ... so others will find everything they need by just looking in the mencoder forum and watching the Title of this thread ... as this here could become a nice "figuing out" & "explanation" thread for mencoders internal filters
Reply With Quote
  #8  
05-03-2004, 10:44 AM
digitall.doc digitall.doc is offline
Free Member
 
Join Date: Jul 2003
Location: Valencia (España)
Posts: 741
Thanks: 0
Thanked 0 Times in 0 Posts
Quote:
Originally Posted by incredible
@ Prodater or Vmesquita

We should rename this Thread to "Filters, Crop, resize etc. using Mencoder" ... so others will find everything they need by just looking in the mencoder forum and watching the Title of this thread ... as this here could become a nice "figuing out" & "explanation" thread for mencoders internal filters
Great Inc, this would be even better than opening a new thread as I said before.
So let's begin:

il
This filter manages interleaved sources. If you want to keep them interlaced, instead of using kerneldeint to deinterlace, you can separate fields, apply filters and then interlace back again.
il=d it separates the fields (like ViewFields filter in avisynth, I think)
il=i it interlaces again the fields (like UnViewFields) for an interlaced output

... corrections please
Reply With Quote
  #9  
05-03-2004, 10:47 AM
incredible incredible is offline
Free Member
 
Join Date: May 2003
Location: Germany
Posts: 3,189
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via ICQ to incredible
Im at work, so ... im really not at the end of my "find all filters in mencoder" mania!

But this would be even better than in avisynth "separatefields() and Weave()" performed !!!!!
Ill give it a try!
Reply With Quote
  #10  
05-03-2004, 10:53 AM
digitall.doc digitall.doc is offline
Free Member
 
Join Date: Jul 2003
Location: Valencia (España)
Posts: 741
Thanks: 0
Thanked 0 Times in 0 Posts
I think that they work different, it seams to me that separatefields doubles framerate (each field is converted in a frame), while "il" stacks vertical both fields in a frame (but I didn't really test it deinterlacing and not interlacing back)
You could propose a way to post filters in mencoder and the comparison to avisynth.
Reply With Quote
  #11  
05-03-2004, 11:05 AM
incredible incredible is offline
Free Member
 
Join Date: May 2003
Location: Germany
Posts: 3,189
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via ICQ to incredible
Quote:
Originally Posted by digitall.doc
I think that they work different, it seams to me that separatefields doubles framerate (each field is converted in a frame)....
Nope!!!
Separate fields just un-weaves the frames and thats why you get 50fields per second!
What you mean is Bob()
Quote:
, while "il" stacks vertical both fields in a frame (but I didn't really test it deinterlacing and not interlacing back)
That would be the best approach!
Quote:
You could propose a way to post filters in mencoder and the comparison to avisynth.
Man, despacio!
Only 2 Hands and even more worse : 24h a day only!!
Reply With Quote
  #12  
05-03-2004, 03:48 PM
digitall.doc digitall.doc is offline
Free Member
 
Join Date: Jul 2003
Location: Valencia (España)
Posts: 741
Thanks: 0
Thanked 0 Times in 0 Posts

By you I was using plural: you all participants in this forum...

Just two hands?, sure?, sometimes it looks like you were not just one but several...
Reply With Quote
  #13  
05-04-2004, 04:52 AM
digitall.doc digitall.doc is offline
Free Member
 
Join Date: Jul 2003
Location: Valencia (España)
Posts: 741
Thanks: 0
Thanked 0 Times in 0 Posts
endpos

endos=xx is like trim(0,xx), BUT,
endpos just admits time (in seconds, or in hh:mm:ss format) or file size in Mbytes.
I think there's no way to make endpos frame accurate, since it looks at encoded movie, not at frame served to encoder (like trim does).
I'll give it a try, and edit this post to give further information.
BTW: didn't find a "startpos" function.
Reply With Quote
  #14  
05-04-2004, 05:18 AM
Prodater64 Prodater64 is offline
Free Member
 
Join Date: Mar 2003
Location: Palma de Mallorca - España
Posts: 2,925
Thanks: 0
Thanked 0 Times in 0 Posts
Quote:
Originally Posted by digitall.doc
...
BTW: didn't find a "startpos" function.
-ss <time>

(see -sb option too)
Seek to given time position.
EXAMPLE:
-ss 56
seeks to 56 seconds
-ss 01:10:00
seeks to 1 hour 10 min
Reply With Quote
  #15  
05-04-2004, 05:51 AM
digitall.doc digitall.doc is offline
Free Member
 
Join Date: Jul 2003
Location: Valencia (España)
Posts: 741
Thanks: 0
Thanked 0 Times in 0 Posts
Cool
Is SS a mplayer or a mencoder filter? (at work now)
So SS looks for a position, and starts encoding from there, isn't it?.
I'll give it a try if I can.
Reply With Quote
  #16  
05-04-2004, 06:48 AM
Prodater64 Prodater64 is offline
Free Member
 
Join Date: Mar 2003
Location: Palma de Mallorca - España
Posts: 2,925
Thanks: 0
Thanked 0 Times in 0 Posts
Quote:
Originally Posted by digitall.doc
Cool
Is SS a mplayer or a mencoder filter? (at work now)
So SS looks for a position, and starts encoding from there, isn't it?.
I'll give it a try if I can.
Is a:
Quote:
DEMUXER/STREAM OPTIONS
Reply With Quote
  #17  
05-04-2004, 07:17 AM
incredible incredible is offline
Free Member
 
Join Date: May 2003
Location: Germany
Posts: 3,189
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via ICQ to incredible
A little Quote!collection of the most needed Videofilters implementated in mencoder engine.
http://www.MPlayerHQ.hu/DOCS/man/en/manpage.html
Copyright is (c) MplayerTeam


Video filter are plugins that allow you to modify the video stream and its properties. The syntax is:

-vf <filter1[=parameters],filter2,...>

and here come the <filters> :


1. Deinterlacing / InverseTelecining


kerndeint[=thresh[:map[rder[:sharp[:twoway]]]]]
Donald Graft's adaptive kernel deinterlacer.
Deinterlaces parts of a video if a configurable threshold is exceeded.
thresh (0 - 255) Threshold (default 10).
map (0 or 1) Paint pixels which exceed the threshold white (default: 0).
order (0 or 1) Swap fields if 1 (default: 0).
sharp (0 or 1) Enable additional sharpening (default: 0).
twoway (0 or 1) Enable twoway sharpening (default: 0)

------------------------------------------------

detc[=var1=value2:var2=value2:...]
.... This was the first and most primitive inverse telecine filter to be added to MPlayer/MEncoder. .... Development on this filter is no longer taking place, as ivtc, pullup, and filmdint are better for most applications. .....

------------------------------------------------

ivtc[=1]
Experimental 'stateless' inverse telecine filter. Rather than trying to lock on to a pattern like the detc filter does, ivtc makes its decisions independently for each frame. This will give much better results for material that has undergone heavy edit- ing after telecine was applied, but as a result it is not as forgiving of noisy input, for example TV capture. The optional parameter (ivtc=1) corresponds to the dr=1 option for the detc filter, and should be used with MEncoder but not with MPlayer. As with detc, you must specify the correct output framerate (-ofps 23.976) when using MEncoder. Further development on ivtc has stopped, as the pullup and filmdint filters appear to be much more accurate.

------------------------------------------------

pullup
Third-generation pulldown reversal (inverse telecine) filter, capable of handling mixed hard-telecine, 24 fps progressive, and 30 fps progressive content. The pullup filter is designed to be much more robust than detc or ivtc, by taking advantage of future context in making its deci- sions. Like ivtc, pullup is stateless in the sense that it does not lock onto a pattern to follow, but it instead looks forward to the following fields in order to identify matches and rebuild progressive frames. It is still under development, but be- lieved to be quite accurate. No configuration options are available yet.
NOTE: Always follow pullup with the softskip filter when encoding to ensure that pullup is able to see each frame. Failure to do so will lead to incorrect output and will usually crash, due to design limitations in the codec/filter layer.

------------------------------------------------

softskip
Only useful with MEncoder. Softskip moves the frame skipping (dropping) step of encoding from be- fore the filter chain to some point during the filter chain. This allows filters which need to see all frames (inverse telecine, temporal denoising, etc.) to function properly. Should be placed after the filters which need to see all frames and before any subsequent filters that are cpu-intensive.

------------------------------------------------


filmdint[=options]
Inverse telecine filter, similar to the pullup fil- ter above. It is designed to handle any pulldown pattern, including mixed soft and hard telecine and limited support for movies that are slowed down or sped up from their original framerate for TV. ....
With no options it does normal inverse telecine, and should be used together with mencoder -fps 29.97 -ofps 23.976. When this filter is used with mplayer, it will result in an uneven framerate during playback, but it is still generally better than using pp=lb or no deinterlacing at all. Multiple options can be specified separated by /.

crop=w:h: x:y
Just like the crop filter, but faster, and works on mixed hard and soft telecined con- tent as well as when y is not a multiple of 4. If x or y would require cropping fractional pixels from the chroma planes, the crop area is extended. This usually means that x and y must be even.

io=ifpsfps
For each ifps input frames the filter will output ofps frames. The ratio of ifps/ofps should match the -fps/-ofps ratio. This could be used to filter movies that are broadcast on TV at a frame rate different from their original frame rate.

luma_only=n
If n is nonzero, the chroma plane is copied unchanged. This is useful for YV12 sampled TV, which discards one of the chroma fields.

mmx2=n
On x86, if n=1, use MMX2 optimized func- tions, if n=2, use 3DNow! optimized func- tions, othewise, use plain C. If this option is not specified, MMX2 and 3DNow! are auto-detected, use this option to override autodetection.

fast=n
The larger n will speed up the filter at the expense of accuracy. The default value is n=3. If n is odd, a frame immediately following a frame marked with the RE- PEAT_FIRST_FIELD mpeg flag is assumed to be progressive, thus filter will not spend any time on soft-telecined MPEG-2 content. This is the only effect of this flag if MMX2 or 3DNow! is available. Without MMX2 and 3DNow, if n=0 or 1, the same calculations will be used as with n=2 or 3. If n=2 or 3, the number of luma levels used to find the frame breaks is reduced from 256 to 128, which results in a faster filter without losing much accuracy. If n=4 or 5, a faster, but much less accurate metric will be used to find the frame breaks, which is more likely to misdetect high vertical detail as interlaced content.

verbose=n
If n is nonzero, print the detailed metrics for each frame. Useful for debugging.

dint_thres=n
Deinterlace threshold. Used during de-in- terlacing of unmatched frames. Larger val- ue means less deinterlacing, use n=256 to completely turn off deinterlacing. Default is n=8.

comb_thres=n
Threshold for comparing a top and bottom fields. Defaults to 128.

diff_thres=n
Threshold to detect temporal change of a field. Default is 128.

sad_thres=n
Sum of Absolute Difference threshold, de- fault is 64.

------------------------------------------------

softpulldown
This filter works only correct with MEncoder and acts on the MPEG2 flags used for soft 3:2 pulldown (soft telecine). If you want to use the ivtc or detc filter on movies that are partly soft telecined, inserting this filter before them should make them more reliable. Currently only libmpeg2 exports the needed flags. If used on material that does not set them, the filter does nothing.





2. Imaging


yuvcsp
Clamps YUV color values to the CCIR 601 range with- out doing real conversion.

------------------------------------------------

pp[=filter1[ption1[ption2...]]/[-]filter2...] (see -pphelp too)
(see explanations above in the black "-pphelp" outputted console screen.)
(always should be the first filter)

------------------------------------------------

crop[=w:h: x:y]
Crops the given part of the image and discards the rest. Useful to remove black bands from widescreen movies.
w,h Cropped width and height, defaults to orig- inal width and height.
x,y Position of the cropped picture, defaults to center.

------------------------------------------------

expand[=w:h: x:y: o]
Expands (not scales) movie resolution to the given value and places the unscaled original at coordi- nates x, y. Can be used for placing subtitles/OSD in the resulting black bands.

w,h
expanded width,height (default: original width,height). Negative values for w and h are treated as offsets to the original size. EXAMPLE: ex- pand=0:-50:0:0 ... this adds a 50 pixel border to the bottom of the picture

x,y
position of original image on the expanded image (default: center)

o
OSD/subtitle rendering.... 0: disable (default) ..... 1: enable

------------------------------------------------

scale[=w:h[:interlaced[:chr_drop[aram[re- size]]]]]
Scales the image with the software scaler (slow) and performs a YUV<->RGB colorspace conversion (al- so see -sws option).

w,h scaled width/height (default: original width/height)

interlaced Toggle interlaced scaling.

chr_drop chroma skipping
0: use all available input lines for chroma
1: use only every 2. input line for chroma
2: use only every 4. input line for chroma
3: use only every 8. input line for chroma

param scaling parameter (depends upon the scaling method used)
-sws 2 (bicubic): sharpness (0 (soft) - 100 (sharp))
-sws 7 (gaussian): sharpness (0 (soft) - 100 (sharp))
-sws 9 (lanczos): filter length (1-10)

presize Scale to preset sizes.
qntsc: 352x240 (NTSC quarter screen)
qpal: 352x288 (PAL quarter screen)
ntsc: 720x480 (standard NTSC)
pal: 720x576 (standard PAL)
sntsc: 640x480 (square pixel NTSC)
spal: 768x576 (square pixel PAL)

------------------------------------------------

hue[=hue:saturation]
Defaults are hue=0.0, saturation=1.0. Value ranges are -180-180 for hue, -2-2 for saturation (negative values result in a negative chroma).

------------------------------------------------

eq[=bright:cont]
Software equalizer with interactive controls just like the hardware equalizer, for cards/drivers that do not support brightness and contrast controls in hardware. Might also be useful with MEncoder, ei- ther for fixing poorly captured movies, or for slightly reducing contrast to mask artifacts and get by with lower bitrates. Initial values in the range -100-100 may be given on the command line.

eq2[=gamma:contrast:brightness:saturation:rg:gg:bg:wei ght]
Alternative software equalizer that uses lookup ta- bles (very slow), allowing gamma correction in ad- dition to simple brightness and contrast adjust- ment. Note that it uses the same MMX optimized code as -vf eq if all gamma values are 1.0. The parameters are given as floating point values. Pa- rameters rg, gg, bg are the independent gamma val- ues for the Red, Green and Blue components. The weight parameter can be used to reduce the effect of a high gamma value on bright image areas, e.g. keep them from getting overamplified and just plain white. A value of 0.0 turns the gamma correction all the way down while 1.0 leaves it at its full strength. Defaults are gamma=1.0, contrast=1.0, brightness=0.0, saturation=1.0, weight=1.0. Value ranges are 0.1-10 for gamma, -2-2 for contrast (negative values result in a negative image), -1-1 for brightness, 0-3 for saturation and 0-1 for weight.

------------------------------------------------

swapuv
Swap U & V plane.

------------------------------------------------

il=[d|i][s][:[d|i][s]]
deinterleaves and re-interleaves lines. The goal of this filter is to add the ability to process interlaced images pre-field without deinterlacing them.

d deinterleave (placing one above the other)
i interleave
s swap fields (exchange even & odd lines)

(This filter has to be used once BEFORE temporal filtering INTERLACED material using the deinterleave param. and once AFTER temporal filtering is done using the interleave param. like in Avisynth separatefiels().weave() ... but in another way especially for temporal filtering!!!)

@ DigiDoc ... you see, you only need il=x as it can deinterleave AND re-interleave

------------------------------------------------

denoise3d[=luma:chroma:time]
This filter aims to reduce image noise producing smooth images and making still images really still (This should enhance compressibility.). It can be given from 0 to 3 parameters. If you omit a param- eter, a reasonable value will be inferred.

luma spatial luma strength (default = 4)
chroma spatial chroma strength (default = 3)
time temporal strength (default = 6)

hqdn3d[=luma:chroma:time]
High precision/quality version of the denoise3d filter. Parameters and usage are the same.

------------------------------------------------

noise[=luma[u][t|a][h][p]:chroma[u][t|a][h][p]]
Adds noise.

<0-100> luma noise
<0-100> chroma noise
u uniform noise (gaussian otherwise)
t temporal noise (noise pattern changes be- tween frames)
a averaged temporal noise (smoother, but a lot slower)
h high quality (slightly better looking, slightly slower)
p mix random noise with a (semi)regular pat- tern

------------------------------------------------

smart- blur=rad:strength:thresh[:rad:strength:thresh]
A "smart"!! blurrer/Sharpener!

rad blur filter strength (~0.1-5.0) (slower if larger)
strength blur (0.0-1.0) or sharpen (-1.0-0.0)
thresh filter all (0), filter flat areas (0-30) or filter edges (-30-0)

------------------------------------------------


delogo[=x:y:w:h:t]
Suppresses a TV station logo by a simple interpola- tion of the surrounding pixels. Just set a rectan- gle covering the logo and watch it disappear (and sometimes something even uglier appear - your mileage may vary).

x,y Position of the top left corner of the lo- go.
w,h Width and height of the cleared rectangle.
t Thickness of the fuzzy edge of the rectan- gle (added to w and h). When set to -1, a green rectangle is drawn on the screen to simplify finding the right x,y,w,h parame- ters.


- End


Also very useful Examples:


Encoding DVD title #2, only selected chapters
mencoder dvd://2 -chapter 10-15 -o title2.m2v ....

Encoding DVD title #2, resizing to 640x480
mencoder dvd://2 -vf scale=640:480 -o title2.m2v .....




This Post contains Quotes from the www.mplayerHQ.hu Manual Document
(c) Mplayer Team!
Reply With Quote
  #18  
05-04-2004, 12:55 PM
jorel jorel is offline
Invalid Email / Banned / Spammer
 
Join Date: Aug 2002
Location: Brasil - MG - third stone from the sun
Posts: 5,570
Thanks: 0
Thanked 0 Times in 0 Posts

ink, you're "too much"!
Reply With Quote
  #19  
05-04-2004, 01:10 PM
incredible incredible is offline
Free Member
 
Join Date: May 2003
Location: Germany
Posts: 3,189
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via ICQ to incredible
You mean its non underestandable ....?

I thought putting the -vf filters in categories makes them finding easier ?
Reply With Quote
  #20  
05-04-2004, 03:42 PM
Jellygoose Jellygoose is offline
Free Member
 
Join Date: Jun 2002
Location: Germany
Posts: 1,288
Thanks: 0
Thanked 0 Times in 0 Posts
I think he meant Inc, you're incredible...

thank you. can't wait till all these are tested... however I still hope many more AVS filters will be ported to Mencoder internals!
__________________
j3llyG0053
Reply With Quote
Reply




Similar Threads
Thread Thread Starter Forum Replies Last Post
Avisynth: Crop and resize question urban tec Avisynth Scripting 3 06-13-2005 08:28 AM
MencodeME e CROP, OVERSCAN, RESIZE vicksson Conversão e Codificação de Vídeo (Português) 3 10-23-2004 02:10 PM
MenCalc or MEncodeMe crop/resize maurus Video Encoding and Conversion 13 05-27-2004 04:18 AM
TMPGEnc: crop without resize? rupan Video Encoding and Conversion 5 03-06-2004 10:36 PM
MPEG Mediator: Resize/crop tutorials? jorel Video Encoding and Conversion 2 08-24-2002 04:30 PM

Thread Tools



 
All times are GMT -5. The time now is 06:47 PM  —  vBulletin © Jelsoft Enterprises Ltd