madVR - high quality video renderer (GPU assisted)

[mambans]

Quick question. I know fullscreen exclusive is a bit buggy with HDR but is there anyone who have gotten it to work?

My won't enter exclusive mode so I still get presentation glitches.

[jespermart]

Anyone got Navi yet? Curious to know how it performs. =)
It performs great. I just changed my Rtx 2010 ti out for a 5700 xt and no more problems with stuttering only issue 3d mvc has to been run in exclusive mode.
Settings are almost identical i have lowered ngu very high settings in my 4k profile to high I didn't have to change anything in my other profiles:)

[jasonwc18]

The latest Nvidia 431.36 driver will only provide 8 bit color output from a custom resolution mode. This appears to be a driver bug regression as I was using the same graphics card and projector (GTX 1070 and a JVC RS600) with a much older driver and got 12 bit output from my custom mode. However, I recently added a 65" OLED in the back of my theater for gaming and HDR, and upgraded the HTPC to a Ryzen 3600 to accommodate the gaming demand. Everything is the same as before except I no longer have the option to set 12 bit color for any custom mode, regardless of resolution or Hz setting.

In contrast, for the standard mode, I can select 24 bit color for 2160p23, 24, 25, 29 and 30Hz modes. If set to 59 or 60Hz, it'll use 8 bit color (due to the limitation of HDMI 2.0) but will revert back to 12 bit color when using 23, 24, 25, 29, or 30 Hz modes.

If I wasn't gaming, I would just go back to my ancient Nvidia driver. However, I would like a relatively new driver since I'll also be gaming on this system. So, can anyone tell me what recent driver versions still work with 12 bit color using custom modes?

Observation: Now that I"m using the same HTPC to connect to two display devices (JVC RS600 projector and a 65" LG OLED), I discovered that the Nvidia driver only saves a single custom mode per resolution/Hz. It's not independent per device. As such, if you are going to connect more than one device, the same mode must work on all devices. I learned this the hard way. :/

[Asmodian]

None of the new ones support >8 bit for custom modes.

However, more than 8 bit is unimportant when using madVR. The only impact is more noise in the image, does 8 bit look too noisy to you? If you get someone to do a blind test with you can you tell which is which?

[tp4tissue]

@jasonwc18 Just make a Madvr partition.

I have entirely separate system partitions for various programs that I NEEED to work.

I have separate custom partition for Starcraft Remastered/ Solidworks 14/ Solidworks 18 / Photoshop and Madvr.

And I also have multiple computers, and multiple monitors at the same desk

This is the ghetto way to fix things, by just throwing more computers at it, But this guarantees Low-Contamination, and Everything works.

[jasonwc18]

None of the new ones support >8 bit for custom modes.

However, more than 8 bit is unimportant when using madVR. The only impact is more noise in the image, does 8 bit look too noisy to you? If you get someone to do a blind test with you can you tell which is which?

What about for native 10 bit sources (4K HDR Blu-Rays)? That was my concern. I assumed it wouldn't matter for 8 bit content.

For those curious, I tested 416.81, 417.71, and 418.81 (DDU uninstall between each) and none was able to do 12 bit color with a custom mode. I chose those versions because people in this thread reported it worked - but on an earlier version of Windows 10 (1803; I'm using 1903 for the Ryzen scheduling update). However, MS's default Nvidia driver, 388.43 (IIRC) does work. Unfortunately, it's from Nov 2017.

[SamuriHL]

8 bit is fine for UHD. With madvr and a good dithering algorithm choice, you won't notice any difference whatsoever. A bunch of us use 8 bit by choice because of banding issues with our LG OLED panels. I'm not (yet) doing a custom res on mine so I can't help there, but, as far as 8 bit goes, it's really not an issue with madvr.

[jasonwc18]

8 bit is fine for UHD. With madvr and a good dithering algorithm choice, you won't notice any difference whatsoever. A bunch of us use 8 bit by choice because of banding issues with our LG OLED panels. I'm not (yet) doing a custom res on mine so I can't help there, but, as far as 8 bit goes, it's really not an issue with madvr.

That's great to hear. I will also using an LG OLED for HDR, so if it's fine on that, 8 bit isn't a problem. I am using Error Diffusion, Option 1 for dithering.

[Asmodian]

What about for native 10 bit sources (4K HDR Blu-Rays)? That was my concern. I assumed it wouldn't matter for 8 bit content.

Even for 10 bit sources. As soon as you send the video to madVR it is converted to 16 bit data (4:2:0 YCbCr -> RGB). During final presentation madVR dithers this to anything from 1 to 10 bit, as configured. The lower the bit depth the higher the noise. The difference between well dithered 8 and 10 bit output is basically undetectable, the increased noise is very subtle. Try comparing 6 bit to 8 bit output to see a stronger version of the effect. 6 bit compared to 8 bit is many times more significant than 8 bit compared to 10 bit but it is still pretty subtle. Dithering is remarkably powerful, another interesting test is to set madVR to 4 bit output and compare ordered dithering to dithering disabled.

It is different for lossily compressed content (e.g. everything we watch), this is because the dithering cannot be completely preserved by the lossy compression. 10 bit is important for HDR blurays on the disc, just not when we are watching them.

Some displays actually look worse when given 10 bit data, even when they do support 10 bit (e.g. LG C7). This is because the internal video processing handles 10 bit worse than 8 bit. Try a blind test, at best most people have to make special test patterns to tell if 10 bit is really working... if you cannot tell whether or not it is working why care if it is?

Use 10 bit if you can and your display supports it properly, it is theoretically better, but do not make any sacrifices to get 10 bit. Also make sure to test it and decide what looks better to you, 10 bit could be worse. :(

[jasonwc18]

Even for 10 bit sources. As soon as you send the video to madVR it is converted to 16 bit data (4:2:0 YCbCr -> RGB). During final presentation madVR dithers this to anything from 1 to 10 bit, as configured. The lower the bit depth the higher the noise. The difference between well dithered 8 and 10 bit output is basically undetectable, the increased noise is very subtle. Try comparing 6 bit to 8 bit output to see a stronger version of the effect. 6 bit compared to 8 bit is many times more significant than 8 bit compared to 10 bit but it is still pretty subtle. Dithering is remarkably powerful, another interesting test is to set madVR to 4 bit output and compare ordered dithering to dithering disabled.

It is different for lossily compressed content (e.g. everything we watch), this is because the dithering cannot be completely preserved by the lossy compression. 10 bit is important for HDR blurays on the disc, just not when we are watching them.

Some displays actually look worse when given 10 bit data, even when they do support 10 bit (e.g. LG C7). This is because the internal video processing handles 10 bit worse than 8 bit. Try a blind test, at best most people have to make special test patterns to tell if 10 bit is really working... if you cannot tell whether or not it is working why care if it is?

Use 10 bit if you can and your display supports it properly, it is theoretically better, but do not make any sacrifices to get 10 bit. Also make sure to test it and decide what looks better to you, 10 bit could be worse. :(

Thanks for the detailed explanation. I know that a lot of regular Blu-Rays have noticeable banding, whereas the same sources in 10 bit 4K Blu-Ray do not suffer the same banding. I didn't realize this was a result of compression rather than the bit depth of the raw output.

Moreover, I am likely in a similar situation given that I'll be watching HDR content on an LG OLED with the same video processing issue. In contrast, my JVC RS600 will handle 12 bit color just fine, but it's not bright enough to really enjoy HDR.

If I understand your post correctly, I should tell madvr to dither to 8 bit so that the NVIDIA driver doesn't do any further dithering to convert it to output in 8 bit?

[Asmodian]

If I understand your post correctly, I should tell madvr to dither to 8 bit so that the NVIDIA driver doesn't do any further dithering to convert it to output in 8 bit?

Good point. Definitely. Double dithering will have higher noise and I like madVR's dithering more.

[SamuriHL]

Yup exactly that. The less the driver does to the output on the way to the display the better.

Sent from my SM-G975U using Tapatalk

[alps006]

Played around with the numbers under the setting "apply target dynamic nits selection", and no matter what I changed, I just felt the brightness was lacking and the picture looked a bit dull. eventually, I unchecked it, voila!!! About 20~30% more brightness and the picture looked great! In theory, should I leave it checked or unchecked? I prefer the latter. Thank you!

[Warner306]

Leave it unchecked if you prefer brightness over everything else. The tradeoff is that you will clip the specular highlights as they appear. It is HDR. You need contrast to make it look accurate.

Lowering the dynamic tuning value will cause the targets to be lower and the image will get brighter as a result. But it won't be as bright as using the static display peak you entered.

[tp4tissue]

Given light of the banding issues introduced in windows 10 beyond 1607, have you guys gone back and retested those oleds ? maybe it's window's problem.

[ryrynz]

Dunno bout the issues with earlier versions but MS is investigating the banding issues reported with 1903. Once that's fixed and maybe some conclusive evidence on the cause of various latency issues I'll update.

[Asmodian]

Given light of the banding issues introduced in windows 10 beyond 1607

It wasn't just beyond 1607, it was on 1903 specifically and the OLED testing was not done with 1903 but with 1803 or 1809, or earlier. :p

Do you know about a banding issue other than the one introduced in 1903?

Edit: I did compare Windowed Overlay with FSE and Fullscreen Windowed on my C7 when I first got it, on 1703 I believe, and they all showed the same banding. Windowed Overlay bypasses the current issue on 1903 so I don't think the banding issues on the C7 (or C9) were caused by Windows. Windows has a new issue which adds some new banding but LG's OLEDs do have some banding on their own. The 10 bit issues on the C7 are worse and manifested when switching between 8 and 10 bit Windowed Fullscreen (or FSE) so also do not seem like they could have been related to the current banding issue.

[tp4tissue]

It wasn't just beyond 1607, it was on 1903 specifically and the OLED testing was not done with 1903 but with 1803 or 1809, or earlier. :p

Do you know about a banding issue other than the one introduced in 1903?


That's exactly what I'm talking about, apparently dithering is disabled on nvidia by default. This caused banding issues with people who used monitor corrections.

They've figured out how to enable the dithering, but only unreliably in all versions POST 1607.

So it's either 1607 or Windows 7 for permanently enabling dithering.

How does this affect Madvr, or does it affect Madvr, I Don't Know.

https://hub.displaycal.net/forums/topic/how-to-enable-dithering-on-nvidia-geforce-with-windows-os/

[Asmodian]

That does not impact madVR at all, Nvidia should not be dithering when using madVR. This is what were were just discussing above. :p

Edit: I was using the TV's two point white balance and madVR's 3DLUT for all color correction. I also tested with the TV's color correction disabled, just to see if it was to blame, but that had no impact on the banding. I have been unable to get good results with an ICC profile for a while, it might have been after 1603 to be honest but I hadn't connected it to the dithering. :o

[huhn]

PC monitors that allow 10 bit input get usually a very good score on rtings while TV doesn't have anything close to that including LCD here. OLED just got more known for this issue because they even produce some banding with 8 bit input which is rare on LCDs.

banding with 10 bit output is a common issue on TVs it's sad because we know from gaming monitors which have very similar tech it is possible to get really good results. which is even more funny because games usually don't dither so they end up with banding anyway.

[Megalith]

The dithering is only an issue if you are using an ICC Profile, correct?

[Asmodian]

Correct

[hannes69]

some conclusive evidence on the cause of various latency issues
Do you refer to the ntoskrnl latency spikes in 1903 or something else?
I have these spikes higher than everything I´ve seen in the net, once up to 60 ms (yes, ms not µs) and since 1903 I have often repeated frames (let´s say 5-10 during one movie) when I had zero all the time in 1809. Sometimes no drops or repeats, sometimes repeats and the audio clock goes wacky, sometimes a repeat followed by a drop in a short time and so both numbers rising slowly, sometimes 50 drops and/or repeats at once, sometimes presentation glitches. Absolutely none of these symptoms in 1809.
I never had problems with Windows updates, so I simply applied them. So this time. And of course the Windows.old folder doesn´t exist anymore...
Of course I don´t know if my problems really have to do with the latency problems.
Maybe it has to do with Windows clocks. Since 1809 the default clock is a 10 MHz clock. I used HPET before and it worked, now it is almost a guarantee for my described problems, so to speak the propability for appearing is much more higher than using the default clock.
Sometimes the audio clock ('clock deviation' in madVR OSD) jumps to a different value during playback and stays there, sometimes this repeats multiple times during playback. Normally I have a value in the region of -0.00220%. Then a repeat is shown and the clock jumps to a different value, let´s say -0.00310%. And this is not only shown, it is really the case: The drop/repeat time is adapted and to the predicted time a repeat occurs (shown in OSD and really the case).
The video clock doesn´t seem to be affected, this is always stable.
All of these problems can not be solved by any madVR settings (rendering settings). I have custom resolutions which are 'perfect'. The problems also show up with smooth motion.
Different GPU drivers don´t change anything. It is not dependant on GPU load. I have two audio devices (PCI card and onboard sound), no change. I tried many things, nothing worked. The culprit really seems to be the 1903 Windows update in my case.
It´s a wonder to me that nobody else reported problems in this thread here. Maybe I am in the minority of people that made this mistake to upgrade to 1903?
So I´d like to warn from updating to 1903! The first time I had problems with such an update and I regret this step the first time.

[Stereodude]

I thought Windows 8.1 was the preferred HTPC OS for madVR. What do you need Windows 10 for?

[el Filou]

Can't we get past that question already?
Some reasons:
- some people don't have a dedicated HTPC but still want to use madVR, and Windows 8 means being stuck in the past when it comes to general purpose computing (also the UI is awful but that's just an opinion)
- newer hardware isn't always supported on/optimized for Windows 8

[XMonarchY]

Is there any kind of development for madVR going on at the moment?

[SamuriHL]

madshi is currently working on the Envy. For the very moment work seems to have stopped on the HDR builds but he did say he'll get back to them soonish. I suspect getting the Envy launched is quite time consuming.

[Stereodude]

- some people don't have a dedicated HTPC but still want to use madVR, and Windows 8 means being stuck in the past when it comes to general purpose computing (also the UI is awful but that's just an opinion)
OpenShell makes them pretty much the same, and I did say HTPC OS in my post. I didn't say all around general purpose OS that you also use for media playback.
- newer hardware isn't always supported on/optimized for Windows 8
Unless I missed something they use the same drivers.

[chros]

Unless I missed something they use the same drivers.

8 months ago when I put together my HTPC I looked around whether I can use Win 8 with ryzen CPUs and b450 motherboards: there was only 1 (!) guy that mentioned that he managed to force somehow the chipset driver to install it on Win8. So I decided to go on the Win10 route.

[hannes69]

What do you need Windows 10 for?
You can work with Windows 95 for many today´s tasks or you can use Linux or you can use MacOS. Windows 10 is the current OS on Win platforms. Maybe the last with its update structure. It´s a matter of time you´ll have to use Windows 10, support for Windows 7 ends soon. And Windows 8 never really was a wide spread OS.
My mistake (in my opinion) was not to use Windows 10 but not to wait for enough feedback about the current update 1903. But - I never really had bigger problems with Windows XP, not with Windows 7 and not with Windows 10 including 1809 regarding HTPC usage. So I personally saw no risk to update.
I still can enjoy movies. 5 frame repeats during one movie is not amusing out of a perfectionist´s view, but on the other side we´re talking about 5 frame repeats, this is not the end of the world :)

I did say HTPC OS in my post. I didn't say all around general purpose OS that you also use for media playback.
We´re talking about Windows consumer systems. All of these are NOT real-time operating systems, so all of them can be considered a compromise and all of them are more or less suited the same way for HTPC usage.
You have rendering settings in madVR so you can make some adjustments depending on OS, GPU and other hardware and software factors. Up till now I always managed 'perfect' video playback. And now the first time I can´t really work around it. One case in so many years. I won´t complain ;)
Windows 10 is a kind of update to Windows 8 and Windows 10 itself is further updated.
I never had big problems with Win 10 so I never will go the step back to Windows 8 (I never used this OS).
Fell free to consider Win 8 a 'HTPC OS' (ridiculous) and Win 10 an 'all purpose OS' (ridiculous as well).

My intention was to warn from some Win 10 1903 problems - not to discuss what OS to use.
And like very very often mentioned in this thread - don´t use arguments like 'you must', 'you have to', 'this is right', 'this is wrong' and things like that. Like upscaling algorithms or HDR settings. We´re talking about personal preferences, not about the 'right' settings. If everything is 100% clear and determined, madVR wouldn´t even have a settings dialogue.
I prefer Win 10 and I´ll have to work with the given possibilities. If the problems are not gone with further updates or latest with 1909, I´ll have to make a fresh install of Win 10 and update to 1809. Again not the end of the world, only some work for a couple of hours.

[chros]

I prefer Win 10 and I´ll have to work with the given possibilities. If the problems are not gone with further updates or latest with 1909, I´ll have to make a fresh install of Win 10 and update to 1809. Again not the end of the world, only some work for a couple of hours.
Although that's true, but exactly that's why I've chosen LTSB/LTSC: I don't have time/energy/etc. to try to figure out and fix all the issues that can happen after a big upgrade (and sometimes only with security fixes as well), and there were reports before as well. I just want to use the PC that I have set up once, not constantly hacking :)

[Stereodude]

Fell free to consider Win 8 a 'HTPC OS' (ridiculous) and Win 10 an 'all purpose OS' (ridiculous as well).
Reading comprehension isn't your strong suit is it? I didn't say Windows 8.1 was a HTPC OS in the sense that you're trying to imply. I asked about using it vs Windows 10 as the OS on a PC that's only used as a HTPC with madVR. As such how it handles general purpose tasks is irrelevant.

You've posted a lot and still haven't provided any actual video playback features that are missing with Windows 8.1 from madVR's capabilities that need Windows 10. So, there aren't any?

[tp4tissue]

If a movie's HDR doesn't seem to peak above 150nit, Then setting the TV + Madvr to 150 nit, and using a 150nit 3Dlut would be better right ? Because then you have the slightly extended range of blacks for better contrast ?

This is on a VA-tv w/ 6500:1 contrast ratio. Am I correct in assuming this is how it'd work ?

As in the higher you set the TV, the brighter the black lvl, and if the peak range is not part of the movie, it just makes everything more grey/less black than is possible ?

[jkauff]

You've posted a lot and still haven't provided any actual video playback features that are missing with Windows 8.1 from madVR's capabilities that need Windows 10. So, there aren't any?
madshi once recommended Win 8.1 over Win 10 for madVR, but IIRC that was over a year ago. That's a couple of major updates ago, so I don't know if he feels the same way now.

I reluctantly moved on from 8.1 a couple of years ago, and 10 has given me no problems. I feel much more secure using the latest version of Windows because important security changes have been made. If I used 8.1 only on a dedicated HTPC not connected to the internet, I wouldn't bother upgrading.

I have no idea if madshi's recent work in the world of HDR makes use of any Win 10-specific capabilities, but you're quite right that with the current madVR release Win 10 adds nothing over 8.1.

[hannes69]

Reading comprehension isn't your strong suit is it? I didn't say Windows 8.1 was a HTPC OS in the sense that you're trying to imply.
-> "I thought Windows 8.1 was the preferred HTPC OS for madVR."
Ok. You 'thought' something. And 'preferred'. I´m thinking many things too. And I know, some people (including madshi) prefer Windows 8 / 8.1. I prefer Windows 10. Like I said - preferences.

You've posted a lot and still haven't provided any actual video playback features that are missing with Windows 8.1 from madVR's capabilities that need Windows 10. So, there aren't any?
In my opinion you can use Windows 7, Windows 8 or Windows 10 for a HTPC. I never used Windows 8, but 7 and 10. And I always could use all madVR features that I wanted to use.
I don´t think that something is missing in Windows 8.1 and I never claimed something like that.
In my personal setup I came across problems with Windows 10 1903. If I want to eliminate those problems at this moment, I can simply revert to Windows 10 1809, I personally don´t have to revert to Windows 8.1.
In my setup I don´t have any problems with Windows 10 1809, so I can say that Windows 10 1809 is a working OS for my setup.
So for me I can´t say that 8.1 is something preferred or 'better' than 10 because what is better than having no problems?
It´s the same matter like many people stick to a GPU driver that they experience as working/flawless for them. My fault was that I didn´t stick with 1809. That has nothing to do with a general 8 vs. 10 debate.
So now I´ve posted a lot again and 'provided' my opinion. I can definitely live with your opinion (why not) maybe you can live with mine :)

[huhn]

windows 8 is recommended for technical reasons.
because you don't notice the technical regression doesn't mean they are not there.

[Wull]

Hi.

I've been using madVR 'SDR' for a few years now. I recently got a projector that can also do HDR. I have the projector configured for both SDR & HDR formats. So I would like to know how I go about setting up profiles within madVR. I've found post that explains how to set up for resolutions profiles so that box is ticked. I would like to create a 'Calibration' profile to switch between HDR and SDR 'BT.709/BT.2020’. Is this possible?

[Alexkral]

If a movie's HDR doesn't seem to peak above 150nit, Then setting the TV + Madvr to 150 nit, and using a 150nit 3Dlut would be better right ? Because then you have the slightly extended range of blacks for better contrast ?

This is on a VA-tv w/ 6500:1 contrast ratio. Am I correct in assuming this is how it'd work ?

As in the higher you set the TV, the brighter the black lvl, and if the peak range is not part of the movie, it just makes everything more grey/less black than is possible ?

That's right, with a movie that peaks so low is best to preserve the blacks, as long as your TV has a sufficient contrast ratio. Increasing blacks also causes noise to appear that otherwise remains hidden.

[mclingo]

it made sense to move from 8 to 10 at the time as it was a free upgrade with a limited time span or so we were told, this was a bit of a con as you can still upgrade from win 7 / 8 free although Microsoft arent shouting this from the rooftops, about a month ago i had an old laptop on win7, i decided to run the win10 update activation and it worked, I now have a free win10 license for that machine showing on my MS account.

although once you've got the license you could do a clean win8 install but who could be bothered when everything seemed to be working. Problems only really started with 1803, 1709 was fine, AMD cards have been mostly fine throughout though, most issues ive had were just bad luck or user error, everything still works HDR/3D/23,976 frame drops still into days even with 3D.

[jkauff]

windows 8 is recommended for technical reasons.
because you don't notice the technical regression doesn't mean they are not there.
Do you have any detailed information on what those issues are? I don't think I've ever seen them posted all together in the thread.

[huhn]

i can only tell a couple out of my head and they depend on the windows version.
FSE is simulated/faked on win 10. this is planned by microsoft and can result in all kinds of issues. they added a new great WFS 10 bit flip presentation but they can't leave there finger of FSE.
WFS 10 bit was broken a couple of times now this is not planned.
1903 just added a new level of banding thanks to yet another WDDM version this is month old.
windows 10 brought back the desktop composition mismatch issue from win 7. this is an extremely old bug and finally acknowledge by nvidia.

[tp4tissue]

That's right, with a movie that peaks so low is best to preserve the blacks, as long as your TV has a sufficient contrast ratio. Increasing blacks also causes noise to appear that otherwise remains hidden.

Awesome, thx for confirming my theory. Dat new Battle Angel. Looks great, even if only ~150nit :D

gamma 2.2 relative w 100% black offset is pretty good at hiding black noise (setting recommended by Florian from dispcal for HDR)

[ryrynz]

You wanna watch the Open Matte release of Alita (https://www.reddit.com/r/alitabattleangel/comments/ccpak9/which_alita_which_aspect_ratio_open_matte_vs/), not sure if it'll ever be released officially.

[brazen1]

Hi.

I've been using madVR 'SDR' for a few years now. I recently got a projector that can also do HDR. I have the projector configured for both SDR & HDR formats. So I would like to know how I go about setting up profiles within madVR. I've found post that explains how to set up for resolutions profiles so that box is ticked. I would like to create a 'Calibration' profile to switch between HDR and SDR 'BT.709/BT.2020’. Is this possible?

Profile group name: DISPLAY
Use this auto select rule:
if (HDR) "BT.2020"
else "BT.709"

One profile name is BT.2020, the other is BT.709 for the calibration portion.

I ticked report BT.2020 to display (nVidia only) for BT.2020 although I can't remember why. Maybe someone knows exactly what that switch is for and can elaborate.

[tp4tissue]

You wanna watch the Open Matte release of Alita (https://www.reddit.com/r/alitabattleangel/comments/ccpak9/which_alita_which_aspect_ratio_open_matte_vs/), not sure if it'll ever be released officially.

Hahaha, major war goin' on in the Alita Threads, IMHO, I'll leave it up to the director to frame his movie. They both look fine to me. If I were myself truly important and non-self-deprecating, I'd opine that saving up the bitrate for a tighter crop is better because of how long the movie is, especially after adding DV track and 10+, if this was a BD100, then it'd go either way.

[Warner306]

Profile group name: DISPLAY
Use this auto select rule:
if (HDR) "BT.2020"
else "BT.709"

One profile name is BT.2020, the other is BT.709 for the calibration portion.

I ticked report BT.2020 to display (nVidia only) for BT.2020 although I can't remember why. Maybe someone knows exactly what that switch is for and can elaborate.

Report BT.2020 should only be needed if you select DCI-P3 in calibration. DCI-P3 sources and displays all follow BT.2020 color coordinates as defined by the ST.2100 UHD standard. If the display doesn't understand a DCI-P3 flag, the input colors might not be displayed with the correct BT.2020 coordinates.

[Wull]

Report BT.2020 should only be needed if you select DCI-P3 in calibration. DCI-P3 sources and displays all follow BT.2020 color coordinates as defined by the ST.2100 UHD standard. If the display doesn't understand a DCI-P3 flag, the input colors might not be displayed with the correct BT.2020 coordinates.



Thanks. My projector is the Epson ls10500. So think setting to DCI-P3 is correct.

What would happen if you select ‘disable calibration controls to this device’?

[chros]

Report BT.2020 should only be needed if you select DCI-P3 in calibration. DCI-P3 sources and displays all follow BT.2020 color coordinates as defined by the ST.2100 UHD standard. If the display doesn't understand a DCI-P3 flag, the input colors might not be displayed with the correct BT.2020 coordinates.
Not with an LG Oled, colors get oversaturated using SDR if you profile the display and it switches bt.2020 mode, so it must be left unticked.

[Wull]

Profile group name: DISPLAY
Use this auto select rule:
if (HDR) "BT.2020"
else "BT.709"

One profile name is BT.2020, the other is BT.709 for the calibration portion.

I ticked report BT.2020 to display (nVidia only) for BT.2020 although I can't remember why. Maybe someone knows exactly what that switch is for and can elaborate.

Thank you.

Does this also apply if I wish to use two 3DLUT files?

[hannes69]

windows 8 is recommended for technical reasons.
because you don't notice the technical regression doesn't mean they are not there.
Yes. But if a problem doesn´t show up for me, it is no problem to me.
E.g. why should a nvidia GPU user care about AMD GPU problems or vice versa?
In Windows 10 certain problems can show up which can´t show up in Windows 8. Ok, so it´s good to recommend Windows 8 in a general way.
On the other side many Windows 10 users don´t have problems. Let´s say 5% of the Windows 10 users have problems, which they wouldn´t have if using Windows 8. Then I´d say: This 5% should downgrade to Windows 8, but the remaining 95% should still use Windows 10.

In my post I simply wanted to point at a personal problem with Windows 10 1903, a hint to maybe delay upgrading for others and the implicit question if someone else experiences similar problems.
Implicit answer: "Your fault, Windows 8 is the better/recommended/right OS for HTPC usage". That´s the point.