aldaco12
29th November 2005, 11:39
Hi. I'm experiencing this strange fact, and I would like to know if usuallly happens with AVI (maybe because they are already non-interlaced. This does not happen with D2V files!).
Let's supose I have a 610 x 344 AVI movie.
I load it with this script:
AviSource("movie.avi")
LanczosResize(448,344)
AddBorders(16,116,16,116)
AddAudio()
ConvertToYUY2()
so the final image will be (448+16+16,344+116+116) = (480,576) PAL SVCD
using the whole 344 Y pixels of the AVI (adding black border to have a PAL compliant video) and taking into account the 16+16=32 pixels lost by my TV screen (no black border is seen).
What I observed is that I always keep , when I resize in this way, the aspect ratio even if I didn't take into account the aspect ratio existing in the original AVI. This is very useful, because in this way, I keep all Y AVI resolution and almost all AVI X resulution (losing only a few X pixels , the ones exceeding 448) losing almost nothing, because the command LanczosResize is very good.
My question is: why does, this, seem to happen always, on AVIs?
Let's supose I have a 610 x 344 AVI movie.
I load it with this script:
AviSource("movie.avi")
LanczosResize(448,344)
AddBorders(16,116,16,116)
AddAudio()
ConvertToYUY2()
so the final image will be (448+16+16,344+116+116) = (480,576) PAL SVCD
using the whole 344 Y pixels of the AVI (adding black border to have a PAL compliant video) and taking into account the 16+16=32 pixels lost by my TV screen (no black border is seen).
What I observed is that I always keep , when I resize in this way, the aspect ratio even if I didn't take into account the aspect ratio existing in the original AVI. This is very useful, because in this way, I keep all Y AVI resolution and almost all AVI X resulution (losing only a few X pixels , the ones exceeding 448) losing almost nothing, because the command LanczosResize is very good.
My question is: why does, this, seem to happen always, on AVIs?