MPCVR-Plus 1.7

MPCVR-Plus 1.7

Since 1.6 (764c4d1). Measured with the tools in tools/dlssnr_probe, on an RTX 3050.

The fork is now MPCVR-Plus

DLSS 5 was the first thing this fork added and it stopped being the main one a while ago —
the upscalers, the chroma pre-pass, the sharpening and render ahead all stand on their own.
So the repository is MPCVR-Plus.

GitHub redirects the old address, so nothing you have bookmarked or cloned breaks. The branch
is unchanged, so the filter still reports itself as 0.10.8.xxxx.dlss5.

One settings page, seven tabs

The two pages — Settings and DLSS — are now one, laid out in the order the picture travels:
Source, Chroma, Scaling, Detail, DLSS 5 NR, HDR, Presentation. Things that belong together
are together at last: sharpening sits with detail instead of among the presentation options,
and DLSS Super Resolution sits with the other enlargers instead of on a page of its own.

Tabs across the top rather than a list down the side, so each tab spreads across the width:
720x371 pixels where the old page was 720x562. Drawn with the system's own group boxes and
check boxes, so a player that themes its dialogs themes this one too.

Upstream's page is left in the tree untouched and simply not listed, so a merge from upstream
still costs nothing.

Every option has a tooltip, and a greyed option shows its own — which is the one worth
reading, since it says why the option is greyed.

Greying that follows the settings, not the film

Request Super Resolution could not be brought back by the box it is supposed to answer. The
page asked the renderer what the video processor was doing with the picture at hand, and a 4K
film on a 4K screen leaves it nothing to resize, so the line greyed whatever the chroma
pre-pass said. A Dolby Vision film did the same for another reason.

These are settings for every film there will ever be, so the film playing now no longer gets a
vote — with one exception, which is spelled out on the page:

Dolby Vision carries its own colour and its own reshaping, which a fixed-function video
processor cannot convert, so the renderer hands the whole chain to the shaders and the
processor is not in it at all. RTX Video Super Resolution lives inside that processor and has
nowhere to run. Use the video processor for resizing now greys while that is playing, with a
line saying why, and the chroma and scaling lists go live, because there the shaders really are
doing all of it.

There is a way round it for a file carrying an HDR10 layer under the Dolby Vision one — profile
8.1, AV1 profile 10.1, which is most of what is released: leaving Prefer Dolby Vision over PQ
and HLG off plays that layer, keeps the processor, and Super Resolution with it.

DLAA: DLSS SR with nothing to enlarge

DLSS only enlarged, so a film already at the screen's size never reached it. Also run when no
enlarging is needed (DLAA) lets it run there too, rebuilding the picture without changing its
scale — the mode games call DLAA. The statistics line says
DLSS SR : 3840x2160->3840x2160 DLAA/M.

It is a whole DLSS pass at the output size, which is the most expensive place to put one. Per
frame on an RTX 3050:

picture	DLSS SR	optical flow	fits a 24 fps frame (41.7 ms)?
1280x720	12.6 ms	3.3 ms	yes
1920x1080	14.0 ms	2.7 ms	yes
3840x2160	70.0 ms	4.5 ms	no

So on that card it is for 1080p and below, and native 4K needs a high-end RTX. Render ahead
cannot rescue it: it hides latency, not a pass longer than a frame. Watch skipped and the
sync offset in the statistics box.

Fixes

• No tooltip ever appeared where comctl32 v6 was not active for the host process:
  TTM_ADDTOOL was handed a structure size it refuses outright, and refuses in silence.
• Ticking DLSS 5 NR could untick itself a moment later: the half-second refresh compared the
  renderer against the page's own copy, so a tick not yet applied looked like the toggle key
  turning it off.
• The Apply button no longer lights while the page is filling itself in.

x64 and Win32, zero warnings.