madVR - high quality video renderer (GPU assisted)

[huhn]

they all have time bombs.

[spectmajor]

Can someone explain what is the issue with HAGS and how to reproduce it? I never disabled it, but I don't see any issue with it.

[strumf666]

Me neither, I don't think it affects all users.

[huhn]

the reported frame rate and composition rate changes after roughly 10-30 mins of playback.

i'm not affected it is usually reported with 23p mode which i do not use i use 119p.

[pirlouy]

It has been mentionned here by... myself, but also in this thread.
Except that I had it with a Radeon card, not nVidia, and madshi reported it to nVidia and not AMD (from what I read). And I noticed it only in 23p mode, because 90% of what I watch is 23,976 Hz so I use 23,976 Hz only.

[Sunspark]

Finally got around to opening up the NUC to replace the fan and thermal compounds. One thing that surprised me, there was a thick dust mat between the blower and the heatsink fins, effectively shutting off airflow. No wonder. It wasn't visible from the outside.

Now that everything's replaced, instead of bouncing off 105C, turning on a bunch of the stronger algorithms only put it up to 75C.. that's a 30C degree difference in temperatures under load, wow and that's with the fan at 3800rpm instead of 8000+. Usually around 3300rpm now.

[purplebaby]

I can't get HDR mode to enable when I play a hdr file on my LG CX (connected to PC via HDMI from RTX 5090 FE). Latest madvr version. Windows 11 LTSC. The video is displayed with SDR tonemapped colors. The TV doesn't switch to HDR mode.

I've set the hdr mode to 'pass through hdr to display' and 'send hdr metadata' on.

[flossy_cake]

Originally Posted by purplebaby

I can't get HDR mode to enable when I play a hdr file on my LG CX (connected to PC via HDMI from RTX 5090 FE). Latest madvr version. Windows 11 LTSC. The video is displayed with SDR tonemapped colors. The TV doesn't switch to HDR mode.

I've set the hdr mode to 'pass through hdr to display' and 'send hdr metadata' on.

I kind of had that issue on my Windows 10 22H2 system with my 3060 outputting 4k120 RGB HDR over HDMI to my Samsung S90D

Firstly directX 9 doesn't support HDR at all so you will need to use DX11 in madvr settings

Secondly i was having an issue where even in Dx11 mode it would randomly not switch to HDR when in windowed mode but would reliably switch when going fullscreen exclusive, so try full screen exclusive

Lastly right click the media player executable and "disable fullscreen optimisations"

But there is some issue with madvr not setting HDR mode in quite the orthodox way or something like that, try asking AI to give more details there could be something else i forgot

[huhn]

yes ask the ai...

madVR tries to use the AMD and nvidia HDR api. and there is nothing wrong with that. a very old one in the AMD case amd_ags_x64.dll from 23 03 2017 5.0.6.0.

the alternative is to change the windows from SDR to HDR which Microsoft doesn't want you to do. so do it as mircosoft wants you to do it manual.

[purplebaby]

I had to remove the display (TV) profile, reinstall madvr, and then have mpc-hc/madvr's first exposure to HDR content be with only my TV connected, so that this became the primary display.

Now HDR works on the TV.

But now I can't get it to NOT use HDR mode on my monitor (which isn't suited for HDR)...

So it's either all SDR or all HDR. Lol.

[huhn]

install the newest GPU driver over the current install if it comes from windows update it may not have all features shipped like the nvidia HDR api which would explain this.

[purplebaby]

Originally Posted by huhn

install the newest GPU driver over the current install if it comes from windows update it may not have all features shipped like the nvidia HDR api which would explain this.

I installed 591.74 as soon as I set up this PC.

[flossy_cake]

Originally Posted by purplebaby

But now I can't get it to NOT use HDR mode on my monitor (which isn't suited for HDR)...

So it's either all SDR or all HDR. Lol.

Windows has it's own toggle setting for HDR mode ("Windows HD Color Settings") so ensure that is turned off as well

Also remember to set your HDMI output to 10-bit in the GPU control panel. Actually now I remember: setting the output to to 8-bit caused the HDR to not flake out in windowed mode. So that affects it too, so that's another knob you can try twiddling to sidestep the bugs. Eventually you will find the magical combination of settings that allows it to work lol

[huhn]

the nvidia api only care if HDR is technically possible nothing else bit deep or what ever does not matter it isn't amd.

go to the windows folder usually on C and search for nvapi64.dll
if it is missing created a restore point.
https://drive.google.com/file/d/1Drl...ew?usp=sharing
do what you must.

[Sunspark]

I won't be able to test again until later tonight because it's too bright in here, but I'm starting to think that downscaling may have issues.

I have multiple players and setups because it's interesting to compare.

I observed last night that on BE with the EVR-CP renderer using bicubic -0.6 and floating point I had great sharpness downscaling and good black levels/rich colour depth. With HC using madVR the blacks were lighter and the image was blurrier. So now I need to begin a series of testing.. switch to software decoding to see what changes with blacks/colours and then check again with all AR and LL turned off, and then again with both chroma and luma on bicubic 60 to see if it can match the clarity of the shader that EVR-CP is using.

Almost all testing most do has been with upscaling. I suppose nowadays there might be more downscaling again because of 4K videos being downscaled to 1080p. In this case I am downscaling 1080p to 768p.

[huhn]

fhere are two parameter in bicubic -0.6 and 60 mean the same but the second is usually not mention and madVR uses something there.

[Sunspark]

So I looked at the code.. strange.. the values are not apples to apples.. https://github.com/Aleksoid1978/MPC-...ic_base_x.hlsl

I'm having trouble mapping these out. different AIs helping me with the math here keep giving me different values for -0.6, -0.8 and -1.0 when trying to convert it into B and C.

[Sunspark]

Woke up from a nap last night and went to watch a show and everything looked like it was moving faster than I expected and "glassy". Still the same in the morning. Wondered if I had smooth motion on, but no. Playback speed was 1.0 and display is 60.015 Hz. What changed was that I was experimenting with D3D11 Native paired with D3D9 overlay using a 24 fps (not 23.976) source so the timings must have been really good. Changing it to copy-back and windowed mode made it look more like what I am used to.

Turning smooth motion on makes it even more glassy like ice skating. You guys like that? Why?

[huhn]

your screen is at 60 HZ meaning it is doing 3:2 that is massive stutter and not the creators intent.

SM will show something very very similar to framerate matching with 24p in that case while still been at 60 hz.

what ever you mean with glassy i do not know. if you forced SM at 24 with 24p in you did something horrible right now.
if your device does any type of motion trash the result with SM will be terrible.
with SM 120 or more is highly recommended.

why would copyback or native have anything todo with that?

[Sunspark]

By glassy I mean it seemed like it had more frames than it should had have, or interpolated ones or something. AI said I am just not used to something that skips some abstraction layers like DWM which affects timing. I don't have perfect optical processing speed though so I'll put this aside for now.

So, now I'm contemplating which is the better choice for this TV.

With a 1:1 pixel mapping for the desktop, I am locked at either 60.015 Hz (disp/comp) or 59.91327/59.955 (disk/comp, slight mismatch) and locked to YCbCr 4:4:4 (no RGB, colour will distort--no idea why). Downscaling is done in software from 1920x1080 to 1360x768. madvr smooth motion is needed due to 3:2 pulldown. For whatever reason, it won't let me create a custom resolution of a lower refresh rate.

The TV however does accept 23.976, 24 and 25 CEA-861 signals, with a catch.. they're at a signal resolution of 1920x1080 which is not the native panel resolution. It does however in that situation accept both YCbCr and RGB without colour distortion (I suspect it still prefers YCbCr). Downscaling is done in hardware from 1920x1080 to 1366x768 ("Native" but not 1:1 so the chroma 4:4:4 test pattern breaks) using an unknown algorithm. madvr smooth motion does not appear to be needed.

Looking at the mainboard, it has a Zoran ZR39748 SupraHD chip that does everything, no separate scaler chip. Scaling is a polyphase FIR scaler which puts it between bicubic and lanczos in quality, so I guess that's good enough for luma scaling.

So I guess I have my answer there.. use the desktop at the lower 1:1 resolution and have madvr auto-switch to 1920x1080 and have the tv scale to panel and hopefully the refresh rate is true.. it doesn't seem to be stuttering. Advantage is not making the PC have the system load of both smooth motion and luma scaling. Flexibility to play with the added load of super-xbr if I want to.

Tip: If your TV is 2-prong power, get your multimeter out and identify continuity points between it and the PC. Then add a grounding wire to it. I did. It helped a lot with the static charge buildup, but still charges me up.. not as bad as before I added the ground wire though. Wire needs to be added to the TV. PCs have too many insulated standoffs and anodized paint on casing won't conduct properly whereas this unit has continuity between 2 of the 4 VESA screws, 1 of the case screws and all the ports. Boy, do I hate 2-prong devices. So lazy and cheap to not have them be grounded from the start.