AVS optimizations for next gknot

[iMaGe]

taken from the avisynth scripting language reference guide:

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

BilinearResize(target-width,target-height,clip)
BilinearResize(source-left,source-top,source-width,source-height,target-width,target-height,clip)

The BilinearResize filter rescales the input video frames to an arbitrary new resolution. If you supply the optional source arguments, the result is the same as if you had applied Crop with those arguments to the clip before BilinearResize (except faster).

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

BicubicResize([b,c,]target-width,target-height,clip)
BicubicResize([b,c,]source-left,source-top,source-width,source-height,target-width,target-height,clip)

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

the key here... is that we can eliminate the crop(w,x,y,z) command, and get a speed boost at the same time. i guess thewef already knew this, and just doing crop for the sake of readability ...

what do you think? is the speed boost that the text is saying negligible?

[TheWEF]

could you please do a test to confirm that this really is faster?

[roy]

You're wrong. It should be:

BilinearResize(clip,target-width,target-height)
BilinearResize(clip,target-width,target-height,source-left,source-top,source-width,source-height)

or you get an error

I'm testing this option now but I don't see any difference in the speed encoding. I dont think that we can expect any.

Avisynth must do the same when we use crop or not. It must in any way be done.

[Psyche]

Sometime ago I made a test, and the results were surprising. In fact not only cropping and resizing at the same time wasn't faster, but slower, not much, but slower. (Something to do with alignment I guess)
Anyway if someone wants to do a test it could be useful (but not much I guess again).