madVR - high quality video renderer (GPU assisted)

[huhn]

Do you guys think MadVR running a blu-ray would perform better than a Darbee chip in an Oppo 103D blur ray player?

If so, I could forgo purchasing a $500 blu-ray player and use MadVR for the enhancements.

if you look for something that does "things" with the picture you can ruin it with Darbee your choice.

MadVR only does things that need to be done with very very high quality Darbee changes the picture in a way that was not intended by the creator of the disk.

of cause MadVr can be used for debanding so changing the picture can help but this is an optional thing. and on a HTPC you can do a lot to "enhance/damage" your picture too.

[leeperry]

How did you interpret that in there?
All I said is that EVR is unlikely to switch between the two, which in practice means its probably always going to use the MPEG2 layout, since the vast majority of content uses that.
Well, chroma is properly aligned with mVR on that MPEG2 sample and it's not the case with EVR...maybe EVR does it MPEG1-style for SD though, anyway it's about time I would encode a proper MPEG1 test pattern and see how that goes as this problem has been bugging me for long enough now :sly:

[mysterix]

Is it should to use dithering even if video and native monitor resolutions are identical without scaling or dithering refers to color conversions in a "video color profile-OS/GPU-monitor" chain only and should to be used always, thus?

[tjcinnamon]

Well, at least mVR aligns MPEG2/H264 chroma properly as shown with this MPEG2 sample (http://forum.doom9.org/showpost.php?p=1622754&postcount=18186) and nev seems to be saying that EVR is always using the MPEG1 alignment (http://forum.doom9.org/showpost.php?p=1622757&postcount=18187). This might explain why I always found mVR sharper looking than EVR, OTOH mVR can't align MPEG1 properly AFAIK so you'll have to feed it RGB as LAV does provide the info but mVR doesn't care.

But this question is asked fairly often and this was madshi's latest take on that subject:

Of course for all this to matter a properly calibrated display helps and you might soon find out that the rabbit hole goes deeper :sly:

What are the color settings madshi is reffering to in madvr?

[huhn]

Is it should to use dithering even if video and native monitor resolutions are identical without scaling or dithering refers to color conversions in a "video color profile-OS/GPU-monitor" chain only and should to be used always, thus?

nearly all videos are YCbCr and YCbCr -> rgb creates float point so yes it should always be dithered.

[leeperry]

Is it normal that I get much higher GPU load when pausing mVR with PotP on W7? I'm using the 13.12 drivers on my HD7850, LAV for decoding and splitting, it happens on any kind of movie and I don't have NNEDI enabled, only mono-static ED1 LL & low debanding so no DXVA involved. I would gladly provide logs.

[sheppaul]

Is it normal that I get much higher GPU load when pausing mVR with PotP on W7? I'm using the 13.12 drivers on my HD7850, LAV for decoding and splitting, it happens on any kind of movie and I don't have NNEDI enabled, only mono-static ED1 LL & low debanding so no DXVA involved. I would gladly provide logs.

Probably you are using Direct3D 9 skin mode?

[tjcinnamon]

So should the luma scaling option be set for 1.2, 1.5x or always?

To me it seems always because if scaling is available it takes up a fair amount of processing power and the settings must be made for worst case otherwise when you get a video that does need it you'll get frame drops.

I'm I right on that?

[vivan]

If you're referring to image doubling using NNEDI3, then you got it wrong.

NNEDI3 can only double resolution. E.g. if you set that option to "always" and open 1280x720 video on 1366x768 display, then madVR will double those 1280x720 to 2560x1440 using NNEDI3 first, and then downscale it to 1366x768. It would take a lot of processing power, while it won't give any improvement.

[tjcinnamon]

If you're referring to image doubling using NNEDI3, then you got it wrong.

NNEDI3 can only double resolution. E.g. if you set that option to "always" and open 1280x720 video on 1366x768 display, then madVR will double those 1280x720 to 2560x1440 using NNEDI3 first, and then downscale it to 1366x768. It would take a lot of processing power, while it won't give any improvement.

Yeah doubling is what I was referring to.

options are:

only if scaling factor is 2.0x or bigger
only if scaling factor is 1.5x or bigger
only if scaling factor is 1.2x or bigger
always if upscaling is needed

A few guides suggest always and some suggest 1.5x

[Asmodian]

Any setting except always is reasonable in my opinion, I usually use 1.5. Below that and I don't think NNEDI3 is worth it.

2.0 is also a good option, with 2.0 you only use NNEDI3 if you will not have to downscale after it.

[fairchild]

2.0 is also a good option, with 2.0 you only use NNEDI3 if you will not have to downscale after it.

I prefer using 2.0 as well as I don't think the benefit of having to upscale past your display resolution only to then also have to downscale will be all that beneficial. Though some swear by using NNEDI3 doubling with 1280x720 videos to 1920x1080 display. I think it's just placebo for these people with their super duper binocular eyes. :D

[burfadel]

I have a problem with the on-screen controls with my connected Samsung H6400 TV. When playing MPC-HC, the on screen controls do not show in full screen! However, this is not always the case.

The problem modes are:
1920x1080 (both 50 and 60 Hz). This is the mode I actually want to use, the desktop fits perfectly on the screen. You should also expect it to work in this mode since it's default!
Any custom made through AMD Catalyst Control Centre (including 1776x1000)

It is not a scaling issue (that is, the controls are not off the edge of the screen). They are simply non-existent. If you click where the controls should pop up, it just pauses. If I underscan the image in Catalyst Control Centre, the desktop of course has black borders around the edge of the screen, the controls simply are not there.

The modes where the on-screen controls work:
1280x720
1776x1000 optimised (this is mode listed in the HDTV support section). So, for some reason 1776x1000 works, but not a custom 1776x1000, nor 1920x1080.

I could of course just use 1776x1000, HOWEVER the picture does not fill the whole screen. This is kind of obvious with it being 1776x1000, it basically shows 1776x1000 inside a 1920x1080 window, essentially. Basically, I have black borders around the image. As this is a custom mode, I cannot use the scaling options! The amount of border is quite large considering it is a 55 inch TV.

What I have tried:
Changing the output colour depth in the AMD Control Centre, which is under Properies (Digital Flat-Panel) between 8bpc, 10bpc, and 12bpc (yes, 12bpc is an option on this screen also).

Playing around with the LAVF settings, output colour spaces etc. No luck.

Several other things!

Has anyone else experience this? Can it be fixed? It is super annoying!

[huhn]

is this happening with EVR too?

this sounds like a problem with mpc hc not madvr

[burfadel]

Okay, I found the issue. It is a bug in MPC-HC! It's working properly now, in fact I can't make it not work properly! :)

How to 'fix'

Make sure the monitor (or TV etc) is in it's native mode, say 1920x1080. Also make sure MadVR etc is selected, then:
go to view --> options
click on 'Fullscreen' under 'Playback' on the left hand side
select the correct monitor from the 'Fullscreen monitor' dropdown list
click on 'Use autochange fullscreen monitor mode
click add, which should add an option to the list at the bottom with the correct display mode and refresh rate
make sure the 'from' and 'to' are set correctly (for this purpose type in say, from 1 to 70, it doesn't matter, as long as it covers what you will play)
move it up to the top and deselect every other option
deselect the 'Apply default monitor mode on fullscreen exit' and 'Restore resolution on program exit' at the bottom
click ok
open a new video and play in fullscreen mode
check out the working controls
exit fullscreen mode
go back to options and deselect the autochange option, it seems to be only needed once
close MPC-HC
reopen and test with your video

If it wasn't working before, it should now. Seems there is a settings bug in MPC-HC somewhere. It works after a reboot etc as well as changing display modes, which is good!

[StinDaWg]

I prefer using 2.0 as well as I don't think the benefit of having to upscale past your display resolution only to then also have to downscale will be all that beneficial. Though some swear by using NNEDI3 doubling with 1280x720 videos to 1920x1080 display. I think it's just placebo for these people with their super duper binocular eyes. :D
Not placebo. There is way less artifacts and a sharper image using NNEDI3 on 720p->1080p.

[leeperry]

Probably you are using Direct3D 9 skin mode?
Oh you nail it, I didn't see this one coming!

If madshi could do anything at all, this would be much appreciated. For now, I'll unassign the pause button in my custom skin....the auto-resume feature will still get the job done.

[tjcinnamon]

Not placebo. There is way less artifacts and a sharper image using NNEDI3 on 720p->1080p.

What is the setting you use?

always
1.2
1.5
2.0?

[QBhd]

I do 720p==>1024x768 and have it set to "always" and I can say for a certainty that there is no placebo effect going on... I too was skeptical, until one day when I decided to tick that radial. And the first thing that popped in my head was "Wow!"... So if I had a 1080 display, I would always be using NNEDI3 for image upscaling.

QB

[leeperry]

I would always be using NNEDI3 for image upscaling.
I think StinDaWg & Frechdachs nailed it (http://forum.doom9.org/showpost.php?p=1683790&postcount=26653) coz what I don't like with NNEDI is the aliasing they're reporting with AR+LL, will need to reevaluate.

[QBhd]

Well if you look at the madVR settings, AR does increase the aliasing bar... as for LL, I am fairly sure it is only supposed to be used with Catmull-Rom

[Stereodude]

Has anyone else experience this? Can it be fixed? It is super annoying!
It sounds like you need to change the TV to the 1:1 pixel setting that disables overscan.

[trip_let]

What is the setting you use?

always
1.2
1.5
2.0?

To make it active on 720p -> 1080p it can't be 2.0.

Not placebo. There is way less artifacts and a sharper image using NNEDI3 on 720p->1080p.

Depends on content a lot and downscaling used, etc.

Here's a quick and dirty look though. Source was posted a while back.

720p -> 1080p
Catmull-Rom (http://i.imgur.com/8y8i46I.jpg)
Lanczos 3 AR (http://i.imgur.com/baZS348.jpg)
NNEDI3 16 neurons doubling, Mitchell-Netravali LL downscale (http://i.imgur.com/YYAYSRj.jpg)

Okay, not quite comparable or fair maybe and not the best choices, but that's what I had saved prior in a quick test for myself. The text at the bottom looks appreciably better with the NNEDI3. I guess many would use a sharper downscaling algorithm though.

For most images most of the algorithms look pretty similar on just 1.5x though, unless pixels are large. I don't know if I'd be taken by hyperbole on describing these things.

[cyberbeing]

NVIDIA users should beware that the 340.43 Beta seems to have a bug which causes Custom Resolutions created by previous drivers to be ignored. They must have accidentally or otherwise changed the binary format of the CustomDisplay registry key slightly, making this new driver think the old key is corrupt. You can create them from scratch again, but rather annoying if you had a lot of special custom timings. YMMV.

[StinDaWg]

I think StinDaWg & Frechdachs nailed it (http://forum.doom9.org/showpost.php?p=1683790&postcount=26653) coz what I don't like with NNEDI is the aliasing they're reporting with AR+LL, will need to reevaluate.
I'm still waiting to hear what madshi has to say about it, just going to use without AR for now.

Well if you look at the madVR settings, AR does increase the aliasing bar...
Ya, but it's a HUGE difference, and only happens with downscaling. No AR text looks 99% perfect, AR on text looks really jagged (worse than just Jinc3AR upscaling).

The first image in each is Lanczos4, the 2nd is Lanczos4 AR. Look at letters like M,N,V,A.
http://t1.someimage.com/SfHuxXs.jpg (http://someimage.com/SfHuxXs) http://t1.someimage.com/2594m88.jpg (http://someimage.com/2594m88) http://t1.someimage.com/Ozw43SN.jpg (http://someimage.com/Ozw43SN) http://t1.someimage.com/sQ8VqBg.jpg (http://someimage.com/sQ8VqBg) http://t1.someimage.com/pMfHijU.jpg (http://someimage.com/pMfHijU) http://t1.someimage.com/NohYjKR.jpg (http://someimage.com/NohYjKR)

http://screenshotcomparison.com/comparison/79590/picture:0

[cyberbeing]

StinDaWg, do you see the same when using Spline 3-tap AR upscaling/downscaling, NNEDI3 256 chroma upscaling, NNEDI3 256 luma doubling?

Testing with 256 neurons is to rule out AR enhancing an NNEDI3 artifact. NNEDI3 has a tendency to produce blocky artifacts on high contrast text edges in particular. Only 256 neurons is completely immune.

Testing with Spline 3-tap is again to rule out potential anomalies. madVR's AR algorithm used with all resizers except Jinc was originally tuned to be near optimal (>95% eliminated ringing, without loss of detail loss or sharpness) only with Spline 3-tap. AR has always produced residual ringing artifacts with Lanczos3/4/8, Bicubic75/100, Spline4, and Jinc3/4 which exponentially become more visible with higher taps. The low ringing and soft algorithms on the other hand experience a slight loss of detail and sharpness with AR.


I'd also be curious if you can you reproduce this with madVR v0.87.8, which is prior to madVR correcting NNEDI3's 0.5 pixel shift when performing additional scaling. When pixel peeping I noticed that the text in your AR screenshots appears shifted slightly left & up compared to the non-AR screenshots, which is a bit strange.

[seiyafan]

So is it still recommended to use Catmull-Rom AR LL for downscaling with NNEDI3 or should it be Spine 3?

[6233638]

FYI I have responded to the discussion of anti-ringing/linear light scaling/NNEDI3, but a moderator has split it off into its own topic here: http://forum.doom9.org/showthread.php?p=1684179

[StinDaWg]

StinDaWg, do you see the same when using Spline 3-tap AR upscaling/downscaling, NNEDI3 256 chroma upscaling, NNEDI3 256 luma doubling?

Testing with 256 neurons is to rule out AR enhancing an NNEDI3 artifact. NNEDI3 has a tendency to produce blocky artifacts on high contrast text edges in particular. Only 256 neurons is completely immune.

Testing with Spline 3-tap is again to rule out potential anomalies. madVR's AR algorithm used with all resizers except Jinc was originally tuned to be near optimal (>95% eliminated ringing, without loss of detail loss or sharpness) only with Spline 3-tap. AR has always produced residual ringing artifacts with Lanczos3/4/8, Bicubic75/100, Spline4, and Jinc3/4 which exponentially become more visible with higher taps. The low ringing and soft algorithms on the other hand experience a slight loss of detail and sharpness with AR.


I'd also be curious if you can you reproduce this with madVR v0.87.8, which is prior to madVR correcting NNEDI3's 0.5 pixel shift when performing additional scaling. When pixel peeping I noticed that the text in your AR screenshots appears shifted slightly left & up compared to the non-AR screenshots, which is a bit strange.
I remember first seeing this issue when NNEDI3 was enabled, so I don't think madVR versions has anything to do with it. I tried NNEDI3 256 neurons/Spline 3AR and it isn't any better, still aliased text. The only thing that removes aliasing on all downscaling algorithms is to not use AR.

So is it still recommended to use Catmull-Rom AR LL for downscaling with NNEDI3 or should it be Spine 3?
I've always wondered why it was recommended here to use Catmull-Rom for downscaling. In various encoding forums where people are obsessed with quality, everyone uses Spline 36 (I guess this is Spline 3 in madVR). Spline is almost as sharp as Lanczos with less ringing/artifacts. Catmull-Rom is too soft IMO. Spline is somewhere in the middle.

If the aliasing is inherent to the algorithm and can't be fixed, I don't think AR should be recommended to use anymore for downscaling (it's still fine for upscaling). One of the greatest benefits from NNEDI3 is near perfect diagonal lines, using AR negates that. I don't see any increased ringing from not using it anyways, at least for 720p->1080p.

Edit: Just took a look at the pictures posted in that linked post and the issue definitely seems to have something to do with the way NNEDI3 doubles. Don't know why it was broken off into another thread either as it's relevant to this discussion we're having.

[Guest]

The moderating strategy was discussed with and approved by madshi, who is the originator of this thread. Please trust us in our attempts to keep things organized and accessible. It is not just a question of relevance. We have 26000+ posts in this thread! It is a nightmare to find things and very hard for madshi. Please continue the topic of linear light scaling/NNEDI3 in the linked thread. Thank you for your understanding.

Just to remind about the policy: This thread is for support of madVR (bug reports, questions about usage, etc.) and occasional development things when madshi asks for them (help with testing, etc). Everything else including theoretical discussions should go into a separate thread. You can preface the thread with "madVR" so it is recognizable as relevant to madVR.

[leeperry]

Yes, please.
So as promised they asked AMD about the copyback nonsense, they replied that their engineering team was aware of the problem but didn't have the time to look at it.

[truexfan81]

So as promised they asked AMD about the copyback nonsense, they replied that their engineering team was aware of the problem but didn't have the time to look at it.

Wow now that is excellent customer service right there. ;) :p :D

[Mangix]

NVIDIA users should beware that the 340.43 Beta seems to have a bug which causes Custom Resolutions created by previous drivers to be ignored. They must have accidentally or otherwise changed the binary format of the CustomDisplay registry key slightly, making this new driver think the old key is corrupt. You can create them from scratch again, but rather annoying if you had a lot of special custom timings. YMMV.

Can't you just do EDID overrides instead? They're limited to four resolutions but they should work. Well, pixel clock accuracy might be an issue.

[Plutotype]

Hi folks,
Win7 x64 ( Aero disabled ), madvr 0.87.10, MPC-HC nightly, Reclock, AMD HD7750 ( 14.4 WHQL ), Samsung UE65H8500 ( UHD TV ) connected directly per HDMI. 23.976fps movie played back on 3840x2160p24 resolution.
Playback in windowed mode works fine ( fullscreen as well ), but switching on fullscreen exclusive mode, when going fullscreen causes black screen and the playback stops there.
http://www.mediafire.com/download/59m39nf78tqqd5x/madVR_-_log.rar

Any hint please what blackscreens the FSE mode?
Thanks

[YxP]

Hi folks,
Win7 x64 ( Aero disabled ), madvr 0.87.10, MPC-HC nightly, Reclock, AMD HD7750 ( 14.4 WHQL ), Samsung UE65H8500 ( UHD TV ) connected directly per HDMI. 23.976fps movie played back on 3840x2160p24 resolution.
Playback in windowed mode works fine ( fullscreen as well ), but switching on fullscreen exclusive mode, when going fullscreen causes black screen and the playback stops there.
http://www.mediafire.com/download/59m39nf78tqqd5x/madVR_-_log.rar

Any hint please what blackscreens the FSE mode?
Thanks

Try without Reclock. Hasn't happened to me since I got rid of it.

[Meulen92]

Hi folks,
Win7 x64 ( Aero disabled ), madvr 0.87.10, MPC-HC nightly, Reclock, AMD HD7750 ( 14.4 WHQL ), Samsung UE65H8500 ( UHD TV ) connected directly per HDMI. 23.976fps movie played back on 3840x2160p24 resolution.
Playback in windowed mode works fine ( fullscreen as well ), but switching on fullscreen exclusive mode, when going fullscreen causes black screen and the playback stops there.
http://www.mediafire.com/download/59m39nf78tqqd5x/madVR_-_log.rar

Any hint please what blackscreens the FSE mode?
ThanksSometimes happened to me when i had 'alternative interop hack' enabled in the image doubling settings.

[baii]

What is the cheapest downscale algorithm to use for device like windows tablet?

I try all of them and seem DXVA is the cheapest, am i right?

The only thing concern here is color management, other than that, don't mind turning down everything else/use any option to lower the load.

[6233638]

What is the cheapest downscale algorithm to use for device like windows tablet?

I try all of them and seem DXVA is the cheapest, am i right?

The only thing concern here is color management, other than that, don't mind turning down everything else/use any option to lower the load.It depends on the hardware. That's possibly true for Intel hardware, but probably not with Nvidia.

Check the render stats to see. (hit CTRL+J when a video is playing, shorter times are better)

[somy]

Hi, I'm considering NUC for my next HTPC, does the i3 CPU with Intel® HD graphics 4400 good enough for MadVR (not extreme settings) with 1080P content?
Thank you in advance!

[ryrynz]

Hi, I'm considering NUC for my next HTPC, does the i3 CPU with Intel® HD graphics 4400 good enough for MadVR (not extreme settings) with 1080P content?
Thank you in advance!

Should be fine providing you're displaying on a ~1080 screen.

[tjcinnamon]

StinDaWg, do you see the same when using Spline 3-tap AR upscaling/downscaling, NNEDI3 256 chroma upscaling, NNEDI3 256 luma doubling?

Testing with 256 neurons is to rule out AR enhancing an NNEDI3 artifact. NNEDI3 has a tendency to produce blocky artifacts on high contrast text edges in particular. Only 256 neurons is completely immune.

Testing with Spline 3-tap is again to rule out potential anomalies. madVR's AR algorithm used with all resizers except Jinc was originally tuned to be near optimal (>95% eliminated ringing, without loss of detail loss or sharpness) only with Spline 3-tap. AR has always produced residual ringing artifacts with Lanczos3/4/8, Bicubic75/100, Spline4, and Jinc3/4 which exponentially become more visible with higher taps. The low ringing and soft algorithms on the other hand experience a slight loss of detail and sharpness with AR.


I'd also be curious if you can you reproduce this with madVR v0.87.8, which is prior to madVR correcting NNEDI3's 0.5 pixel shift when performing additional scaling. When pixel peeping I noticed that the text in your AR screenshots appears shifted slightly left & up compared to the non-AR screenshots, which is a bit strange.

What kind of beastly machine do you have where you can run 256 neurons (with no dropped frames)?!?!?

[cyberbeing]

With a higher-end GPU, 256 neurons on SD content should be within reason.

Though the intention of that post was only to take screenshots of the end result to rule out NNEDI3 artifacts, not actually watching the video in motion.

[tjcinnamon]

With a higher-end GPU, 256 neurons on SD content should be within reason.

Though the intention of that post was only to take screenshots of the end result to rule out NNEDI3 artifacts, not actually watching the video in motion.

I suppose I could run it too so long as it was screenshots.

with 1080p content do I even need to use LUMA image doubling NNEDI3 if my monitor resolution is max 1080p?

[Asmodian]

Image doubling will not run if scaling is not needed, even if set to "always".

I can run 256 neuron luma doubling on 360p -> 1440p @ 30 Hz on a ~1GHz Titan.

[michkrol]

I can run 256 neuron luma doubling on 360p -> 1440p @ 30 Hz on a ~1GHz Titan.

For informational purposes, my GTX 750 Ti overclocked to ~1,4GHz can do luma doubling with 256 neurons and Jinc3 upscaling on 360p -> 1080p at 25fps, with average render times around 39ms and GPU usage around 93% :devil:
That's cutting it really close, but playback is stable ;)

[-Hitman-]

Hi,

I've just started getting into Madvr but I have a minor GFX clipping problem that has plagued me for years and need help resolving it especially now using a quality renderer, i'm at a brick wall before I can carry on.

I have always used amd cards and using a common pluge pattern I have always had to up bri +2 and lower contrast -2 in the CCC settings to get all bars to show correctly, the consensus seems to be that the GFX driver settings for color should be untouched but this gives me a 19-233 video output, current new card is an amd R9 790, this is exactly the same result!

I have tried my onboard haswell 4600, same result as if something is clipping the video slightly.

With madvr integrated into the chain, my settings for colorspace are amd CCC - dynamic range 0-255 - video hdmi output - 0-255 - madvr 16-235 - display set to 16-235 (Pioneer KRP600M).

This gives the same 19-233 output, any change to the above gives either all bars 0+ and washed out or no bars at all on the black clipping pattern with heavy clipping.

I tried just adjusting madvr bri/cont which required bri +10, cont -40 to get 17/18 and 234/235+ bars to show correctly but the video image was a mess and overblown!

This is really frustrating me and need help :(

EDIT: My display has been calibrated using a bluray player and calman5, so it's not the display clipping.

[6233638]

Your KRP-600M should have no problems with clipping.
I don't understand why you would set the display to 16-235 when the video card is outputting 0-255.

Set the video card, display and madVR all to 0-255.
madVR will expand the 16-235 video range to 0-255. (below black and above white will not be visible)

[Plutotype]

Sometimes happened to me when i had 'alternative interop hack' enabled in the image doubling settings.

Thanks, the user has HD7750, cant use any doubling and the interop hack is disabled.

Try without Reclock. Hasn't happened to me since I got rid of it.

Thanks as well, with or without Reclock it gives same result - black screen ( no rendering ).

But during testing I found out, that the FSE does NOT work only when the 23.976fps 1080p movie is played back on a 2160p ( 3840x2160p24 ) resolution target. FSE works ok when changing it to 1080p24 in the display devices section. So my problem with FSE is related only when using it to render in the UHD resolution.

[huhn]

Your KRP-600M should have no problems with clipping.
I don't understand why you would set the display to 16-235 when the video card is outputting 0-255.

Set the video card, display and madVR all to 0-255.
madVR will expand the 16-235 video range to 0-255. (below black and above white will not be visible)

this way the gpu has to change it to 16-235. don't forget his tv doesn't support 0-255.

is this a general problem or madvr only.

you said your screen is calibrated but you change CCC this doesn't make sense. if your screen is calibrated this is not needed.

and on top of it with your current setup everything except MadVR is clipped. how do you use that picture to calibrate the screen?

to me this sounds like a wrong not calibrated screen and not an issue with MadVR.

[6233638]

don't forget his tv doesn't support 0-255.All the Kuros support 0-255.


Edit: Actually, I'm not 100% certain if the US consumer models do - they were stripped down compared to the ones sold elsewhere, to sell people on the "Elite" models.
Outside USA there was only one range of consumer sets, equivalent to the "Elite" without the branding, if I remember correctly.

The KRP-600M, being the pro monitor, absolutely does though.