View Full Version : order of avisynth deinterlace vs crop filter
bartnl
17th May 2003, 19:19
Is there a reason why Gordian Knot by default puts the FieldDeinterlace() filter before the crop() statement? I use Gordian Knot a lot but always edit the the avisynth script to put crop() as first statement to increase encoding speed. Personally this seems so obvious that I do not understand why this is not the default behaviour of Gordian Knot. Maybe i'm overseeing something important with regard to the deinterlace filter that would prohibit cropping before aplying the deinterlacing?
manono
18th May 2003, 08:49
Hi-
I'm not positive of the reason, but I think it has to do with Decomb's Telecide-Decimate and FieldDeinterlace requiring the Horizontal Crop to be a multiple of 4. I always put both Telecide-Decimate and FieldDeinterlace after the crop also, but if you're not careful with the crop values, they can screw up on you. And then we'll get bombarded with claims of something being broken.
bartnl
18th May 2003, 16:26
I think it is since 0.28 that Gordian Knot prohibits you from using 'wrong' cropping resolutions? Before that it was always possible to select wrong cropping resolutions that did not work with avisynth filters, tried that as well ;)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.