Calling DisplayConfig functions for a Windows 8.1 Miracast target

Note

Starting in Windows 10 (WDDM 2.0), the operating system ships with a built-in Miracast stack that can work on any GPU. For information about the Microsoft Miracast stack and the requirements of drivers and hardware to support Miracast displays starting in Windows 10, see the following documentation:

Driver developers should no longer implement a custom Miracast stack. Microsoft might remove support for custom Miracast stacks in a future version of Windows.

To reduce compatibility issues of existing apps being exposed to new Miracast targets, the QueryDisplayConfig and SetDisplayConfig function implementations have ways for apps to find Miracast targets:

  • A value of DISPLAYCONFIG_OUTPUT_TECHNOLOGY_MIRACAST in the DISPLAYCONFIG_VIDEO_OUTPUT_TECHNOLOGY enumeration indicates that the VidPN target is a Miracast device.
  • The Flags parameter value of QDC_ALL_PATHS in a call to QueryDisplayConfig won’t return any paths that connect to a Miracast target that doesn't have an active monitor attached.
  • For each path that has a connected Miracast monitor, QueryDisplayConfig returns the connector type that the Miracast sink reported. Internal Miracast sinks report a value of DISPLAYCONFIG_OUTPUT_TECHNOLOGY_MIRACAST in the DISPLAYCONFIG_VIDEO_OUTPUT_TECHNOLOGY enumeration. For example, if a Miracast sink reports that a TV is connected to the sink with a High-Definition Multimedia Interface (HDMI) cable, then QueryDisplayConfig would report the target type as DISPLAYCONFIG_OUTPUT_TECHNOLOGY_HDMI.
  • The DISPLAYCONFIG_VIDEO_SIGNAL_INFO structure has a VSync frequency divider member, vSyncFreqDivider, that’s used similarly to D3DKMDT_VIDEO_SIGNAL_INFO.vSyncFreqDivider.
  • The DisplayConfigGetDeviceInfo function provides the base connector type for any target. For a Miracast target, this function always returns a value of DISPLAYCONFIG_OUTPUT_TECHNOLOGY_MIRACAST in the DISPLAYCONFIG_VIDEO_OUTPUT_TECHNOLOGY enumeration.