{"id":1502,"date":"2014-02-08T10:42:27","date_gmt":"2014-02-08T08:42:27","guid":{"rendered":"https:\/\/alax.info\/blog\/?p=1502"},"modified":"2014-02-08T21:58:16","modified_gmt":"2014-02-08T19:58:16","slug":"something-went-terribly-wrong-in-x64-build-of-windows-media-video-9-decoder","status":"publish","type":"post","link":"https:\/\/alax.info\/blog\/1502","title":{"rendered":"Something went terribly wrong in x64 build of Windows Media Video 9 Decoder"},"content":{"rendered":"
\n

Unfortunately, 64-bit version of\u00c2\u00a0Windows Media Video 9 Decoder<\/a>\u00c2\u00a0is not as good as its 32-bit sister. 32-bit version is user an order of magnitude more frequently and does not give troubles, nevertheless 64-bit version offers similar feature set it is pretty hard to see it in action since it takes a 64-bit media application to host it and most of media applications are 32-bit (there is often a good reason for this), and even Windows SDK 7.0\u00c2\u00a0topoedit<\/code>\u00c2\u00a0comes pre-built as Win32 application only (provided with source code though, so one can built x64 peer – after fixing buildability issues and adding\u00c2\u00a0x64<\/code> configuration manually).<\/p>\n

Decoder is available as dual\u00c2\u00a0DMO<\/a>\/MFT<\/a>\u00c2\u00a0which enabled it for both DirectShow and Media Foundation APIs and similarly exposes the problem in both as well.<\/p>\n

Once in a while, 64-bit version of the decoder might be producing incorrect output, adding white dots where they are not supposed to be.<\/p>\n

\"02\"<\/p>\n

Because the problem resides supposedly in the decoder itself, it affects everything decoding Windows Media Video of this flavor, including<\/p>\n