Hm. For now, I don't want to get into all this processing data format stuff that AutoGK passes to VD. But I might later. I agree that it would be nice to have an extra user interface for those who have some idea of what they do, but still don't want to go through all the big Gordian Knot hassle (which pretty much describes myself :) ). For now, AGKExpert offers a way to abort the various VD passes (particularly _comptest), in order to change settings before execution. The modifications can be saved in a special vcf file, which is then merged with the AGK settings on each subsequent pass. So far, this solution works quite well for me. However, it requires quite some VD knowledge, which is pretty much the opposite of the AutoGK approach. Ugh - not sure - I think it's exactly Codec changes that AGKExpert does not preserve. This is the ones that I couldn't easily decipher. AGKExpert only works for Filters, not for the compression. At least AGKExpert permits you to abort also the last VD job, and determine yourself what the last pass settings should be - including the compression. If I could finally get that ... VirtualDubMod source to compile with VC6, I would probably try to create a special VD-AGK version that uses VD's processing code, but provides an easier interface just for that purpose. But heavens - why does the source come with a VC6 project file if it does not compile? Maybe I'm going to try NanDub. Other disadvantages may arise with it, but at least that one I can compile. Or maybe we are lucky, and one day Lenox still decides to provide us with the source, so we can build Semi-Auto-GK...