Originally Posted by scowl
Of course this code makes rigid mathematical assumptions on what the correct values of the flags to XvMCPutSurface are (i ^ 3???) but at least it isn't "bloated" by defining them explicitly with screen-wasting hogs like "XVMC_TOP_FIELD" that might tell you what it's actually doing.
i ^ 3 in C, ^ XOR.. It's a very fast trick to calculate a modulus of 4