madVR - high quality video renderer (GPU assisted)

[SirMaster]

Originally Posted by Siso

The screenshot I posted is the setting I'm using. Thanks for your feedback.

Ah, screenshot didn't come through on the forum for me.

Best to use external image host on this forum just FYI.

[Siso]

Originally Posted by SirMaster

Ah, screenshot didn't come through on the forum for me.

Best to use external image host on this forum just FYI.

It is uploaded on ext image site.

[Selur]

@huhn: Thanks for clearing that up.

[Megalith]

HDR no longer works on my system, and I have no idea why. Starting a video puts my TV into HDR mode, but the image is washed out in both windowed and full-screen modes (normally, it would only be washed out in windowed mode). Windows 10, GeForce RTX 3080 Ti, latest NVIDIA driver.

EDIT: A restart fixed it.

[x7007]

NV HDR doesn't work properly with Potplayer with 526.47 Windows 11 22H2??? I am using 4090 and I just noticed the NV HDR is not different than SDR and nothing in MADVR is working, changing from 0-255 to 16-235 or anything in the normal menu,, what is going on??? how can I fix this? only the OS HDR is working

Originally Posted by Megalith

HDR no longer works on my system, and I have no idea why. Starting a video puts my TV into HDR mode, but the image is washed out in both windowed and full-screen modes (normally, it would only be washed out in windowed mode). Windows 10, GeForce RTX 3080 Ti, latest NVIDIA driver.

EDIT: A restart fixed it.

Lol,, same, restart works...

[huhn]

there is a major known and supposed to be fixed issue with madVR and win 11h2 the fix is in beta 164 or 165 give this a try.

the issue is related to the duplication of device ids where it is possible that a device will not response to anything changes in that device id pretty much breaking madVR.

the problem is the driver shouldn't matter and i mostly tested this on AMD.

[OpenSource Ghost]

I am not sure if this is MPC-HC or madVR issue and as such I am asking in both threads.

MPC-HC keep trying to use network connection for video files when madVR is used as external filter. Why? Local Network in madVR tray is disabled. I don't use any MPC-HC plugins that require local or public network use. MPC-HC requests network access only when I launch video files to rendered with madVR, but never when I launch audio files, regardless of renderer. If I launch video files when madVR is not default preferred external renderer, then there are no attempts to use local network.

My PC is highly isolated and doesn't even have local network sharing capabilities, only WAN access over VPN. On top of that I disable private and public network use of MPC-HC executable with basic Windows firewall, but such blocking causes a delay when I launch MPC-HC because MPC-HC attempts to use network when madVR is the set primary external video renderer. If I just disconnect PC from LAN, then there is no delay.

Is there a way to fully disable network functionality of MPC-HC and madVR through their options? Again, network access requests only happen if I tr yto launch video files in MPC-HC when madVR is the default prefered renderer.

[mclingo]

Is it something to do with the licence maybe, are you using a pre licence version? v0.92.17 with no madvmeasure addons

[clsid]

MadVR does local network discovery when its tray icon is enabled. Disabling that in its tray icon right-click menu should stop it.

[shaolin95]

Hi all!
So I using Nvidia 23fps which windows shows as 23.976.
In about 1 hour and 20 minutes of playing Hobbit Part 2, I got 3 dropped frames and 1 repeated. Is this acceptable or is there anything I can do to prevent any drops?
I mean,. this is a 5600x with RTX 3070 dedicated to HTPC only.
Projector is a JVC RS540
Thanks

[flossy_cake]

Originally Posted by shaolin95

Hi all!
So I using Nvidia 23fps which windows shows as 23.976.
In about 1 hour and 20 minutes of playing Hobbit Part 2, I got 3 dropped frames and 1 repeated. Is this acceptable or is there anything I can do to prevent any drops?

What does Ctrl+J say for "1 frame drop every..."

You can fine tune the refresh rate with CRU to make it say "1 frame drop every <many> hours" but it's convoluted and difficult, requires using calculator and adding/removing blanking since we only get 2 decimal places of precision for the pixel clock which isn't enough.

Also are you at 1080p23 or 2160p23? If the latter then due to the the large pixel count, 2 decimal places of pixel clock precision may be sufficient for making a quick 1-click adjustment in CRU.

[shaolin95]

Originally Posted by flossy_cake

What does Ctrl+J say for "1 frame drop every..."

You can fine tune the refresh rate with CRU to make it say "1 frame drop every <many> hours" but it's convoluted and difficult, requires using calculator and adding/removing blanking since we only get 2 decimal places of precision for the pixel clock which isn't enough.

Also are you at 1080p23 or 2160p23? If the latter then due to the the large pixel count, 2 decimal places of pixel clock precision may be sufficient for making a quick 1-click adjustment in CRU.

2160p23 . The time for 1 frame drop changes but usually 50mins to over an 1 hour is what it shows.
I c was able to get great results with jriver and its built in vidoeclock BUT that means no Atmos so useless to me :/
Guess is not a big deal just ocd lol

[flossy_cake]

Originally Posted by shaolin95

2160p23 . The time for 1 frame drop changes but usually 50mins to over an 1 hour is what it shows.

1 per hour isnt too bad. You'll have to watch a few movies and see if you notice it once or twice. If the camera is not moving very much at that point in the movie, it won't even be visible at all.

With my 1080p23 mode I initially had 1 skip in 15 minutes and I was noticing that unfortunately. I wasn't trying to notice it, it just kept presenting itself to me. At first I couldn't get CRU to register my custom mode in Windows list of display modes, but that was due to it clashing with another 24hz mode defined elsewhere in CRU (in the CTA block, it turned out). Once I deleted that mode and created my custom mode in another separate block in CRU, it worked.

NVCP also has its own custom res utility and I did manage to get it to work but it was so buggy and awful. CRU is better imo as it just modifies the EDID stored in the Windows Registry, but it seems the Nvidia driver is the bit of code which actually reads it and uses it to register the new modes in Windows list of display modes. MadVR "sees" whatever is in the list of Windows own display modes list. Also I love the fact that I can backup the EDID with 1 click in CRU so I don't have to remake all my modes if I do a driver update or something.

[shaolin95]

Originally Posted by flossy_cake

1 per hour isnt too bad. You'll have to watch a few movies and see if you notice it once or twice. If the camera is not moving very much at that point in the movie, it won't even be visible at all.

With my 1080p23 mode I initially had 1 skip in 15 minutes and I was noticing that unfortunately. I wasn't trying to notice it, it just kept presenting itself to me. At first I couldn't get CRU to register my custom mode in Windows list of display modes, but that was due to it clashing with another 24hz mode defined elsewhere in CRU (in the CTA block, it turned out). Once I deleted that mode and created my custom mode in another separate block in CRU, it worked.

NVCP also has its own custom res utility and I did manage to get it to work but it was so buggy and awful. CRU is better imo as it just modifies the EDID stored in the Windows Registry, but it seems the Nvidia driver is the bit of code which actually reads it and uses it to register the new modes in Windows list of display modes. MadVR "sees" whatever is in the list of Windows own display modes list. Also I love the fact that I can backup the EDID with 1 click in CRU so I don't have to remake all my modes if I do a driver update or something.

So do you get 0 drops now?
Thanks!

[flossy_cake]

Originally Posted by shaolin95

So do you get 0 drops now?

Not quite -- about 1 drop per 12 hours, which for me is good enough. It even fluctuates a bit depending on ambient temperature.

So let's say you're targeting 23.976hz (24/1.001 to be precise, and precision is important here) and your actual refresh is 23.977hz, the error is 0.001hz which would theoretically give you 1 repeat every 16 minutes (1/0.001/60=16).

Error     = Frame drop every
0.001hz   = 16 minutes
0.0001hz  = 2.7 hours
0.00001hz = 27 hours

For 1 drop per 12 hours I had to get it within around 0.00002hz.

[shaolin95]

Originally Posted by flossy_cake

Not quite -- about 1 drop per 12 hours, which for me is good enough. It even fluctuates a bit depending on ambient temperature.

So let's say you're targeting 23.976hz (24/1.001 to be precise, and precision is important here) and your actual refresh is 23.977hz, the error is 0.001hz which would theoretically give you 1 repeat every 16 minutes (1/0.001/60=16).

Error     = Frame drop every
0.001hz   = 16 minutes
0.0001hz  = 2.7 hours
0.00001hz = 27 hours

For 1 drop per 12 hours I had to get it within around 0.00002hz.

So in the nvcp you set it to anything specific before adding the cru one?
Where do you get the timings from?
Maybe I can PM you to not of off topic?
Thank you!!

[Klaus1189]

You can go on here if you want:
AMD, Intel and Nvidia driver issues and last recommended version

A guide for it would be nice to have.

[flossy_cake]

Originally Posted by shaolin95

So in the nvcp you set it to anything specific before adding the cru one?

I avoid setting refresh rate in NVCP as it seems to have issues distinguishing 23 vs 24, and 59 vs 60, when making custom modes with CRU.

Originally Posted by shaolin95

Where do you get the timings from?

Well, the situation is a bit tricky. In CRU we can select "automatic HDTV" and this will choose timings CRU thinks is standard:



But it is different to what CTA specifies:



Note the bit highlighted in red which says that 23.976hz mode will be the same as 24.0hz mode but with pixel clock reduced slightly to produce 23.976hz.

So I start by plugging CTA's timings into CRU:



I'm not sure why CRU highlights front porch in red. It is a weirdly high value but hey that's what CTA says it should be. (edit: it seems the mode must be added to a new "display id 1.3/2.0" extension block, in which the value won't be red and CRU will even automatically select CTA timings when selecting "automatic HDTV").

Now lower the pixel clock until resulting refresh rate is 23.976:



Now we are ready to make some very small changes to the refresh rate to minimise the "1 frame drop/repeat every..." on MadVR's ctrl+J. Drop = refresh rate is slightly too slow, repeat = slightly too fast.

The problem is we don't have enough decimal places of precision to elicit less than a 0.001hz in the refresh rate. You might get lucky and a 0.001hz nudge might get you to a satisfactory value on ctrl+J. But for higher precision we can instead change the number of pixels in the blanking zones which has a very tiny effect on the refresh rate. To calculate the amount I'm using this calculator: https://www.monitortests.com/pixelcl...&maxpclock=165:



Note how I've already prefilled everything there -- the blanking values I've set to +/- 10% of the CTA spec. This should give us enough adjustability without straying too far from the spec.

Now suppose you want to increase the refresh rate by 0.00001hz, change it from 23.976023 to 23.976033, click calculate, then pick one of the resulting modes and copy their total resolution into CRU:



And remember: in CRU you may need to remove all other 24hz modes to avoid clashes, and create your new custom mode in a separate block. Otherwise it didn't work for me and the refresh rate didn't change -- this can be checked with Ctrl+J or vsynctester.com.

Good luck.

[Alexkral]

I just noticed that the results of custom pixel shaders are stored in a 16-bit buffer in beta versions, and the 32-bit option has disappeared from the "trade quality for performance" menu.

I can't understand what relationship it can have with the tone mapping development.

[chros]

Aks him on avs, Alex! I think we reached.the new low with madvr "development": he doesn't even want to fix obvious bugs that he introduced, let alone lack of manual/unit tests.

@flossy_cake: you can check out this post about CRU.