From: Diego Biurrun Date: Sun, 15 Feb 2009 18:59:18 +0000 (+0000) Subject: Explain how AV_XVMC_RENDER_MAGIC got its seemingly arbitrary value. X-Git-Tag: v0.5~407 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=e98b47557bba168bffd78eb46f0e9ecbdac6c02a;p=platform%2Fupstream%2Flibav.git Explain how AV_XVMC_RENDER_MAGIC got its seemingly arbitrary value. Originally committed as revision 17342 to svn://svn.ffmpeg.org/ffmpeg/trunk --- diff --git a/libavcodec/xvmc.h b/libavcodec/xvmc.h index 5c87957..993f8c6 100644 --- a/libavcodec/xvmc.h +++ b/libavcodec/xvmc.h @@ -30,8 +30,8 @@ #define AV_XVMC_STATE_PREDICTION 2 /** the surface is needed for prediction, the codec manipulates this */ #define AV_XVMC_STATE_OSD_SOURCE 4 /** this surface is needed for subpicture rendering */ #endif -#define AV_XVMC_RENDER_MAGIC 0x1DC711C0 /**< magic value to ensure that regular pixel routines haven't corrupted the struct */ -// 1337 IDCT MCo +#define AV_XVMC_RENDER_MAGIC 0x1DC711C0 /**< magic value to ensure that regular pixel routines haven't corrupted the struct + the number is 1337 speak for the letters IDCT MCo (motion compensation) */ struct xvmc_pix_fmt { /** Set by calling application