# HDR and choosing the GPU behind the virtual screen

> Expanding the display path while improving configuration.

Canonical page: https://pyrosoft.pro/blog/hdr-and-choosing-the-gpu-behind-the-virtual-screen

Live development journal; no publication date.
Work period: 2023-12-02 to 2024-08-31
Updated: 2026-10-20

Creating another desktop is the first step. The next question is what kind of display it can be and which GPU should render it. The December 2023 through summer 2024 work pushed the Virtual Display Driver further in both directions.

HDR support entered the history on December 2. That opened up a more useful virtual-display path for supported Windows HDR workflows, with the operating system, capture software and receiving display still determining the complete result. A virtual monitor advertising HDR doesn't make every part of a streaming chain HDR-capable by itself.

Render-adapter selection followed in the spring. On a machine with more than one GPU, letting the user choose the adapter is much more practical than hoping the default matches the intended setup. That can matter when the GPU doing the work and the one connected to a physical panel aren't the same device.

The summer changes included work toward one driver for Windows 10 and Windows 11, plus GPU fallback and XML configuration. By August, the history also records the XML and EDID work moving together. Those pieces help describe what the virtual monitor should expose and how the driver should recover when a preferred adapter isn't available.

There were installer and control-panel prototypes along the way. They show the project expanding beyond the driver itself, though their early presence shouldn't be confused with the later standalone control panel's maturity.

This stage made the virtual monitor more adaptable. We could start thinking about the intended display characteristics and the rendering hardware as choices in the setup, while still checking each combination against the Windows version and the software that would capture it.