| Thrax |
04-02-2009 08:13 PM |
As of 7068, the Windows Media Foundation lock is still in place. I have been talking to my sources and they say it's still present in build 7072 as well.
Back in build 7000 you could take ownership of the relevant WMF DLLs with CACLS, which would shift control back to third-party codecs. This technique no longer works, which has left me scratching my head.
My first unfortunate runin with this BS came when I tried to use FFDshow's post-processing engine to tweak the output of an MPEG4 stream on Media Player Classic (HC fork). More precisely, I prefer to sharpen the image and tweak the levels of the image to produce more vibrant colors... This is not possible with WMF in play, as FFDShow's decoders are superceded by Win 7's internal WMF codecs.
I'm of three minds on this predicament: It's intentional to get an accurate and sanitized look at WMF codec performance, it's a deliberate gambit to crush codec conflicts (XP was a mess), or programmers haven't figured out the new model.
I tend to believe that the first option is the case, as the latter two seem incredibly irregular. I and others have spoken to Microsoft PR about the codec issue in Windows 7, and they're distributing this canned response:
Quote:
As we move toward the release of Windows 7, we have worked to add more codecs and file types to allow for a better user experience. We also allow Microsoft experiences to use codecs and other format technologies from third-party companies, just as we always have. Third party applications can use the Microsoft codecs or their own. Microsoft does not restrict the use of third-party codecs.
|
All told I believe that we'll probably see codecs unlocked for RC1.
|