madVR - high quality video renderer (GPU assisted)

[Zaoshi]

On a properly calibrated screen and playback chain, you should not see values above 235 or below 16.

In that case my colors are displayed correctly, but why is that?
Shouldn't 235 appear as 235, not 255? If video is going to have colors in ranges 0-16 and 235-255 they'll just get thrown away.
If I use EVR and set LAV to output 16-235 then I can actually see the whole range and color values match the number (which implies video does have those colors, but as seen in the picture those colors just disappear). Shouldn't this be the correct way?

[Damie]

This line only informs you of the actual used colorspace inside the stream.

Thank you! So it's the same as "Mastering display color primaries " shown by Mediainfo.

As my TV shows 96% of DCI P3 uv gamut, and only 72% of BT.2020 uv gamut, and because the source is DCI P3, I'll be selecting the latter in the TV menu.

Selecting BT.2020 in TV menu would result in oversaturation, yes? But if my TV could reproduce 100% of BT.2020 gamut, there would be no oversaturation, right?

[iSeries]

are you running out of Vram? check the advanced rendersteps part and see if you get spikes in finalstep.

Yep, out of vram. 2gb not enough I guess

[nevcairiel]

In that case my colors are displayed correctly, but why is that?
Shouldn't 235 appear as 235, not 255? If video is going to have colors in ranges 0-16 and 235-255 they'll just get thrown away.
If I use EVR and set LAV to output 16-235 then I can actually see the whole range and color values match the number (which implies video does have those colors, but as seen in the picture those colors just disappear). Shouldn't this be the correct way?

These test videos are specifically designed to include data that should not usually be visible, so that you can actually detect problems with that - ie. if you do see it, you know that its wrong.

[Asmodian]

To expand on what nevcairiel said, the test video is flagged as limited range but contains full range information to expose incorrect playback chains.

[johnnylaiyee]

Yep, out of vram. 2gb not enough I guess
By setting to 4 present queue ，my 1050 2gb can play a whole 1080p upscaling to 4k without any issue

Sent from my LG-H860 using Tapatalk

[sauma144]

By setting to 4 present queue, my 1050 2gb can play a whole 1080p upscaling to 4k without any issue.

What upscaler do you use?

[iSeries]

By setting to 4 present queue ，my 1050 2gb can play a whole 1080p upscaling to 4k without any issue

Sent from my LG-H860 using Tapatalk

Upscaling 1080p to 4k is no problem (i often crop black bars and zoom to fill the screen, using ngu doubling for upscaling). 4k hdr downscaled to 1080p is what my card is struggling with.

[johnnylaiyee]

What upscaler do you use?
Luma ngu sharp high
Chroma superxbr 150

Sent from my LG-H860 using Tapatalk

[pankov]

Hello fellow madVR users,
last week I got the chance to test my first 4K TV with HDR support (LG OLED65E6) and I was very impressed with the "punch" of the HDR picture and the OLED picture in general. I was using a few HDR demos and one of them had some external subtitles (.srt) with comments which I decided to try and I think I stumbled on an major downside of using external text subs with HDR videos with current subtitle renderers and/or madVR.
Here is the issue:
Since madVR is smart enough to turn on the HDR mode on the TV and get specular highlights in 1000+ nits (well ~500 nits on this OLED TV) while maintaining the rest of the picture at lower levels ... or even much lower in dark scenes ... the rendered subtitles (which by default are "white" - RGB 255,255,255) are blindingly bright and they have much greater area than a specular highlight and are almost hurting the eyes. This got me thinking if the way madVR and XySubFilter that I use are actually rendering the subtitles is correct. On one side XySubFilter doesn't know if the subs are rendered over an HDR or SDR video ... I think ... and the preference for font color it uses is always the same ... which makes me believe that it's madVR's job to lower the brightness of the color/white in some way (f.e. 255,255,255 = 100 nits as per SDR spec) but on the other side if there is some color/brightness information in the SRT file (I'm not 100% sure if it's possible but with other external subtitles formats it is AFAIK) how should madVR react?

So I'll be glad to hear your thoughts on the subject.
I don't have access to UHD Blu-Ray player and real movies so I'm wondering how these things designed in the real/official format.
Can you someone with access to such content share a few pictures with us? For example one picture from a dark scene with subs and a different one from a very bright scene again with subs on screen.

[sauma144]

I don't know if this can be useful for madVR.

But it seems it's possible to detect HDR support of any displays with Windows.
https://github.com/Microsoft/DirectX-Graphics-Samples/blob/master/Samples/Desktop/D3D12HDR/src/D3D12HDR.cpp#L904

Hope it's not only for latest Win10 release and/or D3D12.

[nevcairiel]

But it seems it's possible to detect HDR support of any displays with Windows.
https://github.com/Microsoft/DirectX-Graphics-Samples/blob/master/Samples/Desktop/D3D12HDR/src/D3D12HDR.cpp#L904

Hope it's not only for latest Win10 release and/or D3D12.

These functions require Windows 10, however it does not require D3D12 to be used.

[Zaoshi]

How can I improve seek times? With EVR seeking is completely instant - when I press Left / Right Arrow it seeks instantly and plays instantly, almost as if there was no seek, but with madVR it takes up to a few seconds to start playing after seek - audio plays but video is frozen on a frame before seek.

[e-t172]

Reducing queue sizes (especially "frames to present in advance") should have a positive effect on seek responsiveness. Don't set them too low though, otherwise you might increase the likelihood of frame drops.

[mzso]

How can I improve seek times? With EVR seeking is completely instant - when I press Left / Right Arrow it seeks instantly and plays instantly, almost as if there was no seek, but with madVR it takes up to a few seconds to start playing after seek - audio plays but video is frozen on a frame before seek.

Hi!

You could check whether the "delay playback start after seeking too" or it's parent is unchecked in the general settings section. Otherwise you'll certainly get slower seek times.

[Zaoshi]

Reducing queue sizes (especially "frames to present in advance") should have a positive effect on seek responsiveness. Don't set them too low though, otherwise you might increase the likelihood of frame drops.

Tried setting CPU, GPU, and Present queues to minimum but it had only minimal effect.

Hi!

You could check whether the "delay playback start after seeking too" or it's parent is unchecked in the general settings section. Otherwise you'll certainly get slower seek times.

It's not turned on, but turning it on when queues are set to minimal actually makes it work better than without delay.
To be honest, it's better even with maxed out queues.


Edit:
I just tried madVR 0.90 and it doesn't have this issue with same settings. Actually, it's nearly as fast as EVR.

[austonrush]

How can I improve seek times? With EVR seeking is completely instant - when I press Left / Right Arrow it seeks instantly and plays instantly, almost as if there was no seek, but with madVR it takes up to a few seconds to start playing after seek - audio plays but video is frozen on a frame before seek.

I just had this issue, took me a couple days to resolve, the problem was related to windows creator update. It left the install files and recovery files on my hdd. Limiting my remaining hdd space down to 20gb. I ran disk cleanup and removed all the recovery files/ install files and junk. Once done madvr went back to normal performance. The strange part was no other programs seemed to be affected.

Make your queue sizes 8 for gpu and 12 for cpu and leave them there. I normally set my my 'frames to present in advance' at 8.

[ryrynz]

Tried setting CPU, GPU, and Present queues to minimum but it had only minimal effect.


Have you tried resetting to defaults via the batch file? Might want to back up first..

[Zaoshi]

Have you tried resetting to defaults via the batch file? Might want to back up first..

Just tried this. All issues have disappeared so I did some poking. This problem seems to arise only when I'm using NGU. Even when I set NNEDI3 to 256 neurons (100 ms frame time) it still seeks faster than NGU (30 ms).
Also, this seems to occur only when video is playing. If I pause and start seeking it's instant.

[hannes69]

Also, this seems to occur only when video is playing. If I pause and start seeking it's instant.
Maybe it´s a better strategy to spend more time watching videos than seeking something within them ;) I don´t quite understand why here and there often comes up the topic of perfect performant seeking. What the heck is permanently to be sought in videos? Start a movie, lean back and enjoy :)

[johnnylaiyee]

Maybe it´s a better strategy to spend more time watching videos than seeking something within them ;) I don´t quite understand why here and there often comes up the topic of perfect performant seeking. What the heck is permanently to be sought in videos? Start a movie, lean back and enjoy :)
Porn maybe?

Sent from my LG-H860 using Tapatalk

[XMonarchY]

If I have Chroma Upscaling set to NGU - AA Very High Q + SuperRes, then should I also enable Anti-Ringing for Upscaling Refinement for the best quality with SuperRes? Linear Light too?

I noticed Chroma Upscaling with NGU AA Very High Q + SuperRes does not allow Anti-Ringing, so it got me confused...

[QBhd]

I thought that the consensus was SuperRes and NGU was less than ideal

QB

[AngelGraves13]

Nvidia's private API for HDR will no longer work with the Creator's Update and has been abandoned according to Nvidia Rep in their forums. The Fall Creator's Update will better support HDR.

[mzso]

Maybe it´s a better strategy to spend more time watching videos than seeking something within them ;) I don´t quite understand why here and there often comes up the topic of perfect performant seeking. What the heck is permanently to be sought in videos? Start a movie, lean back and enjoy :)

Good for you for understanding every mumbled sentence, and never being disturbed while watching a movie, and for always having the time to watch all arbitrarily long videos for the bit of stuff you're interested in partway through it.

Why don't we just use a single keyframe and then only encode reference frames?

[ryrynz]

should I also enable Anti-Ringing for Upscaling Refinement for the best quality...

I keep telling you to decide these things for yourself.

[hannes69]

Good for you for understanding every mumbled sentence, and never being disturbed while watching a movie, and for always having the time to watch all arbitrarily long videos for the bit of stuff you're interested in partway through it.
I watch movies in my home cinema and like the name of this institution suggests I use it like a cinema: The movie is started and then the audience watches the movie till the end. Maybe the movie will get paused when going to the restroom or when getting some beer etc (most of the time not by me, I don´t like interruptions). But seeking is indeed never really needed in my case.
Of course I understand that needs are different. But I think that seek performance is a) not highest priority in a playback chain (video quality e.g. is way more important in my opinion) and b) the given seek performance should be sufficient for everybody. When not having the time to wait 1 sec maybe it´s time to think about stress syndromes ;) ;)

[mzso]

When not having the time to wait 1 sec maybe it´s time to think about stress syndromes ;) ;)

It's really annoying if you seek a lot. eg: when you skim a movie that you already watched.

I myself seek a lot because I often loose focus, or just don't understand what they say in english.

[XTrojan]

So I have 1080p blu-ray rips and a 1080 Ti, I'm settled on NGU, but unsure which NGU to use, very high "sharp" feels way to aliased.

I'm also unsure if I should activate "debanding" since it kinda just seems to add a filter.

[ryrynz]

So I have 1080p blu-ray rips and a 1080 Ti, I'm settled on NGU, but unsure which NGU to use, very high "sharp" feels way to aliased.


Sounds to me like you should turn your screen sharpness down.

[galneon]

I watch movies in my home cinema and like the name of this institution suggests I use it like a cinema: The movie is started and then the audience watches the movie till the end. Maybe the movie will get paused when going to the restroom or when getting some beer etc (most of the time not by me, I don´t like interruptions). But seeking is indeed never really needed in my case.
Of course I understand that needs are different. But I think that seek performance is a) not highest priority in a playback chain (video quality e.g. is way more important in my opinion) and b) the given seek performance should be sufficient for everybody. When not having the time to wait 1 sec maybe it´s time to think about stress syndromes ;) ;)

What I don't understand is people who waste time criticizing the viewing priorities of others, even going so far as to suggest psychological issues, instead of spending their free time watching films in their pretense-laden 'home cinemas'.

[Rick164]

Noticed that madVR GUI didn't have a settings import/export option and even after some google-fu couldn't find any examples that archived this so decided to create 2 simple batch scripts

// Creates settings.reg for automated or manual restore
backup_settings.bat (https://gist.github.com/RickDB/c24b73e1809444b61f38b8ffda3e5304)

// Restores from settings.reg file and clears any current settings
restore_settings.bat (https://gist.github.com/RickDB/a0289245a81b33d39215d4bacf5ae973)

[Q-the-STORM]

Noticed that madVR GUI didn't have a settings import/export option and even after some google-fu couldn't find any examples that archived this so decided to create 2 simple batch scripts
Shouldn't it be enough just to copy the settings.bin?

[Rick164]

Shouldn't it be enough just to copy the settings.bin?

It never creates one here, thought that settings.bin export was something the user could do manually but didn't find examples :)
Best guess is that it's a rights restriction as typically you would need to run as admin before anything can write in program files (at least with UAC enabled), the registry exports just works from anywhere and automated that here with daily task so I can always rollback.

[XMonarchY]

I keep telling you to decide these things for yourself.

Is there a set of example images that can be used to make a comparison? I can't even figure out how to take a screenshot of madVR-rendered content in Exclusive FullScreen Mode...

I often can't see any difference, even zoomed in. I just go by what general thread population suggests as overall highest-quality setting for non-anime film content.

[Asmodian]

It never creates one here, thought that settings.bin export was something the user could do manually but didn't find examples :)
Best guess is that it's a rights restriction as typically you would need to run as admin before anything can write in program files (at least with UAC enabled), the registry exports just works from anywhere and automated that here with daily task so I can always rollback.

Install madVR to a directory outside of Program Files (or you can change the permissions of madVR's directory in Program Files).

But thanks for creating the batch files too. :thanks:

[madshi]

, please make downscaling after doubling use strict AR in NGU AA & super-xbr. And add the hotkey to display configuration dialog. Why it's taking so long to do these simple things?
It's taking so long because my day only has 24 hours, and because I have to spend some of my time on earning money, too. Strict AR for NGU AA + super-xbr will be in the next build. The hotkey will have to wait.

@madshi, I don't know whether this is just an aesthetic glitch, or whether this is specific to my system, but I've noticed that my queues periodically seem to empty for a moment. I don't know if this is because of a latency spike or what, and it usually doesn't seem to cause a dropped frame, but I think it does sometimes when it gets unlucky with the render time. I've noticed that by significantly lowering my settings (bringing the processing down to ~5ms below my frame budget) I can sometimes get it to stop, but it doesn't seem consistent. Maybe it's related to memory usage on the GPU? I'm using the D3D11 path, and enabling "present a frame for every VSync" or "use a separate device for presentation" doesn't change it.

Edit: The reason I ask is that I've noticed the same thing on my laptop (GeForce GTX 1060 3G) and desktop (GeForce GTX 1080). I have Smooth Motion set to "only if there would be motion judder without it", but these 'glitches' don't seem to correspond directly with duplicated frames. Both devices are running Windows 10 with the Creators update, and the latest drivers (382.33), but I think this has been happening for a while now.
That's really hard to say. You don't have any tools like GPU-Z or F.lux running? You may have to experiment to find the cause. E.g. try without a 3dlut. Try a long m2ts movie without segments. Try with FSE mode turned on or off. Try with the new option "hack Direct3D to make 24.000Hz work" turned on or off. Try with a lower number of pre-presented frames. Etc...

Is there a reason why madVR doesn't/can't have a reclock feature like on MPDN or Kodi?
Is it because it can't affect audio?
Correct. madVR is not involved at all in anything audio related. Reclock works by resampling audio, so that's not something madVR can do. However, there will soon be a new feature that may make Reclock like algorithms not needed, anymore. We'll have to see if it works as intended, but that's my hope.

Hey do you know if a Splash Motion2 or SVP like feature is planned for madVR?
Not in the near future.

mpc-hc crash when playing mvc 3d with lavideo decoder, madvr on intel 4600 (with optimus)
"exception: acces violation"
crashin module:
igd10iumd32.dll
offset: 0x17cf088d, codebase: 0xc90000
thread 3992 tried to read memory at adress 0x8244491"
Try different GPU driver versions for both Nvidia and Intel. Also try disabling or enabling automatic fullscreen exclusive mode in madVR, or lowering the number of pre-presented frames to e.g. 3.

Guys I am confused and I need an opinion.After trying madvr's new option I can finally activate 23hz and results seem good(1 frame drop every 1 hour) but I lose 4:4:4.
What do you think it's the best choice?4:2:2 with 23hz and supposedly smoother motion or 60hz with smooth motion on and 4:4:4?
For video playback 4:4:4 is not terribly important. However, smooth motion works pretty well. So I can't really tell you which is better. I'd say compare both and trust your eyes.

Can someone please explain.
I have a ripped version of the BD Oklahoma which is 1080 29.970 frame rate.
Says who? What does eac3to say about this video?

Is there a way to modify any file in Kodi to report back "actual aspect ratio" from MadVR?

Today I have a plugin (Control4 Driver) that make API calls to Kodi VideoPlayer.VideoAspect and ListItem.VideoAspect.

I think the problem reside in Kodi not getting the info from MadVR. And most files I've tried have hard encoded blackbars hence 1.78 is reported. Maybe a trivial problem for most. But I still seek the answer. :)
I don't really understand what you mean/need. Which exactly is the problem you're having? madVR generally does report all the needed information, but whatever software you think should access this information must know how to get the information from madVR.

Madshi, with D3D11 I still get some frames presented from earlier in the video when I jump forward on my HD4000.
Was there at least an improvement? Or is it still as bad as it always was? FWIW, I was able to reproduce the problem on Kaby Lake and my changes worked around the problem for me. In any case, it's an Intel GPU driver bug.

Madshi can you please explain why the following does not work '1080p23, 2160p23' If I use that when the display is set to 2160, it cuts off a 1080p video and only shows half of the video on the display to the right and the left half is black. If I set the display to 1080 it shrinks the 2160p video to the top left corner (quarter) of the display and the rest of the display is black. Is there no way to fix this?
Can I see a screenshot of the OSD? Most probably it's a media player bug. It probably asks madVR to do weird zooming, for some reason.

Is there a way to turn off the "Exclusive/Windowed" message at the top left when switching between windowed/fullscreen?
Not yet. Planned for some future version.

another question:
i cant use mpc-hc "save image" with madvr (dxva2 copy-back decoding + dxva2 scaling).
the output of save image is discolored mostly white picture with barely visible silhouettes, and the size of mpc-hc window, not the frame size.
Screenshotting is currently just barebones feature. It works sometimes and sometimes not. I plan to totally revisit it at some point in the future.

Are there any known fixes for this issue? https://forum.redfox.bz/threads/windows-10-creators-update-messed-up-reclock.72475/

Basically the creator's update has resulted in the loss of normal playback using madvr with reclock, with repeated/dropped frames frequently where before it would not be an issue
I don't know. You could try to reinstall the GPU drivers, hoping for the best. My personal recommendation is to use Windows 8.1.

could you please add the current display ICC profile name to the madVR profile rules variables?
Currently I'm not doing anything ICC. What do you need this for?

is there any boolean value to apply a specific "profile" to hdr content with "undefined hdr"?

I created a profile with the boolean value "HDR". Problem is, I have some videos which doe have HDR but somehow with hdr flag resulting in this "HDR: undefined" instead of HDR: 4000 nits for example.
And in this case the HDR boolean value does not recognize the profile as being HDR.
You're saying the "HDR" profile variable isn't set for HDR content with unknown metadata? If so, that would be a bug!

Do you plan to add Enhanced EWA upscalers into madVR?
Are you sure there's anything new in there? It seems to be very old, much older than the EWA implementation in ImageMagick/madVR.

My LG TV has a PC-mode only on 59 or 60hz refreshrates, it drops to the full-processing mode with anything else (23,24,25,29,50 etc).
Hence I am asking if there is any real reason why I shouldn't use 60hz and smooth motion with madVR?
Is the blending algorithm worse than what TVs do? I doubt this 2010-year panel does REAL 24hz, but some sort of internal conversion to 60hz or close instead. It has the LGs "True Cinema" toggle in settings though, which apparently in new models means 72hz, but when doing a custom resolution with 72hz, it drops frames and is still 60hz really. Very confusing for sure. However even with all settings turned off in the LG, when it is not in PC-mode, the text is less sharp and clearly some processing still left, which I am trying to eliminate with the PC-mode in the first place.
The only person who could answer your question would be someone with *exactly* the same TV you have. So basically, you yourself are the best candidate to test this and come to your own conclusion... :)

I think, when I have "don't rerender frames when fade in/out is detected" option disabled, subtitles are flashing sometimes. Are there any workarounds for it?
That's a problem with the subtitle renderer. You could try a different subtitle renderer. Or, simply activate the "don't rerender frames" option. It's not a night-and-day difference option, so it's not all that dramatic to lose it.

I'm not sure if this has been answered. It seems I can't find it in this thread.

I'm having problem in PERMANENTLY setting the BRIGHTNESS to -15. Once I have changed it to -15 it just won't stick. It resets back to 0 once a new video is played.

Is there a way to permanently set it to -15?
Where exactly are you trying to set the brightness? If you change it in "color & gamma" in your madVR display settings, it's supposed to stick.

Is there a possibility for madvr to add crop functions like - crop to 1.85:1, or crop to 2.35:1, or crop to 2.39:1 or crop to 2.40:1?
What do you need this for? madVR already has automatic detection (and optionally removal) of black bars, which supports any possible aspect ratio, not just those you listed.

between lav settings of hw decoding: no hw decoding through dxva, which of them the "proper/right way" for madvr?
If your CPU/GPU can do it, I prefer software decoding, next best for me is DXVA copyback. If all else fails, you can use DXVA native.

last week I got the chance to test my first 4K TV with HDR support (LG OLED65E6)
Nice!

Since madVR is smart enough to turn on the HDR mode on the TV and get specular highlights in 1000+ nits (well ~500 nits on this OLED TV) while maintaining the rest of the picture at lower levels ... or even much lower in dark scenes ... the rendered subtitles (which by default are "white" - RGB 255,255,255) are blindingly bright and they have much greater area than a specular highlight and are almost hurting the eyes. This got me thinking if the way madVR and XySubFilter that I use are actually rendering the subtitles is correct. On one side XySubFilter doesn't know if the subs are rendered over an HDR or SDR video ... I think ... and the preference for font color it uses is always the same ... which makes me believe that it's madVR's job to lower the brightness of the color/white in some way (f.e. 255,255,255 = 100 nits as per SDR spec) but on the other side if there is some color/brightness information in the SRT file (I'm not 100% sure if it's possible but with other external subtitles formats it is AFAIK) how should madVR react?
Good question! Will have to add this to my to-do list. I suppose subtitles should probably never be brighter than 100 nits. So maybe I need to post process the subtitles to enforce them to not be too bright... :(

I don't know if this can be useful for madVR.

But it seems it's possible to detect HDR support of any displays with Windows.
https://github.com/Microsoft/DirectX-Graphics-Samples/blob/master/Samples/Desktop/D3D12HDR/src/D3D12HDR.cpp#L904
Thanks, was already aware of that, though.

Just tried this. All issues have disappeared so I did some poking. This problem seems to arise only when I'm using NGU. Even when I set NNEDI3 to 256 neurons (100 ms frame time) it still seeks faster than NGU (30 ms).
Strange stuff. Just tried to reproduce the problem here, but can't. Seeking is not any slower here with NGU compared to Catmull-Rom.

Nvidia's private API for HDR will no longer work with the Creator's Update and has been abandoned according to Nvidia Rep in their forums.
Actually, that's not true - fortunately! I've been in contact with the Nvidia developer who's responsible for Nvidia's private HDR API. He's aware of a bug in the current Nvidia drivers and plans to fix it soon.

Noticed that madVR GUI didn't have a settings import/export option and even after some google-fu couldn't find any examples that archived this so decided to create 2 simple batch scripts

// Creates settings.reg for automated or manual restore
backup_settings.bat (https://gist.github.com/RickDB/c24b73e1809444b61f38b8ffda3e5304)

// Restores from settings.reg file and clears any current settings
restore_settings.bat (https://gist.github.com/RickDB/a0289245a81b33d39215d4bacf5ae973)
Nice!

Shouldn't it be enough just to copy the settings.bin?
For export yes. For import no, because madVR checks both the settings.bin and the registry and uses the settings block with the higher revision number. However, you can run the "restore default settings.bat" and afterwards copy the settings.bin. That should do the trick for import.

It never creates one here, thought that settings.bin export was something the user could do manually but didn't find examples :)
The settings.bin file is automatically written, but only if madVR has write access to its own folder. This is supposed to help making madVR more portable.

hi madshi , The authors of SRCNN have published another paper about accelerating SRCNN(FSRCNN).now it can run in real-time performance :D:D
http://mmlab.ie.cuhk.edu.hk/projects/FSRCNN.html
FSRCNN is a big improvement over SRCNN. But it's still not as good as NGU, IMHO.

FSRCNN is a neural network which is trained to do only one very specific thing, namely reverting a Catmull-Rom downscale in such a way that you get the highest possible PSNR/SSIM numbers. Which means that FSRCNN produces very sharp and detailed results, but also has very noticeable ringing artifacts. Furthermore, it works best with images that were downscaled using Catmull-Rom. Any other images (while still looking fairly good) suffer in comparison.

I'm not sure exactly how fast FSRCNN is compared to NGU. My best guess is that the slower FSRCNN preset might be near to NGU Very High, and the faster FSRCNN preset might be near to NGU Medium. But this is just a guess.

If you're interested, I've uploaded some comparison images here:

http://madshi.net/FsrcnnVsNguSharp.zip

I'm pretty sure that FSRCNN achieves higher PSNR/SSIM numbers than NGU Sharp (haven't actually checked), but to my eyes NGU Sharp looks significantly better. NGU is slightly softer, but is much cleaner and consequently looks more natural to my eyes.

NGU is not optimized for PSNR/SSIM. Of course I could do that, and I could also reduce NGU to be just a Catrom-Downscale-Reverter instead of a general purpose upscaler. This way I would probably beat FSRCNN's PSNR/SSIM numbers. But my top priority is not to produce the highest PSNR/SSIM results, but to create the best looking images for the human eye. Which e.g. means that ringing artifacts should be avoided. I like sharpness like the next guy, but it shouldn't come at the cost of ringing.

[Rick164]

@Asmodian that explains it, just noticed your guide from the signature and thanks for that as it helped to clarify some things.

[igvk]

could you please add the current display ICC profile name to the madVR profile rules variables?
Currently I'm not doing anything ICC. What do you need this for?

The reason for this is simple - I would like to use different 3D LUTs for different ICC profiles.

This is because NEC MultiProfiler loads differently named profiles depending on built-in gamut modes of the monitor.
So, this is the only way for me to switch between different calibration modes in madVR automatically, depending on selected picture mode in MultiProfiler.

[madshi]

madVR v0.91.11 released

http://madshi.net/madVR.zip

* fixed: HDR metadata via Nvidia's private API was broken in 64bit
* added workaround for driver bug in Nvidia's private HDR API
* improved Windows 10 HDR metadata support
* D3D11 windowed mode now supports 10bit, if "HDR and Advanced Color" is on
* improved AMD native 10bit DXVA decoding; drivers are still broken, though
* downscaling after doubling now uses relaxed AR only for NGU Sharp + Standard
This is just a little bugfix release for improved HDR handling.

[madshi]

HDR metadata passthrough

In the last couple of days I've talked to Microsoft and NVidia about HDR metadata passthrough. And the current situation is as follows:

1) In Windows 10 Creator's Update there's a new option in the OS display settings dialog named "HDR and advanced color". If you turn this option off, your TV will always be running in SDR mode. If you turn this option on, your TV will always be running in HDR mode. Windows does currently *not* support dynamically switching HDR mode on/off while you're playing an HDR movie (or playing an HDR game)! Microsoft may consider dynamic switching in the future, but don't hold your breath, I'm not too optimistic that they'll add that any time soon (if ever). But let's wait and see.

2) If you switch the "HDR and Advanced Color" option off, your TV will always receive SDR from the PC. If you play an HDR movie in this situation with the madVR option "passthrough HDR content to the display" activated, the OS/GPU will perform a low quality HDR -> SDR conversion behind madVR's back. Consequently, HDR content will look "ok", but the quality is not really good. SDR content will look "perfect", though.

3) If you switch the "HDR and Advanced Color" option on, your TV will always receive HDR from the PC. If you tell madVR to "passthrough HDR content to the display" in this situation, HDR movies should look "perfect". If you play SDR content in this situation, the OS/GPU will convert SDR to HDR behind madVR's back. Consequently, SDR content will look "ok", but it will not be perfect.

4) Currently HDR and fullscreen exclusive mode is a problematic combination. It's partially the fault of the OS, partially of the GPU drivers. It's not clear yet if this will be fixed, or when. Generally, Microsoft wants to get rid of fullscreen exclusive mode. It might suddenly disappear in a future Windows 10 version. I'm not happy about that at all. Which is one of the reasons I've been recommending Windows 8.1 for months now.

5) Nvidia comes to the rescue of all HTPC users who want perfect quality for both SDR and HDR content: Nvidia's private HDR API allows madVR to dynamically switch the TV into and out of HDR mode, as needed. For this to work, you need to deactivate the OS "HDR and advanced color" switch.

6) madVR v0.91.10 had a bug where Nvidia's private HDR API was only called properly in the 32bit madVR version, but not in 64bit. This bug is fixed in madVR v0.91.11.

7) All Nvidia drivers starting with 381.xx up to the latest (384.76) have a bug which results in madVR not being able to switch the TV into HDR, when using FSE mode. You can workaround the issue by disabling FSE mode. Alternatively, using any driver between 376.xx and 380.xx should make dynamic HDR switching work perfectly.

As it stands right now, for all Windows users who want to do both SDR and HDR playback in perfect quality, I can only recommend Nvidia GPUs, because only Nvidia's private API allows madVR to dynamically switch the TV between SDR <-> HDR atm. I'm talking to Intel, maybe they will add a private API, too. Unfortunately my AMD contacts have gone silent. There's still hope for Windows 10, but I'm not overly optimistic atm.

[nevcairiel]

As it stands right now, for all Windows users who want to do both SDR and HDR playback in perfect quality, I can only recommend Nvidia GPUs, because only Nvidia's private API allows madVR to dynamically switch the TV between SDR <-> HDR atm. I'm talking to Intel, maybe they will add a private API, too. Unfortunately my AMD contacts have gone silent. There's still hope for Windows 10, but I'm not overly optimistic atm.

Just to clarify, before more people ask, basically NVIDIA also works on Windows 10 Creators, minus the bug they're still fixing in their drivers?

[madshi]

The reason for this is simple - I would like to use different 3D LUTs for different ICC profiles.

This is because NEC MultiProfiler loads differently named profiles depending on built-in gamut modes of the monitor.
So, this is the only way for me to switch between different calibration modes in madVR automatically, depending on selected picture mode in MultiProfiler.
Hmmmm... Do you keep the ICC profile active, and the 3DLUT comes on top of that? Or do you have "disable GPU gamma ramps" checked in madVR, which I think should disable the ICC?

Usually you get the best quality if you disable the ICC and create a new 3DLUT which does everything. But that might not be what you want?

Just to clarify, before more people ask, basically NVIDIA also works on Windows 10 Creators, minus the bug they're still fixing in their drivers?
I hope to have a workaround in v0.91.11 for the Nvidia driver bug. It works on my PC, but I can't say for sure if it will work for everyone.

Basically there's a chance everything might already work perfectly for all Nvidia users with the latest drivers. If it doesn't, then downgrading to an older driver should definitely do the trick.

[igvk]

Hmmmm... Do you keep the ICC profile active, and the 3DLUT comes on top of that? Or do you have "disable GPU gamma ramps" checked in madVR, which I think should disable the ICC?

Usually you get the best quality if you disable the ICC and create a new 3DLUT which does everything. But that might not be what you want?

This ICC profile is used for color managed programs to map the output colors to the monitor color space. I'm not loading anything to GPU, if I understood the question correctly.

The monitor itself has several modes (like Full wide gamut, sRGB, Adobe RGB). I usually switch between Full (native) and sRGB mode. And here system monitor ICC profile changes (when done in NEC MultiProfiler, not via monitor own controls) - it's actually convenient, because all color-managed programs know how to convert the colors.
Except for madVR, which still uses wrong 3D LUT. So, if I could access the name of the current system display ICC profile, I could use another 3D LUT in madVR (or disable usage of it at all).

Here is example of display profile in Windows:
https://s19.postimg.org/6pwvrky0v/Color_Management-1.jpg (https://postimg.org/image/6pwvrky0v/)

[thighhighs]

Hi all. What about features like NGU AA direct 4x and NGU direct 3x? Direct 3x NGU completely dead? Direct 4x NGU AA possible in the future?

[huhn]

Is there a set of example images that can be used to make a comparison? I can't even figure out how to take a screenshot of madVR-rendered content in Exclusive FullScreen Mode...
than do it without FSE?
I often can't see any difference, even zoomed in. I just go by what general thread population suggests as overall highest-quality setting for non-anime film content.

if you can't see it you don't have to use it.

i mean you have trouble with downscaling because you are following random settings from other people...

[mrcorbo]

Preliminary results from the new version running on a GTX 1060, Latest Nvidia Drivers (384.76), latest Fast Ring Insider Build of Windows 10 (16232).

Switching in and out of HDR mode works "the Nvidia way". Basically, it's identical to how invoking HDR mode on an Nvidia card worked prior to the Creator's Update. UI colors go all wonky, etc. But it does show the video in HDR.

When viewing an HDR video madVR default settings "Use DXVA chroma upscaling.." under "trade quality for performance" cause incorrect colors when in fullscreen.

FSE still doesn't present HDR for me, but non-FSE fullscreen doesn't crash anymore when passing HDR metadata so I can finally watch an HDR video in fullscreen. :cool:

Both closing MPC-HC and playing a non-HDR video after an HDR video trigger an Nvidia HDR to SDR mode change. So, for me, your workaround is working.

Edit:Also, if you follow up an HDR video with another HDR video it triggers the mode change again (and a few seconds of black screen) even though you're already in HDR mode.

[mitchmalibu]

Correct. madVR is not involved at all in anything audio related. Reclock works by resampling audio, so that's not something madVR can do. However, there will soon be a new feature that may make Reclock like algorithms not needed, anymore. We'll have to see if it works as intended, but that's my hope.
Care to share a bit more about this ? To say that it piqued my curiosity is an understatement :)

Otherwise, I tried to make the "D3D11 windowed mode now supports 10bit, if "HDR and Advanced Color" is on" feature work, no go on 32bit MPC-BE : getting a black screen as soon as I go fullscreen using a HDR clip. Same on 64bit. 10bit with FSE works fine (but Reclock goes bonkers).

Anyway, these are uncharted territories you're exploring, keep up the great work.

Edit : nevermind, didn't see that nvidia released a new driver this week. Updated to 384.76, everything working as described.

[Q-the-STORM]

Can someone please explain.
I have a ripped version of the BD Oklahoma which is 1080 29.970 frame rate.
As it states Scan type, store method = Interleaved fields in the properties, this does mean its a 29.970 interlaced BD is that correct?


The film was shot in 29.97fps, so this is the correct framerate...
Since the BD specs only support 29.97fps interlaced, they encoded this with MBAFF interlacing which should decode to 29.97 progressive frames (like most 25fps BDs and european TV)

[70MM]

The film was shot in 29.97fps, so this is the correct framerate...
Since the BD specs only support 29.97fps interlaced, they encoded this with MBAFF interlacing which should decode to 29.97 progressive frames (like most 25fps BDs and european TV)

Many thanks for your reply, you are the first on the subject at hand...

I have so much trouble playing this film on my 1080ti card, it keeps repeating 100s of frames constantly into the 1000s!
Even though my render times are very low, 15 odd.

I must have things not set correctly for playing 29.97 progressive material. I set madvr to 4K for all my ripped BDs, 23.97 materiel plays perfectly.

Any pointers in the setup would be greatly appreciated...