I already told about that to Inc and he answered that the scale is necessary as it does not only scale. I didn't have any problem without it but I confess that in the manual it is say that scale also perform a space color conversion that seems to be necessary for other filters.
It's a little the equivalent to our ConvertToYV12().

For the other information I let you read into the manual :
http://www.mplayerhq.hu/DOCS/man/fr/manpage.html

(note: here we are using lanczos so the 9 is the precision of the filter, that is something taht you can modify in avisynth).

But the slower things in all this is the unsharp. You lose 3 fps for each usage and here it is used 2 times :-(

But that Inc said it don't mean that it he say to be correct.
I am always reading manual before posting. In manual, there is not filters that needs rgb colorspace (at less I can't find out it). But I just find out an option explanation that permits to deduce that scale it is not necessary when original and scaled frame size match.

I understand the blue remarked text as it is not usual neither necessary to use scale when mentioned condition is true. (except for spuaa option, of course)

Is it correct this way?
Again from manual, don't would be?:

--------------------------
Visit: Intermediate guide: MencodeMe/Win32 - Avisynth - MakeAvis by Prodater64.
Visit: KVCD - MencodeMe - Auxiliar Task - KVCD Docking Gate by Prodater64.
Visit: Mencoder scripting with AVSEdit and Guide for Multiple Files by Prodater64.
Visit: Mini-guide quick and easy - DVD to (S)KVCD with MencodeMe by Maurus.
Visit: Mencode-me: a newbie oriented GUI - 0.23 is out! by VMesquita.
--------------------------
http://www.digitalfaq.com/archives/error.gif

Inc, as myself, never "say" something. He report something he has experimented himself.
As I told you, SOMETIMES you need that conversion. And has I also told you : PERSONNALY I never had any problem.

You see, that's not just "saying"...

Don't always trust the man : scale does NOT convert to RGB (and that is a good thing) but in the case of lanczos it seems to output in YV12. Unfortunally, in all my attempt, the source was also YV12 so I never saw the benefit of this. And BTW I don't use scale when I do not need to scale (just as you are suggesting).

But I just find out an option explanation that permits to deduce that scale it is not necessary when original and scaled frame size match.

No, the part in blue tells taht you can FORCE the scaling even when it is not necessary. That means that without that NO SCALING is done when the target has the same res than the source. In other words, "scale" is optimized.

For sure not ! "sws" is a parameter independant, scale is an option of the "vf" parameter. You line in syntaxically incorrect.

@anyone,

Mencoder.exe -include temp.conf -lavcopts vbitrate=1037:vpass=1 "F:\Temp\KSVCD.avs" -o /dev/null

Also, I'm trying to use MEncoderAVS from http://ffdshow.sf.net/ffmpeg_avs.rar
and every frame is dropped for "duplicate error" which creates no log and
mpv files. Is this compiled version of MEncoder working for Win32 :?:
Others claim to have it working, but I can't get it to stop dropping
frames for "dup error" :roll: This avs version would allow me
to encode directly from an avs script instead of MakeAVIS avi file. :)

-BP

:lol: Nice. (shure I dont got "holes" in my hands)

Well ....
IF you would see the log of the console the forced colorspace conversion seems to be fixed as now the scaler just does a BYpass IMHO as in my case i got NO fps speed loss if not scaling in effective is set due to values different from the orig state!.

"YV12 to YV12 colorspace scaling" in case of DVD inpout resizing or similair quoted is written there already since a lot of outcomed builds, means since 1-2 Month!

Try to load a strange mpeg4 codec and apply a filter (I dont know which one suffered now but ..) ... that caused a crash in mencoder IF that Scale was not used before!

Also ... if you look into mencoder Console log .... Verrry often when mencoder cant recognise the input diata... he uses "scale" to get that input decodable. So as Phil said ... theres mor "in" :scale: than just a scaler.

And according to cosmetics ... ;-) Even when using fitcd on a 720 source just beiing cropped to 704 .... you wont find only a "Crop" line in the avs output script generated by Fitcd or Moviestacker, ... no ... the whole Bicubicresize(XXX,YYY,i,i,x,y,XXX,YYY) will be put out with "sclaing" parameters.

You tell you read manuals? Nice. Ok. I also do ... but Practice will also give a little overview whats happening. Then you will see that some parts of the manual have not been updated properly ... as the console log output DOES report something different.

Generally: Shure Im not everytime right as im just a product of "this" human world. But I do not "just assume" I at least do "say" things if I did try them before :!: :arrow: no offense 8)

Wouldnt be ? I think you should try as I saw that scale:.....:9 is the argument for lanczos ... where the single "-sws 9" could be the sclaer argument for mplayer ??? Maybe its needed to be double mentioned .. which would be silly but we never know. And that could be found out.

No offense Phil, please, I know Inc. and your working way.

I understand that from:

--------------------------
Visit: Intermediate guide: MencodeMe/Win32 - Avisynth - MakeAvis by Prodater64.
Visit: KVCD - MencodeMe - Auxiliar Task - KVCD Docking Gate by Prodater64.
Visit: Mencoder scripting with AVSEdit and Guide for Multiple Files by Prodater64.
Visit: Mini-guide quick and easy - DVD to (S)KVCD with MencodeMe by Maurus.
Visit: Mencode-me: a newbie oriented GUI - 0.23 is out! by VMesquita.
--------------------------
http://www.digitalfaq.com/archives/error.gif

You just need lessons on "how to read nice UNIX app lan page" :-)

In correct english this gives :

"if the scaling method (that is setted by -sws option as you can read in the manual several pages above this one) is bicubic (that correspond to -sws 2) then this parameter represents the sharpness and can take a value from 0 to 100.

if the scaling method is gaussian(that correspond to -sws 7) then this parameter represents the sharpness and can take a value from 0 to 100.

if the scaling method is lanczos(that correspond to -sws 9) then this parameter represents thefilter length and can take a value from 1 to 10."

if the scaling method is something else than the three values above, then this paremeter is not used."

As you can see, the manual would have twice the number of pages if everything was expressed like this ! :-D

@ Dialhot: Thank you.

In Argentina (where I'am from) we say (more or less): Who don't know is like who don't see.
Thank for your lessons.


--------------------------
Visit: Intermediate guide: MencodeMe/Win32 - Avisynth - MakeAvis by Prodater64.
Visit: KVCD - MencodeMe - Auxiliar Task - KVCD Docking Gate by Prodater64.
Visit: Mencoder scripting with AVSEdit and Guide for Multiple Files by Prodater64.
Visit: Mini-guide quick and easy - DVD to (S)KVCD with MencodeMe by Maurus.
Visit: Mencode-me: a newbie oriented GUI - 0.23 is out! by VMesquita.
--------------------------
http://www.digitalfaq.com/archives/error.gif

Not trying to be a pest, (and I understand about Kwags noise & minbitrate thingy), but wouldn't having hqdn after noise=3th remove the noise you've just put in?

,hqdn3d=3:6:2,unsharp=l3x3:-0.7:c3x3:-1.5,noise=3th, Instead? or am I waaay wrong... :oops:

I didn't noticed that in the previous post but yes, you are right. I did the same mistake 2 days ago and changed that since then.

WOW!!

The Fluffbutt actually got something you guru's didn't!!!

:lol: :lol: :lol: :lol: :lol: :lol:

<PURRRRRRRRRRRRRRRRRRRRRRRR> !!!!

We just find funnier to let you discover your mistakes by yourself and answer after that : "you didn't knew that ? pffff.... newbies..."

:-D

:lol: :lol:

:rotf: