This has to be the worst article ever published on THG, inaccurate and so little content. The worst error has to be when the author claims an error/glitch in the new DivX codec, and uses a screenshot from flask to prove his point.
If the author had ANY clue whatsoever of what he was writing about, he would surely know that flask is an mpeg DECODER, and that the screenshot he shows is the output of the mpeg DECODING process and has nothing to do with the codec he has configured - in this case the DivX4.01.
The "glitch" in question is an interlace problem, which ironically enough the new divx4 codec can fix you check the "de-interlace" button.
I have noticed a serious error in your post so it seems only fit that you get a taste of your own medicine. Flask is not a "DECODER" it is a decoder and a re-encoder both. Flask needs help to decode the source which will depend on the type of source and it shall need help to encode (record) to which ever codec is picked as an output. If all Flask did was decode all it could do is play.
I would know nothing of Flask or any other conversion program if it were not for Tom's page and thank them for sparking an intrest. Of course to really get into it requires more information then Tom's page provides but that is what <A HREF="http://www.doom9.net" target="_new">http://www.doom9.net</A> and <A HREF="http://www.divx-digest.com" target="_new">http://www.divx-digest.com</A> are for. For some reason I find it had to get to down on Tom for some technical errors that are not too important to a newbie. When someone is no longer a nubie they will go elsewhere for more complete info.