How to bypass resize ?

Hi, first of all, many many thanks to len0x and all others!! I'm encoding a Divx at the same exact resolution as the input, so I don't need at all the resize filter. The fastest way I found is to open the avs script and to comment the LanczosResize(...) command before starting to encode, but I was wondering if there is another way. For example, is any of the resize filters smart enough to understand that if input resolution=output resolution it doesn't need to do anything? Or maybe could GordianKnot itself recognize this situation and avoid to add the Resize command in the avs script? Or maybe could it be another option in the "Save&Encode" window? Bye!

My doubt was if the "resizer" is able to recognize that no real resize is needed and therefore to bypass all its work. Anyway, without the resize my encoding took 1 hour+28 minutes for 1st pass and VirtualDubMod crashed during the 2nd pass, when the estimated time was 58 minutes. I restarted from scratch, I left the LanczosResize active and the 1st pass took 1 hour+39 minutes and the 2nd pass 1hour+12 minutes. NB: This is not an accurate test because I was working with the PC, but it seems that some overhead exists. Bye!

There is no "good" way to do it. The fastest way should be by pressing edit in the save .avs window.

Yeah, if you're doing credits (with DivX) it's a bit more work. Technically it would probably be very easy to do it, but I think len0x said the problem is the space. There are already 6 resizers and it may be hard fitting more. I'm no programmer, but I can't imagine it being that hard telling Gordian Knot to comment the resizer if input and output is the same. But len0x is for vacation for a few weeks, so we'll have to wait.

maybe having the resize filter as an option..... and while i'm thinking about extra options....an auto-autocrop option :p just something that some people (ie: me) would find handy. I'm currently using GK to recode SVCDs and they're a mix of 4:3 and 16:9 format...so occasionaly i forget to hit the autocrop button...:rolleyes:

Did you use a fixed quants encoding? In that case, where there any difference in filesizes?