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 > General > Newbies
Register FAQ Calendar Today's Posts Search

Reply
 
Thread Tools Search this Thread Display Modes
Old 6th October 2021, 18:03   #21  |  Link
Gavino
Avisynth language lover
 
Join Date: Dec 2007
Location: Spain
Posts: 3,431
Quote:
Originally Posted by hello_hello View Post
... It seems a few decimal points can make quite a difference there too.
You should always use floating point values with Animate when animating a function which has float parameters.
Integer values (without decimal point) will be converted to float on entry to the animated function, but the interpolation itself will be done on an integer basis (hence potentially truncated).
Quote:
As a side note, there's no shortage of artefacts when I try the zoom example on the Avisynth wiki. If I use BiliearResize it's fine, but unfortunately my poor little monkey brain doesn't understand why.
This is because (as I think you discovered later), unlike all other resizers, BicubicResize has the additional parameters b and c before the cropping parameters. (Perhaps because they existed prior to the introduction of the cropping extension). So a 'gotcha' when animating resizers is that BicubicResize is a special case and has to be explicitly given these parameters too.

So the wiki example is wrong at present (although correct if a different resizer is used in place of BicibicResize).
__________________
GScript and GRunT - complex Avisynth scripting made easier
Gavino is offline   Reply With Quote
Old 6th October 2021, 20:31   #22  |  Link
Richard1485
Guest
 
Posts: n/a
Ah, so it's just that pretty much any resizer other than BicubicResize would have done, and hello_hello just happened to choose BilinearResize. I thought that the question was why the latter, in particular, is fine in terms of artifacts. (Does the weighted average smooth them out somehow?) It's a soft resizer, so I figured that helps, but anyway I misunderstood. Thanks!
  Reply With Quote
Old 10th October 2021, 17:10   #23  |  Link
hello_hello
Registered User
 
Join Date: Mar 2011
Posts: 4,829
Well... if nothing else, CropResize makes the Ken Burns effect easy. No need to do the math in advance because the script won't distort the picture.
And it's fun watching the cropping preview animated. At least the first few times......
(This is a test version, the current CropResize doesn't accept float for cropping)

Code:
CropResize(1280,720)

v = Last.Trim(18900,18900).Loop(190)
Animate(v, 10, 179, "iCropResize", 
\    960,720, 0.0, 40.0, -400.0, -40.0,
\  960,720, 745.0, 120.0, -250.0, -310.0)
Animate Test.mkv (2.9MB)

Animate Cropping Preview.mkv (996kB)


Last edited by hello_hello; 11th October 2021 at 14:13.
hello_hello is offline   Reply With Quote
Reply


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 14:45.


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