|
|
| Marticus |
| Posted: Sep 1 2002, 02:12 PM |
 |
|
Unregistered
|
I am trying to shrink some large files to a more manageable size, but I don't want to shrink them all the way down to 3**x2**, so I tried 440x300 and found that I am getting an annoying glitch all the way through the reprocessed file.
Here is an example frame:
You can see the problem is a column of pixels on the left have been offset downwards, which is more evident when I zoom in on an affected area:
I tried using the Smart Resize filter by dgraft, but it turns out to use the same resize routines. Can anyone help solve my problem please? |
|
| Asmordean |
| Posted: Sep 1 2002, 02:59 PM |
|
|
Unregistered
|
I've tried to reproduce your problem but cannot do so.
What size is your input frame?
Colour format?
What settings are you using in resize?
I assume that the raw capture file doesn't exhibit this issue.
|
|
| Marticus |
| Posted: Sep 1 2002, 03:10 PM |
|
|
Unregistered
|
My input file is a vob via avisynth, however I have saved it as a full size uncompressed avi (~2gb) and used that as input and it exhibits the same behaviour. The input file is 720x480 @29.97fps, I clip the boundaries (null transform + cropping) to 684x477 (There's a lot of black on the edges). Then I use the resize filter to eg 360x240 and compress. |
|
| avih |
| Posted: Sep 1 2002, 04:46 PM |
|
|
Unregistered
|
some codecs/decoders/encoders only handle well sizes that are multiples of 16 or 32. maybe you used one of those in either your encoding or decoding.
as a rule of thumb, always use sizes that are multiples of at least 16, or even better, 32. give that a try, and report your results  |
|
| Marticus |
| Posted: Sep 1 2002, 05:32 PM |
|
|
Unregistered
|
Thanks, avih. 592x400 seems to work fine. I should have thought to try something like that myself, but I've just been learning (the hard way, try try try again) how to use AVI-Synth, and was a little short tempered after I found this bug in a long encode (hungry filters). |
|
