Desktop duplication

Windows 8 introduces a new Microsoft DirectX Graphics Infrastructure (DXGI)-based API to make it easier for independent software vendors (ISVs) to support desktop collaboration and remote desktop access scenarios.

Such applications are widely used in enterprise and educational scenarios. These applications share a common requirement: access to the contents of a desktop together with the ability to transport the contents to a remote location. The Windows 8 Desktop duplication APIs provide access to the desktop contents.

Currently, no Windows API allows an application to seamlessly implement this scenario. Therefore, applications use mirror drivers, screen scrapping, and other proprietary methods to access the contents of the desktop. However, these methods have the following set of limitations:

• It can be challenging to optimize the performance.
• These solutions might not support newer graphics-rendering APIs because the APIs are released after the product ships.
• Windows does not always provide rich metadata to assist with the optimization.
• Not all solutions are compatible with the desktop composition in Windows Vista and later versions of Windows.

Windows 8 introduces a DXGI-based API called Desktop Duplication API. This API provides access to the contents of the desktop by using bitmaps and associated metadata for optimizations. This API works with the Aero theme enabled, and is not dependent on the graphics API that applications use. If a user can view the application on the local console, then the content can be viewed remotely as well. This means that even full screen DirectX applications can be duplicated. Note that the API provides protection against accessing protected video content.

The API enables an application to request Windows to provide access to the contents of the desktop along monitor boundaries. The application can duplicate one or more of the active displays. When an application requests duplication, the following occurs:

• Windows renders the desktop and provides a copy to the application.
• Each rendered frame is placed in GPU memory.
• Each rendered frame comes with the following metadata:
  • Dirty region
  • Screen-to-screen moves
  • Mouse cursor information
• Application is provided access to frame and metadata.
• Application is responsible for processing each frame:
  • Application can choose to optimize based on dirty region.
  • Application can choose to use hardware acceleration to process move and mouse data.
  • Application can choose to use hardware acceleration for compression before streaming out.

For detailed documentation and samples, see Desktop Duplication API.