madVR - high quality video renderer (GPU assisted)

[leeperry]

Having more thoughts about it, there's also LUT Manager (http://lut-manager.software.informer.com/) that can load and save CLUT data, but I'm cool with Argyll's CLUT being applied in 8bit atm :o

I guess I could merge the .cal file inside the yRGB 3DLUT using that .ti3 parser (http://forum.doom9.org/showthread.php?t=162285), but phewwwww PQ already kills as is and that'd need a truckload of double-checking in order to ensure that everything is processed as it should and I got better things to do atm. I need the CLUT to be applied on the windows desktop when mVR is not using it inside the 3DLUT so that'd make things even more complicated I guess..

[dansrfe]

Why is there more than one gamma ramp mechanism that can be used by the graphics card? The ability to apply profiles on top of each other makes no sense whatsoever, in any case.

[leeperry]

well, dispwin.exe(from Argyll) uses the RAMDAC hardware CLUT AFAIK, and it can do 10bit over VGA. The current "disable gamma ramps" option in mVR doesn't wipe it from my limited testing.

[dansrfe]

well, dispwin.exe(from Argyll) uses the RAMDAC hardware CLUT AFAIK, and it can do 10bit over VGA. The current "disable gamma ramps" option in mVR doesn't wipe it from my limited testing.

So then the disable gamma ramp setting only disable surface level CLUT application mechanisms.

3DLUT is applied to the RAMDAC during madVR playback I believe.

Which beings us back to the question: If someone has calibrated their monitor with a 3DLUT and wants it applied to their desktop in addition to madVR, what should they do?

[cyberbeing]

well, dispwin.exe(from Argyll) uses the RAMDAC hardware CLUT AFAIK
Only programs with special low-level system drivers like Rivatuner can modify the RAMDAC directly, and there really is no good reason to do this unless you have an ancient GPU with doesn't support CLUT adjustments normally. argyllcms dispwin and other lut loaders uses the standard Windows api for loading the CLUT onto the GPU. Maybe the method madVR uses for resetting the CLUT just doesn't work on WinXP?

Edit: It appears that you need to restart madVR before any change to the "disable GPU gamma ramps" option becomes effective.

Which beings us back to the question: If someone has calibrated their monitor with a 3DLUT and wants it applied to their desktop in addition to madVR, what should they do?
yCMS 3DLUTs cannot be used outside of madVR, and other applications which choose to support the 3DLUT format.

On the desktop, you would use a calibrated gamma ramp from an ICC profile, which won't offer gamut correction outside ICC color manged applications.

[dansrfe]

So before the "disable gamma ramps" option existed in madVR what was going on if someone had an ICC profile installed via Windows 7 and a 3DLUT loaded into yCMS via madVR?

[baii]

I have a question regarding which will give better PQ.
set up -i7 sandy 2670qm, m8900 (sort of a desktop 6850m)
content - 1080i -> 2560*1440p
Situation is either
1.Anything +AR but Jinc3(even w.o AR) in chroma/upscale + GPU deinterlacing(either auto or all the way forced vector adaptive)
2.Any algorithum with AR + yadif/software deinterlacing

So the question really is : do gpu deinterlacing worth dropping jinc3?

[mzso]

Chroma is upscaled, because it's stored at half-resolution in YV12.

I said image upscaling, I didn't change chroma. That's why it's weird.

[TheElix]

[code]madVR v0.84.3

* added media player screenshot functionality (IBasicVideo::GetCurrentImage)I can't believe it!!! Thank you!
Edited: Er... How does it work?

[cyberbeing]

So before the "disable gamma ramps" option existed in madVR what was going on if someone had an ICC profile installed via Windows 7 and a 3DLUT loaded into yCMS via madVR?

You would take measurements for yCMS 3DLUT after you've created and loaded the calibrated gamma ramp from an ICC profile. Alternatively, you could re-use measurements taken during ICC profiling.

The 3DLUT would be used for performing gamut corrections, and optionally fine-tuning the whitepoint and gamma via shaders.
The GPU gamma ramp would be applied on top as the blunt of the gamma and whitepoint correction needed for your display.

[Toku]

I noticed that in newer versions of MPC-HC, the seek bar has little black bars which show where each chapter begins/ends. Having these in the seek bar is really useful when playing a video with multiple sections (Advert breaks/Opening/Ending etc) Do you think you could add a feature like this into the Seekbar for Fullscreen exclusive mode?

[6233638]

I can't believe it!!! Thank you!
Edited: Er... How does it work?In MPC-HC, there is a "Save Image" command (default: Alt + I) and a "Save Image (Auto)" command (default: F5)

You should save at least one image with the Alt + I command to set the destination folder and image type. (it defaults to a low quality JPG, I set it to PNG) and after that, hitting F5 should save to that directory with the type of image you selected.

Note: this saves an unscaled screenshot.

As far as I know you don't need more than 10000:1. At any moment the human eye can't perceive more. The fact that the eye can adapt to low light conditions is irrelevant because it takes like a half hour.The human eye has a limited range of contrast it can see simultaneously - about 100:1, but that shifts up and down in brightness constantly over a dynamic range of about 1,000,000:1. (similar to how exposure works on a camera if you are familiar with that)

So if you are showing a bright image on a display, black level almost doesn't matter, because it is below the threshold of what your eye can see simultaneously. (your eye tends to "expose" based on the brightest object)

If you are watching a dark film in a dark room, then a display with 10,000:1 contrast (5,000:1 once calibrated) is nowhere near enough to put black level below the threshold of what your eye can detect.

You need in excess of 100,000:1 contrast at calibrated levels (100cd/m² white) before the screen stops "glowing" when displaying black. The eye is very good at detecting the contrast between a dark screen, and the total darkness of the room.
Samsung announced that their OLED has 150,000:1 at 600cd/m² peak white, which puts it at only 25,000:1 once calibrated (assuming their numbers are accurate) because OLED is like Plasma where lowering peak brightness has no impact on black level unlike LCD. (with LCD, lowering the backlight lowers both peak brightness and black level)

With projectors, the reference level is only 48cd/m² which means they actually require even higher contrast ratios for the same black level perception. (I actually find 48 a lot more comfortable on a flat panel in a dark room as well)

This is why it's disappointing that even though JVC have projectors with a 130,000:1 native contrast ratio, they still refuse to implement a dynamic iris. I have not seen the very latest X95 projector, but their previous 90,000:1 CR projectors were still not enough to stop black "glowing" in a dark room. If they implemented a dynamic iris in addition to having such a high native contrast ratio, I bet it would be able to push black level below the limit of human perception in all but the darkest scenes.

Hopefully this will change once laser/LED sources are used in HT projectors, as you can adjust the brightness far better than a dynamic iris allows. (though I feel that Sony already have a very good iris implementation that is transparent in most cases now)

[ryrynz]

Note: this saves an unscaled screenshot.


Which at times may not be useful as what you may wish to capture is the scaling. :D

I just set up a shortcut key for automatic FSE mode mode disable/enable & or the 10 seconds options use them when required and hit Print screen.

[mindbomb]

I think he is having trouble cause he is using the stable build of mpc hc, which doesnt allow you to take screenshots with madvr.

you have to use a nightly.

[THX-UltraII]

Hi guys, just a little OT. I want to know if my 'chain' is configured the correct way so the colors and blacks&whites are displayed correct:


MY SOURCE (HTPC) settings:
- NVIDIA graphics card with latest driver and I use the HDMI output of my card.

- Media Player Classic with madVR as output renderer with output setting PC Levels (0-255).

- using LAV video decoder with all the 'Output Formats' checked and 'RGB Output Levels' set to 'Untouched (as input)'.

- I m also using ffdshow Raw Video Decoder: Raw Video to 'All Supported' and in the Output settings only checked the box 'YV12'.

MY DISPLAY DEVICE (JVC RS55 projector) settings:
- Color Profile
The manual of my projector says I have to choose a profile here that suits the input source. A have a few settings I can choose here (I will quote the manual). Which is the correct one to choose?? (looking at the content I m watching*) *I think it is also important to mention the content I m running. I m running only a few different types of content. Full Blu-Ray movies (BDMV structure folder or .m2ts files) and .mov trailers from HDtrailers.net
1. Standard
This is a HDTV profile with an especially rich representation of the film-specific colors
2. Cinema1
This is a profile that resembles the color space of the DCI standard
3. Cinema2
This is a profile that resembles the color space of HDTV

- HDMI Color Space Input
I can choose 'Y Pb/Cb', 'Pr/Cr' or 'RGB' here. I assume I have to choose RBG?

- HDMI dynamic range Input
I can choose 'Standard (16-235)', 'Enhanced (0-255)' or 'Super White' here. I think I have to use 'Enhanced (0-255)' but what s the 'Super White' option for? (I quote the manual about the explanation of the Super White option: ''It is set if the dynamic range of the input video scale level is 16-255. Please set the output to video equipment compatible with Super White for Super White-enabled DVD / BR etc.''



Thanks for all input!

[TheElix]

I think he is having trouble cause he is using the stable build of mpc hc, which doesnt allow you to take screenshots with madvr.

you have to use a nightly.
Thanks! This was most useful.

[vlatko27]

Hi all, I followed this guide (http://imouto.my/watching-h264-videos-using-compute-unified-device-architecture-cuda/) to the letter. I think I got everything working properly.

My plasma(Panasonic G10) is hooked to the GTX660 via HDMI cable. The GPU is outputting 0-255 to the TV and madVR is set to 16-235(which is the only colorspace my TV supports).

Most movies play perfectly fine, however some files require me to change the colorspace to 0-255(even though my TV doesn't support it) in madVR, otherwise the picture is too bright, washed out...

Here's a clip (http://www.mediafire.com/?wongyo7qorm4auf) of one of those video files. I'm just curious as to why this happens with some files.

[Keiyakusha]

Hi all, I followed this guide (http://imouto.my/watching-h264-videos-using-compute-unified-device-architecture-cuda/) to the letter. I think I got everything working properly.

My plasma(Panasonic G10) is hooked to the GTX660 via HDMI cable. The GPU is outputting 0-255 to the TV and madVR is set to 16-235(which is the only colorspace my TV supports).

Most movies play perfectly fine, however some files require me to change the colorspace to 0-255(even though my TV doesn't support it) in madVR, otherwise the picture is too bright, washed out...

Here's a clip (http://www.mediafire.com/?wongyo7qorm4auf) of one of those video files. I'm just curious as to why this happens with some files.
I don't see anything wrong with sample you provided. Maybe if you stop using shitty guides, things will improve. Especially this (http://naruto.anime.my/img/tutorial/MPCHCv1/step2part07.png) recommendation looks pretty scary to me.

[kopija]

Most movies play perfectly fine, however some files require me to change the colorspace to 0-255(even though my TV doesn't support it) in madVR, otherwise the picture is too bright, washed out...

Here's a clip (http://www.mediafire.com/?wongyo7qorm4auf) of one of those video files. I'm just curious as to why this happens with some files.

Are the problematic files in SD resolution by any chance?
If so, try going into Nvidia control panel and change the colorspace there also.
See here (http://forum.doom9.org/showthread.php?t=143689) for the whole story, and chech out the black level test patterns and try them out.

[MSL_DK]

In that case I'd recommend to tell madVR that your display is not calibrated yet. You can do this by telling madVR to disable the calibration controls. Then after you've calibrated your display by using your display's setup menu, you can tell madVR that your display is already calibrated and how you calibrated it. That will allow you to change gamma curves/values through the madVR controls, without damaging your calibration. As the first step of the calibration you should make sure that GPU and madVR RGB output levels are set correctly, by checking black and white levels with a test pattern.

Thanks for your reply :-)

I finally understood why so many do not recommend using htpc as a source to calibrate.

If I choose to use ycms, is it correct understood that ycms values ​​should be taken from an already calibrated monitor .. A monitor that is calibrated using a blu-ray player?

[vlatko27]

I don't see anything wrong with sample you provided. Maybe if you stop using shitty guides, things will improve. Especially this (http://naruto.anime.my/img/tutorial/MPCHCv1/step2part07.png) recommendation looks pretty scary to me.
Well would you mind sharing a non-shitty guide? That guide seems to be very popular so I followed it.
Are the problematic files in SD resolution by any chance?
If so, try going into Nvidia control panel and change the colorspace there also.
See here (http://forum.doom9.org/showthread.php?t=143689) for the whole story, and chech out the black level test patterns and try them out.
No, the files 1080p HD. I watch HD in 99% of the cases.

In nVidia CP I set the colorspace to RGB Full 0-255 so the GPU doesn't do any conversions, but leaves that to madVR(which is something Mr. madshi has always insisted on).

I pass the test patterns (http://www.avsforum.com/t/948496/avs-hd-709-blu-ray-mp4-calibration)(black and white clipping) normally, but like I said some files(though they are a minority) require me to change the colorspace in madVR to 0-255 which doesn't make sense, as my TV doesn't support full range.

[Keiyakusha]

Well would you mind sharing a non-shitty guide? That guide seems to be very popular so I followed it.
Yes, I know that it is popular. I noticed this by amount of users than come to forum like this one after following that guide and ask questions similar to yours. I can't recommend guide as I don't use any not that i see any need in one. Starting from basic setup like having only LAV filters, madvr and MPC-HC is always preferable. Do so, if you don't mind advices. When you sure that it is working and you really have full control of its results, you can extend it by adding something like realtime debanding. Speaking of, that guide seems to be focused on "quality", but it recommends broken debanding from previous century. That's not talking about things that just useless.
I don't think any advanced user or developer on this forum actually followed that guide so its hard to provide support. That guide is pretty messy. With that setup there is tons of places where the problem you describing can happen. This may be related to ffdshow raw filter.

[NicolasRobidoux]

FWIW, I've also found other cases where sigmoidization wasn't working too well. I don't have time to double check right now, but I *think* this image also made problems with sigmoidization:

http://madshi.net/colorsrc.pngMathias: Thank you.
Kind of looks like halftone to me. Will check.

[NicolasRobidoux]

Yeah: Basically it's digital halftoning. Makes sense that only linear light would manage.

[leeperry]

Having more thoughts about it, it's true that the ability to set automatic rules based on resolution & fps to change the rescaling algorithms would be most welcome...coz quite frankly, even my 8800GS can do full Jinc3 AR for both chroma & luma when upscaling SD>1080p and Jinc3 AR chroma upscale on native BD files....720p encodes have gone through nasty non-AR downscaling in Avisynth anyway, and 1440x1080 streams aren't that common.

The 650Ti is bottlenecked by its 128bit memory controller and the more it goes, the less the vanilla 660(195€ shipped) makes sense against the 660Ti(240€ shipped atm)....and let's not mention the 660GS that has become pointless. That's a bunch of money for some videophool upscaling, hah(I'm trying to convince myself here :D)

FWIW, Kazuya made screenshots comparisons between Spline3 AR and Jinc3 AR on a 720p to 1080p conversion and the difference is invisible....so the bang/bucks ratio might be (quite/very/maybe not) low, when OTOH it looks killer fosho when going SD>1080p :)

[vlatko27]

Yes, I know that it is popular. I noticed this by amount of users than come to forum like this one after following that guide and ask questions similar to yours. I can't recommend guide as I don't use any not that i see any need in one. Starting from basic setup like having only LAV filters, madvr and MPC-HC is always preferable. Do so, if you don't mind advices. When you sure that it is working and you really have full control of its results, you can extend it by adding something like realtime debanding. Speaking of, that guide seems to be focused on "quality", but it recommends broken debanding from previous century. That's not talking about things that just useless.
I don't think any advanced user or developer on this forum actually followed that guide so its hard to provide support. That guide is pretty messy. With that setup there is tons of places where the problem you describing can happen. This may be related to ffdshow raw filter.
Well I took your advice and started from scratch...literally.

Fresh install of Win 7 > nVidia Drivers > MPC-HC > madVR.

Same thing.

The only thing that seems to solve all issues, for every video file, is setting the Digital Color Format to YCbCr444 instead of RGB under nVidia Adjsut Desktop Color Settings.

[Yoshi8765]

What exactly you want to hear? Here are some facts for you:
- madvr doesn't support native dxva
- dxva doesn't brings anything good (its not bad either, so lets call it useless waste of time).
- that guide you linked talks about different type of dxva. that one doesn't needs to be supported by renderer in any way. It is a feature of LAV video decoder.
- this guide maybe good in terms of providing results that do work, but its makes you do pretty complicated setup. and many things it suggests only needed to work around user's lack of knowledge and possible problems he can face. You supposed to read it and do exactly as it says. But don't try to understand it, because its like reading the book from end to beginning - at some point you'll figure out the story, but its not easy to follow.

Hmm I see. Basically, what you're saying is, it's too much to explain and I wouldn't get it either, right? That's completely fine with me, to be honest. Thanks for responding.
But I just want a yes or no question to this: MPC-HC shows DXVA as off when using madVR. But from your explanation, I'm guessing LAV filters control that, so I can ignore what MPC-HC says, right?

[Asmodian]

In nVidia CP I set the colorspace to RGB Full 0-255 so the GPU doesn't do any conversions, but leaves that to madVR(which is something Mr. madshi has always insed on).

...as my TV doesn't support full range.

If your TV doesn't support full range I am pretty sure you should not set full range in the nVidia CP. I think madshi always recommends full range if you can. If you cannot use full range use limited range in both MadVR and Nvidia CP.

[HauntingShock]

http://madshi.net/madVR.zip

[code]madVR v0.84.3

* added media player screenshot functionality (IBasicVideo::GetCurrentImage)


How come I couldn't save a screenshot? I'm using MPC-HC.

[huhn]

you need a new version

http://xhmikosr.1f0.de/mpc-hc/

[vlatko27]

If your TV doesn't support full range I am pretty sure you should not set full range in the nVidia CP. I think madshi always recommends full range if you can. If you cannot use full range use limited range in both MadVR and Nvidia CP.

Are you sure mate?


For best quality you should force NVidia to use full range and then you need to use the matching options (either full or limited) in both your display and madVR.


The setting in the Nvidia control panel controls the video output range (a setting which has no effect with madVR) it does not control what levels the card is outputting.

If you have an HDTV which can only accept 16–235, and you plan on using it for more than just video playback, you're stuck with the graphics card scaling the levels.

If you only use the connected PC for video playback, I would recommend forcing 0–255 via the registry "hack" and setting madVR's output levels to TV levels. This means that the graphics card will not be touching the levels, which should avoid introducing banding into the image. It should also mean that BTB and WTW information is visible by adjusting the brightness/contrast on your TV. (but BTB should not be visible with your display calibrated anyway) It does, however, mean that the desktop will look terrible with everything below 16 and above 235 being clipped. That's why I would only recommend you do this if you are only ever going to use the PC for video playback.


If you have the option of 16–235 or 0–255, you are best off sending 0–255 to the display (may or may not require the registry "hack"—the two Sony LCDs here do not) and having madVR set to output PC levels (0–255) which will scale the levels with a high degree of precision.


You never want to be outputting YCC from a PC, always RGB.

[Keiyakusha]

But I just want a yes or no question to this: MPC-HC shows DXVA as off when using madVR. But from your explanation, I'm guessing LAV filters control that, so I can ignore what MPC-HC says, right?
Yes you can ignore it.

[Vyral]

Hi madshi.
I've updated Catalyst drivers from 12.8 to 12.10 and now I have a huge amount of dropped and delayed frames with all algorithms.
The only change I've noticed is the render queue :
With Catalyst from 12.8, the render queue was between 5 and 7 /8
With Catalyst from 12.10, the render queue is now between 3 and 5 /8.

[ryrynz]

Vyral, play with your flushing settings, perhaps try no flushing on all steps for starters. Also is this with FSE mode or Windowed mode?

[asubert]

I just move to madvr and HD content are beautiful. I still havr some dvd and it looks like madvr is not able to render. I have a macrovision error. I foind some fix on the net by replacing a dll, but it is not sure it is still working.

Any chance to have a fix. For the time being, i use evr for dvd.

[Vyral]

Vyral, play with your flushing settings, perhaps try no flushing on all steps for starters. Also is this with FSE mode or Windowed mode?

Windowed mode.
I'll try no flushing on all steps later.
What surprised me is that I didn't change anything in the settings.

Edit : I tried the option "don't flush" on all steps but the problem is still here.

[TheLion]

Windowed mode.
I'll try no flushing on all steps later.
What surprised me is that I didn't change anything in the settings.

Edit : I tried the option "don't flush" on all steps but the problem is still here.

Check and double check if any options/defaults in the driver were activated by the update.

I updated from 12.8 to 12.11 beta with my 5870 and it works great.

[Asmodian]

Are you sure mate?

Well, no, and I guess madishi is worried about the drivers messing with the video signal if set to 16-235. I am not sure what they might do to it. It should be easy to test. If you are sometimes getting gray blacks that sounds like a double conversion, a limited range video getting processed as if it was 0-255 getting converted to 16-235.

I would trust madishi's advice over mine (if I were you) but he cannot know all possible situations. :)

[Vyral]

Check and double check if any options/defaults in the driver were activated by the update.

I updated from 12.8 to 12.11 beta with my 5870 and it works great.

I've checked all options in Catalyst Control Center but all settings are the same as they were before.
Maybe the drivers are just broken.

[ryrynz]

Try uninstalling, reboot and reinstall fresh. Also do you have the same issue in Fullscreen Exclusive mode?

[TheLion]

I've checked all options in Catalyst Control Center but all settings are the same as they were before.
Maybe the drivers are just broken.

Try 12.11 beta drivers.

[6233638]

I just move to madvr and HD content are beautiful. I still havr some dvd and it looks like madvr is not able to render. I have a macrovision error. I foind some fix on the net by replacing a dll, but it is not sure it is still working.

Any chance to have a fix. For the time being, i use evr for dvd.dslibdvdnav (http://sourceforge.net/projects/dslibdvdnav/files/0.2.4.zip/download) should fix this if you are using Windows 7.

Unfortunately, there doesn't seem to be a working "hack" for Windows 8 yet (the tool provided just changes a few registry keys to point to dslibdvdnav) and I have been unable to play DVDs on it since upgrading.

It would be nice if Madshi were able to find the source of the Macrovision errors, especially now that LAV Filters supports DVD decoding, but it seems to be a low priority for him, as he doesn't watch DVD.

For me, DVD is probably 50% of what I watch now, after being Blu-ray exclusive for a number of years. (the rest is probably 25% web, and 25% Blu-ray content) There are a number of titles I own which are probably never going to see a Blu-ray release, or are very low priority for it. These days, there seem to be few archive releases of interest to me on Blu-ray, and the majority of new releases are definitely of no interest to me.

[robpdotcom]

Replacing the qdvd.dll still works to enable DVD playback on Windows 8 ..... at least on the consumer preview.

[6233638]

Replacing the qdvd.dll still works to enable DVD playback on Windows 8 ..... at least on the consumer preview.In Windows 7 you did not have to replace system files to get that working though, you could just use the "Path Hack" tool provided with dslibdvdnav and point it to the XP qdvd.dll

This no longer works on Windows 8. Update: figured out a way to get that working now (http://forum.doom9.org/showpost.php?p=1598268&postcount=189)

Neither dslibdvdnav.ax or the XP qdvd.dll are good solutions though. They don't work with all of my discs, and qdvd.dll has a tendency to crash the player when seeking. (video plays but the player becomes unresponsive)


There was a brief period where ffdshow Video Decoder, LAV Audio + madVR did work with the Windows 7 DVD Navigator, and that worked flawlessly with all the discs that I tried.

[ryrynz]

Perhaps you could fire through some old versions of MadVR and see if you can find the latest one that works in that manner, perhaps Madshi could get that working again in a new build.

[6233638]

Perhaps you could fire through some old versions of MadVR and see if you can find the latest one that works in that manner, perhaps Madshi could get that working again in a new build.It was actually an older version of LAV Audio that seemed to get it working, and I need the downmixing/better format support that newer versions have.

DVDs work fine with renderers other than madVR, so I don't know that the problem lies with LAV, however. (ffdshow audio decoder doesn't work either)

Neither Madshi, nor Nevcariel seem to have any interest in this problem though. (and Nevcariel says that DVDs work on his system)

I did at least figure out (http://forum.doom9.org/showpost.php?p=1598268&postcount=189) how to get the old hacks working on Windows 8, though they don't work nearly as well as the Windows 7 (and presumably 8) DVD Navigator does.

[hdboy]

Hi, I found that by enabling windowed overlay I can get glitch free playback on my secondary monitor (my TV) without having to use D3D full screen exclusive. I dislike FSE due to various drawbacks.

What are disadvantages to using windowed overlay?

Also, when I try to get image capture, MPC still says it's not supported with madVR.

thanks

[ryrynz]

Nevermind for now.

[Asmodian]

What are disadvantages to using windowed overlay?

There is a very small performance hit and it bypasses Windows 7's color management.

[mzso]

The human eye has a limited range of contrast it can see simultaneously - about 100:1, but that shifts up and down in brightness constantly over a dynamic range of about 1,000,000:1. (similar to how exposure works on a camera if you are familiar with that)

So if you are showing a bright image on a display, black level almost doesn't matter, because it is below the threshold of what your eye can see simultaneously. (your eye tends to "expose" based on the brightest object)

If you are watching a dark film in a dark room, then a display with 10,000:1 contrast (5,000:1 once calibrated) is nowhere near enough to put black level below the threshold of what your eye can detect.

You need in excess of 100,000:1 contrast at calibrated levels (100cd/m² white) before the screen stops "glowing" when displaying black. The eye is very good at detecting the contrast between a dark screen, and the total darkness of the room.

I'm sure that's not right. 1000000:1 is only with calculating in rods which takes around a half hour to adapt. I've seen multiple references to 10000:1 though. And now that you mention it's probably not enough with the extremes of environmental light. But I don't think one should expect the screen to be fair well in full daylight and complete darkness. By the way I'm quite fine to use the same settings in darkness as the ones I use in light. With movies anyway, computer desktop not so much.