Linked by Thom Holwerda on Thu 12th Feb 2009 08:05 UTC, submitted by poundsmack
Permalink for comment 348605
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.





Member since:
2007-06-21
It really doesn't matter. The reference implementation is Silverlight, that's what developers will be writing for and Silverlight will use Microsoft's codecs. You will then be sucked along in having to support them, if you want to be relevant to your users.
Think about it. If you didn't have to use Microsoft's codes then why is there a need for Moonlight at all? Either you can't see this or you've had a major injection of denial. "
You seem to be extremely confused.
Silverlight content authors do not target a codec implementation, they write Silverlight applications that may or may not use encoded audio/video (which would be in wmv, mp3, etc).
Moonlight is needed because Silverlight isn't a video player plugin, it's an RIA framework which just happens to include audio and video playback.
Just because a Silverlight application uses wmv doesn't mean you, as a Moonlight user, are limited to having to use the Microsoft codec blob - in fact, we Moonlight developers used the FFmpeg codec implementation throughout most of the development effort for Moonlight 1.0.
Alas, the content that users will want to view with Moonlight will not ;-). "
If you want to view the content, you have to use Moonlight or reboot to Windows and watch it using Silverlight.
Your choice.
If Moonlight didn't exist, you wouldn't have a choice at all.