madVR - high quality video renderer (GPU assisted)

[sat4all]

OK, so firstly if you're creating an HDR 3D LUT in Displaycal (using the Madvr HDR profile presumably) with a 400 nit max display you should set the peak luminance on the 3D LUT tab to around 1000 nits.

In MadTPG you are emulating an HDR movies metadata, so set the minimum to 0 and the max to 4000.

Personally I increase the patches from the default 175 to just over 1000 as I had some issues with using less, however you may be fine with the default.

Remember to set the peak luminance in Madvr to 1000 nits also.

Let me know how you get on with that :)

So i took your advice and made a 1114p profile using you suggested settings, unfortunately the outcome was very dull. Comparing mad max fury road bluray version to uhd make the last one look even dimmer. (my sdr mode is calibrated using 100nit as target)
Now i'm giving 400nit as target another shot in displaycal, but using larger profile 1114p this time bcs all my previous profiles were using default 175p.

Edit: Increasing patches doesn't matter, targeting 400nit still look unnormally bright.

Cheers

[Clown shoes]

So i took your advice and made a 1114p profile using you suggested settings, unfortunately the outcome was very dull. Comparing mad max fury road bluray version to uhd make the last one look even dimmer. (my sdr mode is calibrated using 100nit as target)
Now i'm giving 400nit as target another shot in displaycal, but using larger profile 1114p this time bcs all my previous profiles were using default 175p.

Edit: Increasing patches doesn't matter, targeting 400nit still look unnormally bright.

Cheers

I'm honestly not sure mate. Those numbers were Florian's suggestion based on tone mapping calculations.

If I'm honest I've given up on the 3D LUT approach and I've gone back to calibrating the display with manual controls and HCFR. I'm getting much better results this way.

[sat4all]

I'm honestly not sure mate. Those numbers were Florian's suggestion based on tone mapping calculations.

If I'm honest I've given up on the 3D LUT approach and I've gone back to calibrating the display with manual controls and HCFR. I'm getting much better results this way.

thanks much, maybe be i need to adapte to dim hdr picture.
everything else is unwatchable.
Manual calibration is no go for me bcs of LG oled's broken CMS.

[Asmodian]

You cannot make one 3DLUT that looks good for all HDR sources, only 3DLUTs that looks good for a specific set of metadata. Put your content's metadata values into the mastering display's fields when creating the 3DLUT.

[kalston]

Actually it goes bonkers with GSYNC even without Smooth Motion enabled sometimes.

Just add your video player's .exe to the Windows Media Player's nvidia profile (some other built-in profiles work, Internet Explorer for example, just don't use a game profile or try to make your own), you will never have to worry about G-Sync for video playback again.

[NoTechi]

You cannot make one 3DLUT that looks good for all HDR sources, only 3DLUTs that looks good for a specific set of metadata. Put your content's metadata values into the mastering display's fields when creating the 3DLUT.

I am using a 3DLUT for non HDR Content so far and I really like the result. I wasn't aware that HDR requires different 3DLUT (madvr was actually giving me a error message when I tried to add the BT2020 LUT within the HDR config page) but thinking it over it makes sense to me since I would use different settings in my projector as well.
So I am planning now to:
- re-calibrate my HDR Settings
- create a HDR 3DLUT

My question is why it is different for different HDR sources. Isn't the whole point of using a 3DLUT to have the incoming signal analysed and the outgoing signal adjusted based on the 3DLUT. If for example a movie would be mastered in 1000nits and the whole calibration and the 3DLUT would have been done targeting 4000nits wouldn't be the intention of madvr to adjust it accordingly?

But if I am wrong and if I would need a HDR 3DLUT for all types of different source metadata would there be a way madvr recognizes the incoming metadata and chooses the right HDR 3DLUT automatically?

NoTechi

[fhoech]

If I'm honest I've given up on the 3D LUT approach and I've gone back to calibrating the display with manual controls and HCFR. I'm getting much better results this way.
In your case it's just impossible to profile your particular display in HDR mode and get something usable due to the incredibly inconsistent display-imposed HDR tonemapping. The situation is different on displays where there is no display-imposed tonemapping or the tonemapping is of higher quality (e.g. the LG OLED HDR TVs seem to do fine when they are not adjusted to death before profiling).

[fhoech]

You cannot make one 3DLUT that looks good for all HDR sources, only 3DLUTs that looks good for a specific set of metadata.
One's anecdotal opinion doesn't necessarily make an universal truth.

Put your content's metadata values into the mastering display's fields when creating the 3DLUT.
I wouldn't recommend doing it that way. By entering a mastering display peak luminance that is lower than 10K nits you gain a certain (usually really small) amount of extra luminance in HDR highlights, but risk potentially losing detail due to clipping. HDR metadata is not a good or accurate way to figure out what's actually encoded in the content.

[sat4all]

Finally i've got things right, thanks to this document

https://preview.ibb.co/gmSWqo/uhda_calibration_procedure.png (https://ibb.co/hK34Ao)

With 540 as target in both displaycal and madhcctrl hdr settings. Now HDR average picture level doesn't look deviate drastically from that of a regular Bluray SDR.
So referring to this document, if your oled can't match the recommended minimum peak luminance you should still use 540 as target, but with newer oled's your are free to use your real peak luminance as they go beyond that.
This is what they mean? or 540 is the magic number for my display which barely hit 400nits.

[Clown shoes]

Finally i've got things right, thanks to this document

https://preview.ibb.co/gmSWqo/uhda_calibration_procedure.png (https://ibb.co/hK34Ao)

With 540 as target in both displaycal and madhcctrl hdr settings. Now HDR average picture level doesn't look deviate drastically from that of a regular Bluray SDR.
So referring to this document, if your oled can't match the recommended minimum peak luminance you should still use 540 as target, but with newer oled's your are free to use your real peak luminance as they go beyond that.
This is what they mean? or 540 is the magic number for my display which barely hit 400nits.

I would say that is a coincidence as that document is specifically talking about a display with 540 nits max output which yours doesn't have

[Clown shoes]

I am using a 3DLUT for non HDR Content so far and I really like the result. I wasn't aware that HDR requires different 3DLUT (madvr was actually giving me a error message when I tried to add the BT2020 LUT within the HDR config page) but thinking it over it makes sense to me since I would use different settings in my projector as well.
So I am planning now to:
- re-calibrate my HDR Settings
- create a HDR 3DLUT

My question is why it is different for different HDR sources. Isn't the whole point of using a 3DLUT to have the incoming signal analysed and the outgoing signal adjusted based on the 3DLUT. If for example a movie would be mastered in 1000nits and the whole calibration and the 3DLUT would have been done targeting 4000nits wouldn't be the intention of madvr to adjust it accordingly?

But if I am wrong and if I would need a HDR 3DLUT for all types of different source metadata would there be a way madvr recognizes the incoming metadata and chooses the right HDR 3DLUT automatically?

NoTechi

It's quite simple really; Most of our TVs aren't really suitable for HDR material, despite being compatible.

You really need a minimum of 1000 nits otherwise you need to make compromises somewhere.

With regard to applying the HDR LUT it won't auto apply at present and you will need to use the one in the DisplayCal folder

[Clown shoes]

In your case it's just impossible to profile your particular display in HDR mode and get something usable due to the incredibly inconsistent display-imposed HDR tonemapping. The situation is different on displays where there is no display-imposed tonemapping or the tonemapping is of higher quality (e.g. the LG OLED HDR TVs seem to do fine when they are not adjusted to death before profiling).

I've actually got the 3D LUTs working much better now, but I discovered I need to do some display calibration first to get it much closer to target. My aim is to get a half decent calibration with HCFR first and then follow that up with DisplayCal to polish things off :D

[Clown shoes]

In your case it's just impossible to profile your particular display in HDR mode and get something usable due to the incredibly inconsistent display-imposed HDR tonemapping. The situation is different on displays where there is no display-imposed tonemapping or the tonemapping is of higher quality (e.g. the LG OLED HDR TVs seem to do fine when they are not adjusted to death before profiling).

Oh and another thing I found out from Ted was that you should never touch the brightness and contrast controls on a commercial HDR TV, as it effectively breaks the tone mapping.

Since following that little nugget of advice I'm not getting all that red crap in my highlights like I was before :D

[Asmodian]

One's anecdotal opinion doesn't necessarily make an universal truth.

True, but I would be surprised if you could get one 3DLUT that looks good for both Wonder Woman and the first Harry Potter movie.


I wouldn't recommend doing it that way. By entering a mastering display peak luminance that is lower than 10K nits you gain a certain (usually really small) amount of extra luminance in HDR highlights, but risk potentially losing detail due to clipping. HDR metadata is not a good or accurate way to figure out what's actually encoded in the content.

So you recommend analyzing the video and setting the mastering display peak nits to the peak actually encoded? I do get good results that way but doesn’t that need a 3DLUT for every video?

If you don’t care about the extra luminance in the highlights I suppose you could use 10k but then it is much darker than passthrough is, at least on my OLED with it peak brightness just below 700 nits after calibration. My display is already struggling with brightness for HDR, a 3DLUT that dims it more is not a good option. :(

Harry Potter, for example, is very dark with a 3DLUT generated with peak nits set to 10K but looks normal with passthrough. It is not a really small change, it is quite significant and much more noticeable than improved hue, etc. Right now a 3DLUT completely ignores the video’s metadata doesn’t it? There is a reason HDR is moving to dynamic metadata and tone mapping that changes for each frame, not just every video, and a 3DLUT that does 1 tone map for everything cannot be as good or there is no point in even having metadata for HDR in the first place.

[Warner306]

The next madVR build is supposed to add a profile rule for the peak luminance of the video. This should make it possible to use multiple HDR 3DLUTs for multiple HDR standards. Not perfect, but an improvement.

[foozoor]

Maybe the guy madshi hired is fixing this.

[Thunderbolt8]

Maybe the guy madshi hired is fixing this.he hired someone? to keep madvr up to date?

[nevcairiel]

No. Don't listen to foozoor, he is just constantly trolling.

[Manni]

True, but I would be surprised if you could get one 3DLUT that looks good for both Wonder Woman and the first Harry Potter movie.



So you recommend analyzing the video and setting the mastering display peak nits to the peak actually encoded? I do get good results that way but doesn’t that need a 3DLUT for every video?

If you don’t care about the extra luminance in the highlights I suppose you could use 10k but then it is much darker than passthrough is, at least on my OLED with it peak brightness just below 700 nits after calibration. My display is already struggling with brightness for HDR, a 3DLUT that dims it more is not a good option. :(

Harry Potter, for example, is very dark with a 3DLUT generated with peak nits set to 10K but looks normal with passthrough. It is not a really small change, it is quite significant and much more noticeable than improved hue, etc. Right now a 3DLUT completely ignores the video’s metadata doesn’t it? There is a reason HDR is moving to dynamic metadata and tone mapping that changes for each frame, not just every video, and a 3DLUT that does 1 tone map for everything cannot be as good or there is no point in even having metadata for HDR in the first place.


At the moment the best way to use a 3D LUT with MadVR for HDR content is to use a BT2020 SDR calibration (with a power gamma of 2.4) and use the pixel shader HDR to SDR conversion. If you set your display to its peak brightness (or whatever you're comfortable with with HDR) you're still watching HDR (it's just that the conversion is done in the source instead of the display). You can then create different profiles for various values for peak brightness, according to content. And you only need one SDR BT2020 3D LUT to get best accuracy all the time.

Madshi didn't have the time in the last release to include the peak brightness variable that will allow us to use profiles to select automatically the best profile, but you can still switch manually with a key combo (or iRule).

I'm still using passthrough because I have implemented in the Vertex with HD Fury a way to automatically select the best custom gamma curve for my JVC according to the content, but as soon as MadVR catches up I'll most likely use pixel shader (provided we get 10bits back as there is no banding in pixel shader, unlike passthrough), as having a 3D LUT significantly improves results, even on my autocal'ed JVC.

Ideally the next step will for MadVr to dynamically adjust the curve to the content, so we won't need profiles anymore, but we're not there yet.

[foozoor]

No. Don't listen to foozoor, he is just constantly trolling.
He said he hired someone for something in madVR. :search:

he hired someone? to keep madvr up to date?
You should ask madshi. ;)

[gfxnow]

Just out of curiosity, what media player does Madshi himself use when testing/using MadVR?

[ajamils]

I have following setup
- HTPC (i3, 8gb RAM, Nvidia 1050)
- Yamaha A3070 AVR
- JVC X790r Projector

I recently started using madVR with Kodi and MPC-HC and having a lot of issue playing 4K mkvs with HDR. When I play a file using MPC-HC (with madVR set to pass through HDR and no other settings changed), my projector automatically switches to HDR mode indicating that HDR signal is being received but the whole pictures has dark pink/purple tint on it. As soon as I end playback, everything goes back to normal. If I select Enhanced Video Renderer (Custom Presenter) in MPC-HC, video plays correctly but HDR tag is not passed so no auto switching is done by projector. HDR is turned off in Windows settings (and I am unable to turn it on because when I try to do that, everything goes black and by the time pictures resumes the prompt to confirm selection is gone)


https://uploads.tapatalk-cdn.com/20180515/1e46e624e607b233ecf03bcbe394e1df.jpg

https://uploads.tapatalk-cdn.com/20180515/30dedc1ec263be7b9a0bb28a9195c106.jpg

I have also played with setting in madVR to convert HDR to SDR but the results have been less than ideal with more prominent noise and depending on the settings colors ranging for overly saturated to very pale.

I have already tried different HDMI cable and doing a clean install of Nvidia drivers but not much luck.

Separately, I'm having another issue which may or may not be related and that is I cannot set the resolution in Window or Nvidia control panel to 1080p/60. For some reason it keeps getting back to 4K/24. When I try to set the display setting to 1080p/60 the screen goes black and when it comes back I usually have a second or two to press a button to confirm changes otherwise it reverts back to 4k/24 setting. If in case I successfully change the settings it works for sometime and then randomly changes back to 4k/24.

I have checked on the AVR and video is set to "Pass through" on the projector it shows that it is receiving "4K signal". So there is something in the HTPC which keeps switching the resolution/frame rate. For the most part I can live with that setting but some of the programs (like Nvidia Control panel) do not scale even when scaling is set to 300% so they are impossible to use on 120" screen.

[Koltos]

Hi everyone!

Please someone could help me. I have tv Samsung UE55J6200 which connected to PC by hdmi cabel.

I tried to make right settings for watching movies slightly on 23,976 ghz. But i have problem with custom mode.

My adapter is GTX 770. I heard that NVIDIA has problem with right 24 hz. So in MADvr there are 23 hz mode is active, when on NVIDIA in custom mode is 24hz. Than I tried to optimize settings, watch film for 30-40 minutes than i go to settings and see this:

https://pp.userapi.com/c830608/v830608621/102b1a/dg7PHK9OdF4.jpg

I picked mode without frame drops and repeats, push Test mode and screen of my TV becomes black. I suppose GPU are not supported right mode.

But why? How can i solve that problem? Someone has it? So how is right to calibrate this?

[huhn]

a black screen usual means your TV doesn't support the input. you can only try a different combination in hope it works.

[Koltos]

a black screen usual means your TV doesn't support the input. you can only try a different combination in hope it works.

So is only way to use mode with repeat frames?

[ryrynz]

No. Don't listen to foozoor, he is just constantly trolling.Not this time. Madshi did say he was getting external help to deal with 3dlut stuff I think it was. Speculation is gonna happen in a forum.

Just out of curiosity, what media player does Madshi himself use when testing/using MadVR?

mpc-hc most likely I think, I'd rate mpc-be as the better player though.

On another note I was playing with FSE to test out 10bit color and noticed that the composition rate was listed as 60hz even though I had the screen at 24hz.

[nevcairiel]

Not this time. Madshi did say he was getting external help to deal with 3dlut stuff I think it was. Speculation is gonna happen in a forum.

I know what madshi said, he is still using that information to troll.

[Audionut]

but I would be surprised if you could get one 3DLUT that looks good for both Wonder Woman and the first Harry Potter movie.


I'm getting to old to chase mastering problems.

This is by far the most undesirable aspect of display calibration, even if you manage to understand all of the different aspects of display calibration (there is no button that says, "push here stupid"), you're still at the mercy of people who are supposed to know better, but still **** it up.

[huhn]

So is only way to use mode with repeat frames?

i have no clue what your TV accepts and what not.
so yes there is a possibility that you can fix it with a custom refreshrate.

[madjock]

I had no joy with the custom side of MadVR, if I tried anything else apart from the custom res that I set up in Nvidia that MadVR saw, then I just had a fuzzy screen mostly.

Best I could get it to was 1 Frame Repeat every 38 minutes with Custom res and Nvidia, better if I took some settings down, so just learnt to let that go.

Had to roll back to an earlier driver with Nvidia to get the custom res to stick as have many.

[oldpainlesskodi]

Hi Guys,

A few pages back I posted about the Club 3D CAC 1080 Display Port 1.4 HDMI 2.0 A (B) Hdr Active displayport to hdmi adapter, and if anyone has bought one, and would like the latest firmware for it, PM me (I am working with the manufacturer on ironing out a few bugs).

[Koltos]

I had no joy with the custom side of MadVR, if I tried anything else apart from the custom res that I set up in Nvidia that MadVR saw, then I just had a fuzzy screen mostly.

Best I could get it to was 1 Frame Repeat every 38 minutes with Custom res and Nvidia, better if I took some settings down, so just learnt to let that go.

Had to roll back to an earlier driver with Nvidia to get the custom res to stick as have many.

Sounds good. To what driver did you roll back?

And I think Nvidia is really working strange in a way of custom mode. One of funny thing, when my hdmi on 60hz I need to enable on my TV black level of hdmi "Low". When it changes on 24hz with MADvr I need to enable black level of hdmi to "Normal". It's so weird that signal of black seems changing because of refresh rate.

[foozoor]

Not this time. Madshi did say he was getting external help to deal with 3dlut stuff I think it was. Speculation is gonna happen in a forum.
I thought it was for his completely new algorithm.
I hope it's not related to color conversion. :scared:

[madjock]

Sounds good. To what driver did you roll back?

And I think Nvidia is really working strange in a way of custom mode. One of funny thing, when my hdmi on 60hz I need to enable on my TV black level of hdmi "Low". When it changes on 24hz with MADvr I need to enable black level of hdmi to "Normal". It's so weird that signal of black seems changing because of refresh rate.

I went back to 390.77.

I then went to Nvidia Control Panel/Customise, changed the Refresh Rate to 24 or 23 in the upper refresh rate box (only allows 2 numbers)

Then go to Timing, select GTF, then select Manual and the GTF settings stay there, then change that refresh rate in lower right to 23.976 and save.

Give that a go and see how you get on. I went from frame drops every X minutes, to frame repeats every 38.

When you start a video it says frame drops every X this then goes to days then jumps over to frame repeats, the gist is there are multiple clocks involved and you will waste more time messing with it and getting nowhere, and apart from being fixated on something I never cared about before I am quite happy.

[ryrynz]

I thought it was for his completely new algorithm.

Yeah, that's right.. The math side of things for that.

[fhoech]

True, but I would be surprised if you could get one 3DLUT that looks good for both Wonder Woman and the first Harry Potter movie.
Try target peak = 700 with mastering display peak = 10K.

If you don’t care about the extra luminance in the highlights I suppose you could use 10k but then it is much darker than passthrough is
The LG 7 series do seem to loose quite some highlight detail though (e.g. the beach in Sony's "Whale in Tonga" demo looks very flat), and this looks to be how they buy the extra brightness.

Harry Potter, for example, is very dark with a 3DLUT generated with peak nits set to 10K but looks normal with passthrough.
Target peak shouldn't be 10K. Mastering display peak should probably be 10K for best preservation of highlight detail.

It is not a really small change, it is quite significant and much more noticeable than improved hue, etc. Right now a 3DLUT completely ignores the video’s metadata doesn’t it?
When using a "process HDR content" 3D LUT, you can override the metadata that is being sent to the display in madVR's HDR settings. I don't know if disabling that checkbox means the movie metadata is passed through.

[Asmodian]

Try target peak = 700 with mastering display peak = 10K.

Yes, this is what I tried. Or 4000 for the mastering display peak. I seem to get best results using the measured peak nits for a video as the mastering display's peak and 700 for target peak. It has a similar brightness as passthrough. At 10K mastering display peak all movies are pretty dark, with a dim "normal" brightness, but highlights do look good.

I would not be surprised if LG was normally pushing the mid-range into the highlights but the image is still too dark with all my HDR content using a 10K 3DLUT. :(

I did try messing with the metadata options sent to the display but I am not sure they help much, I do not remember a big difference between them. Also I wanted to leave them set to the same values I used when profiling the display.

[LigH]

Can you imagine any reason why madVR 0.92.12 may delay video rendering by about 4-6 seconds of blackness after a player starts? The statistics OSD reports about 100 dropped frames and appears not before the video as well; ProcessExplorer reports 0% GPU usage during this delay; EVR CP renders immediately.

[huhn]

what os?
is delay frames until queues are full tickt?

[LigH]

Windows 7 SP1

No, the delay option is not checked. Queue sizes are: CPU = 12, GPU = 8 (AMD Phenom-II X6 + Nvidia GTS 450).

[giulianoprs]

Hello everyone, I'm new to the forum, sorry my English, I ask you some advice, in "the display modes" having a 4k TV is better to set in the string of resolutions 2160p23,2160p24 ect ect always? even with 1080p files? in "chroma upscaling" NGU is ok? or too strong?
In "image upscaling" better JIN (upscaling) or NGU (doubling)? here I have a lot of confusion.
My video card is an asus amd rx 560 strix o.c.
Thanks to everyone bye !!!
I forgot with NGU I have very high temperatures, 65 ° GPU

[Warner306]

Hello everyone, I'm new to the forum, sorry my English, I ask you some advice, in "the display modes" having a 4k TV is better to set in the string of resolutions 2160p23,2160p24 ect ect always? even with 1080p files? in "chroma upscaling" NGU is ok? or too strong?
In "image upscaling" better JIN (upscaling) or NGU (doubling)? here I have a lot of confusion.
My video card is an asus amd rx 560 strix o.c.
Thanks to everyone bye !!!
I forgot with NGU I have very high temperatures, 65 ° GPU

Yes, keep all the display modes 2160p, etc. This will upscale everything to 2160p.

NGU Anti-Alias or any other NGU scaler is good for chroma upscaling. For image upscaling/doubling, NGU Sharp or NGU Anti-Alias are also good choices.

That temperature is not that high and won't do any damage. If it bothers you, use something other than NGU for chroma/image upscaling.

[Kamikaze Ice]

thanks much, maybe be i need to adapte to dim hdr picture.
everything else is unwatchable.
Manual calibration is no go for me bcs of LG oled's broken CMS.

Check how your display behaves when showing 150+ nits content.
I've mentioned in one of your avsforum threads that I have an E6 so I'll use mine as an example of what I'm trying to say here.

Any portion of content exceeding ~130 nits will begin to "build up" the longer it remains on screen.
When calibrating/profiling my primary monitor (E6) I move everything off of it (no desktop icons, no task bar, no wallpaper, etc). I change the background color to 45/45/45 rgb.
Since madtpg does not stay minimized after measurements, I push it into the corner and resize it (no chance of retention or burn in from interface elements).
When I toss a windowed "60% white" pattern on the screen for 60 seconds, when I return to the desktop I can clearly see a glowing rectangle where the white pattern was. This is retention, and goes away after a few minutes.
If you measure say, 30%, it will be brighter than it should.

It's very important to know how your display behaves in this regard.

This is likely why you have a dimmer picture with DisplayCAL.

I'm getting closer to being ready to use DisplayCAL, but I'm assuming white drift compensation will be counter-productive in this case, adding more white patterns in the list.
I think the only solution for the time being is to create a custom pattern list manually to keep retention from happening. I've been trying to avoid doing this, as it's a huge pain in the ass lol.



And like Florian said, the tone mapping can also screw with it. You'd need to have a separate 3D LUT for the various nit levels specified in the metadata. 85% of 4000 nits would be mapped differently than 85% of 1000 nits.
How accurate the metadata is, is another can of worms.



---------

Finally i've got things right, thanks to this document

<SNIP>

With 540 as target in both displaycal and madhcctrl hdr settings. Now HDR average picture level doesn't look deviate drastically from that of a regular Bluray SDR.
So referring to this document, if your oled can't match the recommended minimum peak luminance you should still use 540 as target, but with newer oled's your are free to use your real peak luminance as they go beyond that.
This is what they mean? or 540 is the magic number for my display which barely hit 400nits.

That's the calibration procedure Ted and I were talking about in your thread on avsforum.

You cannot LITERALLY follow their procedure. It is impossible.
Also, that was for the 2016 oled series like my E6, and does not apply to yours at all.

While you can't follow their literally, it is possible to follow their targets...
HOWEVER this can only be done by using the service menu controls (lowering Sub-Brightness and Sub-Contrast, using the 2-point "white balance" controls), and aligning 20-point controls with the normal Brightness/Contrast controls.
This is a very tedious process. Aside from me and harlekin, I've not seen anyone even try this approach to calibrating these displays. I don't blame them, this does sound completely too stupid to work. I'm not suggesting anyone try this either, just that this is something I've done and can't prove or disprove my claim.

[MysteryX]

On a ASUS laptop with Geoforce GTX 1050, if I use madVR with DirectX9, sometimes the video driver will be unstable, such as video occasionally freezing or going blank, especially when switching monitor, and sometimes even BSOD. (although I'm not 100% certain these instabilities are caused by madVR but it appears so)

If I render using DirectX11, it appears to be more stable, but the seek bar doesn't display properly and often goes black when hovering the mouse. (and full-screen dedicated mode only displays a black screen)

Anyone else have these issues?

On my previous laptop, with a Radeon 7670M, it was perfectly stable under Direct9 but DirectX11 wasn't working well.

[Sebastiii]

Hi guys :)

Spotted a bug with confirmed by friend too, from madVR9213 up to madVR9214 (latest) 10Bit for "D3D11 fullscreen windowed" didn't work anymore (it says 8 bit).

Do you have the same ?

Cheers.

[ryrynz]

But now there is another issue. 10bit had stopped working while in D3D11 Fullscreen Windowed mode. Only way to enable 10bit now is to use the D3D11 Exclusive mode. :(

That's a bug in the latest MadVR release unless you are in passthrough on Windows 10, because in that case there is minor banding due to OS/nVidia driver bug. In pixel shader, 10bits should be brought back shortly, as I don't think it was Madshi's intention to force 8bits in that mode as well.

Learn to search my son..

[mrmojo666]

Hi guys :)

Spotted a bug with confirmed by friend too, from madVR9213 up to madVR9214 (latest) 10Bit for "D3D11 fullscreen windowed" didn't work anymore (it says 8 bit).

Do you have the same ?

Cheers.


Here it's working nicely d11 fullscreen windowed output 10 bit. but as you know i have amd card.

[el Filou]

No, the delay option is not checked. Queue sizes are: CPU = 12, GPU = 8 (AMD Phenom-II X6 + Nvidia GTS 450).Are you using MPC-HC? If yes, have you tried another NVIDIA driver version? I remember that in one of their release notes some time ago it said there was a bug where playback would freeze/stutter at the start with MPC-HC.

[oldpainlesskodi]

I noticed a few folks having problems getting custom modes to work ( i think on Nvidia cards).

I am on driver version 391.35 (and have tried the latest drivers), and I could not get custom modes to work with the latest versions of MadVR. However, I went back to MadVR v0.92.7, and voila, custom modes work perfect, and for my set up, using 10bit rgb @ 4K 23.976 too (one drop frame every 8 hours or so).

If you dont want to stay on 0.92.7, simply use that version to set custom mode, and then go back to your preferred version of Madvr.

This may, or may not work for others, but it works here, so I see no reason why it would not work for other setups using nvidia.

[e-t172]

Can you imagine any reason why madVR 0.92.12 may delay video rendering by about 4-6 seconds of blackness after a player starts? The statistics OSD reports about 100 dropped frames and appears not before the video as well; ProcessExplorer reports 0% GPU usage during this delay; EVR CP renders immediately.

Exact same issue here, it appeared when I upgraded Windows from 1709 to 1803. This only happens when madVR switches to exclusive mode, though.