Re: DirectX for C# SDK

"Chuck Walbourn [MSFT]" wrote:

The AVP managed component of MDX 1.1 was a very simplistic wrapper, and was
never intended to expose the full DirectShow interface to managed
developers. Most media applications are very perfomance sensitive, so
DirectShow applications tend to be written most often in C/C++. As noted in
my previous post, native interop at a level that makes sense for your
application is far more performant than a generic managed wrapper. If you
are looking for such a generic wrapper, they are easy to write and available
in shared source projects as well.

The Windows Media team has always owned DirectShow, even when it was
shipping in the DirectX SDK. There's been some mixed-messaging about
DirectShow with the release of Windows Media Foundation in Windows Vista,
and the plan is to eventually replace DirectShow with WMF in a future
version of Windows. Windows Media has not invested in DirectShow in a long
time, and is instead focused on WMF, but DirectShow continues to be
supported and is still an important API for many video/audio applications.
It has been supported through the Microsoft Platform SDK / Windows SDK since
April 2005, when it was removed from the DirectX SDK.

The first release of WMF is focused on protected content playback for
Windows Meida formats, and much work has gone into support existing
DirectShow applications as well for backwards compatiblity. DirectShow is
still the preferred API to write video applications for non-protected
content playback, supporting formats other than Windows Media (WMV, WMA) and
MP3, capturing, and editing.

See for details and
mitgration guideance with respect to DirectShow and Windows Media

As for managed technology supporting video scenarios, Silverlight is built
around having a strong streaming media functionality.

-Chuck Walbourn
SDE, XNA Developer Connection

This posting is provided "AS IS" with no warrenties, and confers no rights.