Avisynth: Advantages/Disadvantages of Using Gripcrop() or FitCD?

sparskter · #1 07-06-2005, 10:18 PM

Hello! New member, new post

Well. FITCD can generate avisynth scripts for manipulating overscan:

http://shh.sysh.de/fitcd.html

Here is a script for an avi 720x480 and overscan=3:

Code:

# -= AviSynth v2.5.5.0 script by FitCD v1.2.4 =-
AVISource("D:\animes\anime\Karekano\[Kamikakushi]_Karekano_01_[DVD_720x532][56D5A708].avi")
LanczosResize(640,432,0,0,720,532)
AddBorders(40,24,40,24)
#Trim(0,43296).FadeOut(150)

And this is a script using GripCrop():

Code:

movie="C:\karekano.avi"
AVISource(movie,false)
myoverscan=3
width=720  #352, 480, 528, 704, 720
height=480  #240, 480

GripCrop(720,480,overscan=myoverscan,source_anamorphic=false,dest_anamorphic=false)
GripSize(resizer="LanczosResize")
GripBorders()

Well, my question is: is there any difference between these two methods(fitcd and gripcrop() ) ? Is GripCrop() better ?

best regards
sparskter

kwag · #2 07-06-2005, 11:34 PM

Hi sparskter, and welcome

I suggest you keep using FitCD, because GripFit sometimes will give you a (pun intended) fit

Really. Sometimes it just gets confused with the source, and will give you wrong parameters. So it's better to keep using FitCD.

-kwag

Dialhot · #3 07-07-2005, 03:28 AM

Let do a slightly different answer : GripCrop is aimed to cut the existing borders of the source and then resize the remaining areq (called film area) correctly.

It's true that FitCD is better to compute the resizing parameters but you have to feed with correct values if there are some borders in your source (border that you have to find using virtualdub and the nulltransform filter for instance).