emoose

Have you tried the rtx-1.2 build at https://github.com/emoose/VideoRenderer/issues/5#issuecomment-1452590217 ? That seems to help some others with HDR issues, maybe can help with this too.

E: (in the slim chance any NV engineers might see this after my report, the initial build found at https://github.com/emoose/VideoRenderer/releases/tag/rtx-1.0 should display the issue, or to build from source use...

> You can disable P010 output in LAV Video Decoder. You also need to change hardware decoder from Native to Copyback. Aha looks like that did the trick, video that...

Hm not noticing much with HDR videos, GPU usage stays flat with them, couldn't notice any difference toggling it neither, maybe they disable those in browsers somehow. >Additionally, you can...

@clsid2 added your suggestions in https://github.com/emoose/VideoRenderer/commit/4e2e1605b903f1886d1c77922d1f4b66d3368be2 - seemed VSR was still working on some interlaced clips I tested though so removed the interlaced check. Made it only check for P010/P016...

Oh good idea, with YUY2 it still requests VSR but doesn't look like it's active, low power draw & no difference toggling in NVCP. RGB32 didn't seem to request it,...

>Your release notes mentioned that dithering should be disabled. Is that really true? Any idea why this breaks VSR? You might have used 10-bit video when testing this. I noticed...

Not having much luck with ffdshow using rev4533 it seems, added the "ffdshow raw video filter" as preferred external filter and enabled resizing in the ffdshow config, tested at 640x480...

Maybe it's `NV12`, noticed it wasn't listed in the filters media types for ffdshow, if I change LAV to use `YUY2` that does let it take effect & shows in...

Aha nice looks like it's working now, ty! Now to see what sizes it works with. E: 720x1280, 1080x1920, 1440x2560 have noticeable quality difference with SuperRes toggled (using `No aspect...