madVR - high quality video renderer (GPU assisted)

[Andy o]

This is not a gamma problem. If your set is clipping below 16, no gamma setting will bring those levels back, just the same as brightness can't.

Just quickly testing with the gradient test (http://www.lagom.nl/lcd-test/all_noprofile.php#gradient-h.png) at the site provided by QBhd above, I can clearly tell banding when setting CCC to pixel format limited RGB. When using full they're completely smooth. I'm using 11.11 drivers.

[fairchild]

This is not a gamma problem. If your set is clipping below 16, no gamma setting will bring those levels back, just the same as brightness can't.

Just quickly testing with the gradient test (http://www.lagom.nl/lcd-test/all_noprofile.php#gradient-h.png) at the site provided by QBhd above, I can clearly tell banding when setting CCC to pixel format limited RGB. When using full they're completely smooth. I'm using 11.11 drivers.

As I explained, I only brought up gamma because someone else brought it up as a possible source for problems. With Limited RGB, I see all the blocks properly since now the desktop is being expanded to 16-235. When using Full RGB I get no black boxes on that test. (clipping video patterns through MadVR or EVR are proper when using the correct settings for my setup) RGB Limited also shows no visible difference with that test or grayscale ramp video tests with either RGB Limited or RGB Full.... And that test is really not designed for testing video through a renderer.

Different strokes for different folks. (in this case folks=htpc setups) ;)

[QBhd]

Ok, so if the static images still do NOT show levels properly then that means the display is not accepting Full RGB. With that said, you should still have CCC set to Full RGB in Pixel format. But madVR needs to be set to TV Levels.

QB

[Andy o]

With Limited RGB, I see all the blocks properly since now the desktop is being expanded to 16-235. When using Full RGB I get no black boxes on that test. (clipping video patterns through MadVR or EVR are proper when using the correct settings for my setup) RGB Limited also shows no visible difference with that test or grayscale ramp video tests with either RGB Limited or RGB Full.... And that test is really not designed for testing video through a renderer.

Different strokes for different folks. (in this case folks=htpc setups) ;)
It's not as simple as "different strokes" though. The pixel format output affects everything, not just video, so those images are perfectly fine to test for artifacts. Leaving aside banding for a moment, if your TV doesn't accept full RGB, you should not be seeing the same grayscale ramps when you set full or limited RGB. When outputting full RGB pixel format, you should be seeing the ramp crushed and clipped at the edges, whereas with limited RGB output you should be see a more uniform gradient.

That could be a reason why the banding introduced is not as visible to you, but you should see a difference in clipped whites/crushed blacks at least.

Or, something else than your TV simply not accepting full RGB is going on.

Also, the reason I say the issue is not that simple, is because if you're getting a smooth (properly dithered) limited RGB output, it is extremely unlikely that it's just different setups. You have a 5830, I have a 5770. It would be very surprising (and welcome) news to all of us who have been following these pixel format shenanigans for almost two years (http://www.avsforum.com/avs-vb/showthread.php?t=1224697#prob7) now.

[dansrfe]

DXVA deinterlacing bug: When switching displays (applies especially to DVDs) MPC-HC crashes on account of DXVA. I think this is linked to madVR's DXVA auto deinterlacement detection.

[jjames5]

Hi all, i've been using mpc-hc+madvr for a long time with great succes. perfect quality, the frequency matching really nailed the last issues.

But the later versions experience some weird problems here:

I have setup consisting of a thinkpad T500 with a panasonic plasma TV hooked up as secondary display (dvi->hdmi), When a movie starts up fullscreen on the tv and this is switched to exclusive mode, it just displays the first frame and then you hear the audio running. If i then right-click on mpc-hc it brings up the main menu, and the video displays and sort of 'catches up'..
Also if i move the cursor to the thinkpad screen (primary) and activate another window the video will freeze again on the tv. This has been so with the versions from the last month or so. makes it a little hard to use the pc for other things while something is playing...

The 0.79 version of madvr caused massive dropped frames untill i increased the CPU and GPU queue sizes manually??

Right now using madvr 0.79 mpc-hc 1.5.3.3887

best regards
Jesper

[pankov]

fairchild, Andy O,
this Full/Limited RGB having no difference reminded me of a problem in ATI drivers that was present an year or so ago ... when I was still using ATI/AMD card (I've switched to NVIDIA around that time).
Since the problem was/is in the drivers the only thing that I could do to avoid it was using a DVI output instead of HDMI. Luckily my card had two DVI outputs + HDMI + VGA so I was able to connect both my LCD Monitor and my projector (via a DVI-HDMI dongle) to DVI outputs and have real Full RGB output on both.
fairchild, do try this just to be sure that your is really not capable of receiving full RGB.

[Skwelcha]

interesting... i put up the philips TV over DVI this time, i still dont see 0-16 in my test video if i set madvr to 0-255, but i can see all fields in the lagos lcd test picture from 1 onwards. If i set madvr to 16-235 in this configuration i can even see 0-16... same behavior i have when i set the CCC to ycbcr 4:4:4 when its connected over hdmi...

[nevcairiel]

For the record, if your TV/HTPC is properly configured, you are not supposed to see 0-16, because all usual movie content is 16-235.
What madVR does if you set it to 0-255 output is simple - it "expands" the 16-235 input to 0-255, which means all the 0-16 and 235-255 information is lost, but thats OK, as its not supposed to be used in movie content.

[Skwelcha]

what do you mean with properly configurated? i was under the assumption that you shouldnt see the 0-16 with correct brightness settings, but if you raise the birghtness high enough, you should see it at least on test videos. At least this is what some calibration tutorials say, regarless that movies are in 16-235

[QBhd]

what do you mean with properly configurated? i was under the assumption that you shouldnt see the 0-16 with correct brightness settings, but if you raise the birghtness high enough, you should see it at least on test videos. At least this is what some calibration tutorials say, regarless that movies are in 16-235

That only happens if you set madVR's input from TV Levels to PC Levels (Input NOT Output). madVR just assumes the video is TV levels. Also you should not see 0-16 flashing in these test videos if your Black levels are properly set when madVR assumes the video is TV Levels.

QB

[nevcairiel]

what do you mean with properly configurated? i was under the assumption that you shouldnt see the 0-16 with correct brightness settings, but if you raise the birghtness high enough, you should see it at least on test videos. At least this is what some calibration tutorials say, regarless that movies are in 16-235

Calibration tutorials typically talk about usual home entertainment equipment, which sends Limited RGB to your TV (or more likely even YCbCr). If you setup your PC to output Limited, and set your TV to expect it, that would be the same situation - however i would not recommend that approach.

If you output "Extended" or "Full" RGB, you should never see any 0-16 lines when you play a test video with madVR, or something is improperly configured.
You should see 16-235 (i usually can see 17-234, the two extremes are sometimes indistinguishable, and only become visible while losing detail on the other end of the spectrum)

[noee]

Thanks, I've confirmed exactly what you're saying re: Limited vs. Full. I was wrong on my setup using Limited.

[MSL_DK]

what do you mean with properly configurated? i was under the assumption that you shouldnt see the 0-16 with correct brightness settings, but if you raise the birghtness high enough, you should see it at least on test videos. At least this is what some calibration tutorials say, regarless that movies are in 16-235

Read this Calibrate HTPC for optimal video output (http://sunmaiblog.wordpress.com/2010/10/06/calibrate-htpc-for-optimal-video-output/) Think it will eliminate a number of misunderstandings.

[Skwelcha]

doesnt this tutorial come to the same conclusion? it's a tutorial to get BTB & WTW, the same thing i want. But interesting that he cant get it with his 5770, the same series i have... maybe it's the gpu and not the TV in the end...

[QBhd]

I have a 5770, and I can get BTB & WTW, as long as I set the madVR input to PC Levels. This is only done to test, it is not the setting to use for standard playback... so it's not the card

QB

[iSeries]

My current setup is:

LG TV (High black level)
ATI 6450 (Full RGB)
MadVR (PC levels)

I get flashing bars from 17-234 with a test video. 16 is black and 235 is white. Everything that gets fed to MadVR is 'as is' YV12 / NV12.

I was under the impression that this is exactly what I would want, ie I'm not supposed to see anything below 16 or above 235 if it's set up correctly. But reading all this confusion and I don't know any more lol. Seems like no-one else knows either :)

[QBhd]

That's the setup... BTB & WTW are not needed or wanted for video playback. Using 0-255 tests are only to see if your viewing device (TV or Receiver) can accept Full RGB once the signal gets out past the GPU.

[iSeries]

That's the setup... BTB & WTW are not needed or wanted for video playback. Using 0-255 tests are only to see if your viewing device (TV or Receiver) can accept Full RGB once the signal gets out past the GPU.

That's a relief then lol, TV is definitely accepting 0-255 as the gradient test pics at http://www.lagom.nl/lcd-test/all_noprofile.php#gradient-h.png (as linked by Ando o earlier) display correctly.

[Andy o]

That's not a levels test though, that's more like a banding test. But there should be levels tests in the same page.

[MSL_DK]

BTB & WTW are not needed or wanted for video playback.

BTB and WTW is wanted and useful for video playback.

[iSeries]

That's not a levels test though, that's more like a banding test. But there should be levels tests in the same page.

Yep, the levels squares all display correctly too.

@ MSL_DK - please explain further. I was under the impression that commercial blu rays / DVDs are 16-235. What purpose would BTB and WTW serve for video playback?

[MSL_DK]

@ MSL_DK - please explain further. I was under the impression that commercial blu rays / DVDs are 16-235. What purpose would BTB and WTW serve for video playback?

Please read here :)HTPC Blu-Ray essentials By madshi (http://madshi.net/htpc/page3.html)

And here

Calibrate HTPC for optimal video output (http://sunmaiblog.wordpress.com/2010/10/06/calibrate-htpc-for-optimal-video-output/)

[QBhd]

Yes those reads are all good... but that is to help illustrate what madVR does and proof that it's doing what it's designed to do. And also those reads re-enforce the fact that a system should be able to handle the Full Levels for best performance. However if you just play those test videos and you DO see the BTB & WTW then clearly something is wrong. Also if you see NO flashing bars then something is also wrong.

QB

[jmonier]

My current setup is:

LG TV (High black level)
ATI 6450 (Full RGB)
MadVR (PC levels)

I get flashing bars from 17-234 with a test video. 16 is black and 235 is white. Everything that gets fed to MadVR is 'as is' YV12 / NV12.

I was under the impression that this is exactly what I would want, ie I'm not supposed to see anything below 16 or above 235 if it's set up correctly. But reading all this confusion and I don't know any more lol. Seems like no-one else knows either :)

The final result that you state IS what you want, BUT I think you are going through two unneeded conversions (one in madVR and one in the LG TV) to get there. I get the same result with similar equipment with madVR set to TV levels (16-235) and LG set to "Low".

There is a lot of confusion with terminology that is not always consistent. At TV levels madVR outputs the full range of 0-255 with Black at 16 and Ref White at 235. At PC levels it expands 16 to be at 0 and 235 to be at 255. Thus you can see BTB and WTW ONLY with madVR TV levels.

If you set madVR to TV levels you will see the full range of 0-255 (i.e BTB and WTW) with the LG set to 'High'. Then when you set the LG to 'Low', 0-16 will all be black which is what you want.

One more point: I've found that you cannot necessarily adjust with Brightness and Contrast as many calibration guides tell you to do. It depends on the unit. Note that while 16 is black and always should be, 235 is a more arbitrary limit. There is actually chroma information up to 240-244 and the Spears-Munsil Color Clipping test does not display correctly unless you can also see white up to about 244. That's possibly why the LG shows WTW in both High and Low and why my JVC RS-50 projector has a third Super White setting.

One more note: My settings will be correct for video material but will cause clipping of blacks from the desktop. If displaying all the black gradations in the desktop and other non-video material is important then you would have to go with the madVR PC levels with some small degradation in the video (primarily banding, although madVR's dithering may minimize that). And, for most things, you would never notice the difference in the non-video material.

[Asmodian]

That's not it, that's for EVR video (or madVR using DXVA deinterlacing), and some other renderers. There is another setting called pixel format where you can choose between RGB Limited, RGB Full, YCbCr 4:4:4 and YCbCr 4:2:2. That setting controls final output of everything.

Thanks!

After finding this option (I swear CCC didn't have this a few versions ago :o) and understanding that "Black Level Low/High" actually meant "Dynamic Rage Limited/Full" I was able to calibrate my LG-PK750 plasma TV with full range and it looks even better than after I had calibrated it with limited range.

[MSL_DK]

Yes those reads are all good... but that is to help illustrate what madVR does and proof that it's doing what it's designed to do. And also those reads re-enforce the fact that a system should be able to handle the Full Levels for best performance. However if you just play those test videos and you DO see the BTB & WTW then clearly something is wrong. Also if you see NO flashing bars then something is also wrong.QB

See jmonier description

There is a lot of confusion with terminology that is not always consistent. At TV levels madVR outputs the full range of 0-255 with Black at 16 and Ref White at 235. At PC levels it expands 16 to be at 0 and 235 to be at 255. Thus you can see BTB and WTW ONLY with madVR TV levels.

If you set madVR to TV levels you will see the full range of 0-255 (i.e BTB and WTW) with the LG set to 'High'. Then when you set the LG to 'Low', 0-16 will all be black which is what you want.

This confirms what are written in the links I am referring to.

[iSeries]

The final result that you state IS what you want, BUT I think you are going through two unneeded conversions (one in madVR and one in the LG TV) to get there. I get the same result with similar equipment with madVR set to TV levels (16-235) and LG set to "Low".

There is a lot of confusion with terminology that is not always consistent. At TV levels madVR outputs the full range of 0-255 with Black at 16 and Ref White at 235. At PC levels it expands 16 to be at 0 and 235 to be at 255. Thus you can see BTB and WTW ONLY with madVR TV levels.

If you set madVR to TV levels you will see the full range of 0-255 (i.e BTB and WTW) with the LG set to 'High'. Then when you set the LG to 'Low', 0-16 will all be black which is what you want.

One more point: I've found that you cannot necessarily adjust with Brightness and Contrast as many calibration guides tell you to do. It depends on the unit. Note that while 16 is black and always should be, 235 is a more arbitrary limit. There is actually chroma information up to 240-244 and the Spears-Munsil Color Clipping test does not display correctly unless you can also see white up to about 244. That's possibly why the LG shows WTW in both High and Low and why my JVC RS-50 projector has a third Super White setting.

One more note: My settings will be correct for video material but will cause clipping of blacks from the desktop. If displaying all the black gradations in the desktop and other non-video material is important then you would have to go with the madVR PC levels with some small degradation in the video (primarily banding, although madVR's dithering may minimize that). And, for most things, you would never notice the difference in the non-video material.

In that case then, I'm lost. I understood LG's 'High' black setting to be 0-255 (PC levels) and 'Low' to be 16-235 (TV levels). Indeed, if I plug my TV into my PC using a regular VGA monitor cable, 'High' black level is a forced setting and cannot be changed.

So where exactly is the double conversion happening? MadVR outputs PC levels, my graphics card then outputs this as PC levels, and the TV displays it as PC levels.

The problem here is, so many people have a different opinion, and everyone believes their opinion is correct. This obviously leaves people like me eternally confused. Madshi, help?

[Qaq]

MadVR expands 16-235 (YUV) to 0-255 (RGB) by default. To pass it 'through' you need: 1) 0-255 RGB in video driver; 2) 0-255 RGB in display (HDMI input set as 'PC" (RGB), Black level set to High (0-255).
After that the only thing is left is chroma bug, haha. But you can do nothing with it.

[Budtz]

So I have set lav video to output 0-255. and madvr converts this and my samsung tv's hdmi black level is set to low. is this correct then?

[Qaq]

No. "Low" means 16-235. And you don't need to set lav to 0-255, its madVR's job.

[iSeries]

MadVR expands 16-235 (YUV) to 0-255 (RGB) by default. To pass it 'through' you need: 1) 0-255 RGB in video driver; 2) 0-255 RGB in display (HDMI input set as 'PC" (RGB), Black level set to High (0-255).
After that the only thing is left is chroma bug, haha. But you can do nothing with it.

Hi,

So you are saying my settings are correct then? (YV12 / NV12 untouched>MadVR PC levels 0-255>ATI6450 Full RGB 0-255>TV High black level 0-255)

[nevcairiel]

So you are saying my settings are correct then? (YV12 / NV12 untouched>MadVR PC levels 0-255>ATI6450 Full RGB 0-255>TV High black level 0-255)

Looks correct.

[iSeries]

Many thanks Nev - this thread is becoming a sea of confusion lol. You are one of the few people round here whose advice I trust :)

[MSL_DK]

So you are saying my settings are correct then? (YV12 / NV12 untouched>MadVR PC levels 0-255>ATI6450 Full RGB 0-255>TV High black level 0-255)

Looks correct.

Okay, now we know it. Then I ask do we get BTB and WTW from these settings? :p and it is not what we want to achieve?

[nevcairiel]

Okay, now we know it. Then I ask do we get BTB and WTW from these settings? :p and it is not what we want to achieve?

You do not get BTB or WTW.

Videos are meant to be 16-235, if you set your system to show values outside of that range, that means the "normal black" at 16 won't be as black as it could be, or the "white" at 235 will not be as white as it could be.
Personally, i rather have the usual values look as good as they can instead of leaving some room to show the "unusual" values.

IMHO, just forget about BTB/WTW, and enjoy the movie without any unnecessary level compression.

[Qaq]

So you are saying my settings are correct then? (YV12 / NV12 untouched>MadVR PC levels 0-255>ATI6450 Full RGB 0-255>TV High black level 0-255)
Correct (if TV HDMI input set to PC (RGB)).
EDIT: and TV Gamma set to Wide.

[iSeries]

Correct (if TV HDMI input set to PC (RGB)).
EDIT: and TV Gamma set to Wide.

Hi,

My LG has 3 gamma settings, Low, Medium and High. Which would be wide? And why would I need to change this from the default Medium?

Thanks!

[Qaq]

oops. Try "High" and check the picture. I got LG too but use my native lang settings.
I can't explain why High right now. I just don't remember. Maybe Medium is good for TV translations and High is better for HD video.

[iSeries]

Low = brighter image
High = darker image

What would I be looking to achieve by changing this from default Medium?

Thanks again!

EDIT: just saw your edit. The last thing I want to do is go changing things because I read a post from some guy on some forum saying they read a post from some other guy on some other forum saying that it was a good idea lol.

[dansrfe]

As far as I know. Limited is obsolete and if you're using it then you need to find a way to make Full RGB work with your system.

[jmonier]

In that case then, I'm lost. I understood LG's 'High' black setting to be 0-255 (PC levels) and 'Low' to be 16-235 (TV levels). Indeed, if I plug my TV into my PC using a regular VGA monitor cable, 'High' black level is a forced setting and cannot be changed.

As I said, the nomenclature is confusing. Your statements are all correct but what it means is this: High (0-255/PC levels) means that 0 is black; Low (16-235/TV levels) means that 16 is black. And Low is really 16-255 in the LG. That means that you will see flashing bars all the way to 255 in both High and Low.

So where exactly is the double conversion happening? MadVR outputs PC levels, my graphics card then outputs this as PC levels, and the TV displays it as PC levels.

I did say this already, but I'll try to explain further. With madVR set to PC levels means that it takes video black (16) and changes it to PC black (0) and also changes 235 to 255. This means that a monitor/TV that is set for PC levels will properly display black as black and not as dark gray. It also means that you can never see BTB and WTW.

So one conversion takes place in madVR. I, perhaps, confused things by referring to a second conversion in the TV. The TV has to perform a conversion from the digital signal to what you see on the screen in either case. For the High setting, 0 becomes black on the screen (complete absence of light). That is the second conversion that I was talking about, but I see now how it was confusing. For the Low setting 16 becomes black, which is where you want it for a signal that includes BTB and WTW.

If madVR is set to what is called TV levels (16-235), you will see BTB (bars 1-16 flashing) with the LG set to 'High' and you will NOT see BTB with the LG set to 'Low'. (As I said before, with the LG and, possibly, other sets, you will see WTW with either setting.)

There is a lot of confusion in the inclusion of 16-235 with the 'TV levels'. 'TV levels' means that you have an untouched signal where 16 is black and 235 is white. Unfortunately, it can easily be interpreted to mean that 16-235 has become 0-255. That is NOT correct.

'PC levels' actually means that the 'TV levels' have been converted to display correctly on a PC monitor where 0 is black.

[jmonier]

MadVR expands 16-235 (YUV) to 0-255 (RGB) by default. To pass it 'through' you need: 1) 0-255 RGB in video driver; 2) 0-255 RGB in display (HDMI input set as 'PC" (RGB), Black level set to High (0-255).

While 'PC levels' is the default setting in madVR, that means that madVR will convert 16-235 to 0-255.

If the TV/Monitor has a setting to display 16 as black (e.g. the 'Low' setting in the LG), you can set madVR to 'TV levels' and have the TV/Monitor do that conversion. That eliminates the conversion in madVR and moves it to the TV/Monitor where there is no penalty.

[jmonier]

Okay, now we know it. Then I ask do we get BTB and WTW from these settings? :p and it is not what we want to achieve?

Of course, we don't want to see BTB in normal viewing. That would produce a washed out picture with black becoming gray.

The only way you can see BTB under any conditions is to set madVR to 'TV levels'. Then you can see it on a TV/Monitor that is set to 'PC levels' (e.g. 'High' on the LG). With madVR set to 'PC levels', 16 is converted to 0 and the original 0-15 is thrown away, thus no BTB.

As I've said other places, you may see WTW for either TV/Monitor setting and that's not necessarily a bad thing. (At worst, normal program material will lose a slight amount of 'brightness'.)

[fairchild]

As far as I know. Limited is obsolete and if you're using it then you need to find a way to make Full RGB work with your system.

There is more to it than that. In a PC that is not strictly being used for video playback (games, web browsing, etc.) then on TV's that don't seem to handle Full RGB, you get black crush on the desktop and in games. So instead of constantly switching depending on your application, you can set it and forget it using Limited RGB. (obviously this is not optimal and you will get some extra conversions but to my eye *not a hardcore videophile* I see absolutely no difference)

[iSeries]

As I said, the nomenclature is confusing. Your statements are all correct but what it means is this: High (0-255/PC levels) means that 0 is black; Low (16-235/TV levels) means that 16 is black. And Low is really 16-255 in the LG. That means that you will see flashing bars all the way to 255 in both High and Low.

I dont have time to read the whole post full but sorry this is not correct in my case at least. With my setup as it is with TV black level at high I only see flashing bars from 17-234 with a test video. As I said earlier, 16 is complete black and 235 is complete white with MadVR set to PC levels, ATI driver set to Full RGB, and TV black level set to High.

However, using the test image here: http://www.lagom.nl/lcd-test/all_tests.php all 32 bands are clearly distinguishable which is exactly how it should be if my TV is displaying PC levels 0-255.

Also, using the test images here: http://www.lagom.nl/lcd-test/all_noprofile.php#gradient-h.png the gradient test image has zero banding and the black level and white level images below it all display exactly as they should, ie visible below 16 and above 235.

[dansrfe]

The last 5 pages of this thread has carried out the disscussion of only levels. Not about madVR directly. This is precisely why madshi doesn't reply or update for weeks or months at a time. It's because the thread just goes on tangents and people infiltrate the thread with problems that are not directly related to the topic of the thread. Open a new thread for a disscussion about levels and related problems of calibration. This isn't a topic that is directly related to madVR and it causes more headache for people (not to mention the developer) to sift through these threads and try and get positive feedback or constructive criticism related to their software or topic.

[iSeries]

I partially agree that some of it has been off topic - although learning how to use MadVR properly with our individual setups is important and completely on topic as far as I'm concerned.

I disagree entirely that off topic posts are the reason why Madshi doesn't update or reply for a while though. I'm sure he's a very busy person and his life doesn't revolve around MadVR.

[jmonier]

The last 5 pages of this thread has carried out the disscussion of only levels. Not about madVR directly. This is precisely why madshi doesn't reply or update for weeks or months at a time. It's because the thread just goes on tangents and people infiltrate the thread with problems that are not directly related to the topic of the thread. Open a new thread for a disscussion about levels and related problems of calibration. This isn't a topic that is directly related to madVR and it causes more headache for people (not to mention the developer) to sift through these threads and try and get positive feedback or constructive criticism related to their software or topic.

Every post of mine (and the posts I've responded to) have been directly aimed at level setting within madVR and the external settings needed to work with that.

[jmonier]

I dont have time to read the whole post full but sorry this is not correct in my case at least. With my setup as it is with TV black level at high I only see flashing bars from 17-234 with a test video. As I said earlier, 16 is complete black and 235 is complete white with MadVR set to PC levels, ATI driver set to Full RGB, and TV black level set to High.

If you don't read the whole post, how will you understand what I'm saying? If you want help, you have to co-operate, otherwise I'm wasting my time.

I'll say it once more and then I'm done: With madVR set to TV levels you will see 0-255 with the LG set to 'High' and 16-255 with the LG set to 'Low'. What you're reporting above is exactly what I said you would see with madVR set to PC levels, so what I said IS exactly correct in your case.