I've updated the first post. Uploading the source isn't really easy to do, because it's a VOB. I will have to try other sources to see if it happens to them as well.
--------------------- Channing Preston Madison Motorsports
Please no simplification :) I'm guessing the problem is source, script, etc., because the only difference with skystrife's build is the hrd pulldown patch. Are you using --nal-hrd?
The memory usage of x264 in the last month? has significantly reduced, or at least thats what I've experienced! I'm encoding something right now with the normal filters I've used before, x264 only shows as using 128mb or ram under the task manager as where before it would be using up to 1gb! Actually even when encoding with a few things open, it only shows as 1.2gb of ram used in total under task manager with Vista x64. Going by this, I would find it difficult to think that it could be reaching the 2gb limit, something would have to be seriously wrong. Is your computer overclocked, or ram settings tweaked?
--------------------- For Sale- Infinity Basslink 2
nope. x264 used to use 1GB, skystrife's build is using 500MB right now. Anyways it would be strange that a new build would affect that much cpu/ram heat.
I didn't have time to upload anything yet, but the problem is here: SeparateFields() DeBlock() Weave() line 1 and 3 work fine line 2 works fine together I get this AviSynth error randomly: CAviStreamSynth: System Exeption - Access Violation at 0x39e643f, reading from 0x69ac0a6 Now it is an avisynth error, but only affects randomly x264. BTW I also happens with skystrife's build, just for somereason the first time it didn't happen. It's more likely to happen when using --b-adapt 2 If I can find some time later this week I'll post the source.