Quote:
Originally Posted by Leak
Thanks. 
Ah, I see - the resize adds borders at the top and bottom that of course aren't in the image data (so AviSynth will still see an image with no borders), but are taken into account when I request the DAR of the image.
I'll see if I can figure out a way to get the DAR of the image without the borders. Still, the borders will be lost that way, but what should I do? AviSynth has no concept of "padding" the image on it's four sides (as much as it has no concept of "aspect ratio", that's why I added those 2 variables - but I really don't want to frankenstein yet another workaround like this into the filter), so I'd either have to add the borders to the image data (yuck) or simply drop them. |
Please don't drop them. Users may want to adjust to full screen.
Quote:
|
But of course, it's best not to use the resize filter before the AviSynth filter; if you need to resize you can always do that at the beginning of the AviSynth script - that'll also save some RAM as it won't buffer the resized images; it's probably best to put the AviSynth filter as early as possible in your filter chain anyway.
|
True, but bug is a bug...
Not all users are experts, they may want to use ffdshow's resize rather than learning how to use AviSynth's resize.