madVR - high quality video renderer (GPU assisted)

[svengun]

It will be a bit complicated than that (I wanted to find my previous post about this but I couldn't):
- basically, since both of your Philips 65OLED803 and LG OLED EG920V TV are HDR capable, you want to passthrough the HDR content to them
- meaning you can't use external 3dlut with hdr content!
- you can only use external 3dlut with SDR content :)


Hey Chros,

HDR looks like shit , when I use that option , it's really dark and has very few 'sparkle highlights'

I know it is intended for projectors , but I am getting amazing results now and I have many many options to tweak it

It was only until recently , that I was really happy with result on my new Philips in regards to HDR.

Two Things did that:

1- using the BT709 (old) 3DLUT , shared by Madshi

2- Tonemapping (using Measurement files v 86) (My favo option and my current one, I'm using NEO-XP's latest config settings, he's on the AVSforum)

Using the live algo for HDR measurements should be providing way better results than the (static) HDR10. I think this is comparable , but even better than using HDR Meta Data like HDR10+ or DV (current results with this normal brightness, incredibly sharp , beautiful colors and amazing HDR)

I don't understand why I could not use a calibration 3DLUT , I intend to make a 709 & a bt2020 (DCI-P3) one, using DisplayCAL

I think your last 'dashed' remark is incorrect. U CAN use bt709 as an external 3DLUT , WHEN your are tonemaping to SDR, this will show HDR on ur TV , ur TV just won't tell you that is it is an HDR signal

Please elaborate ;-)

I purchased an X-rite i1Display Pro for 230 euro's just for that....

[chros]

What's the use case for the "tone map HDR using external 3DLUT" madVR option, then? :confused:

In latest stable madvr:
- it adds the possibility to do "static" hdr2sdr conversion which is waaay faster than the dynamic tonemapping implementation of the test versions.

HDR looks like shit , when I use that option , it's really dark and has very few 'sparkle highlights'
- which TV are we talking about? newer Philips or the older LG
- which option? hdr passthrough?

Then something is not right with your setup, it should be clearly way better with it than with madvr's dynamic tonemapping.

Doesn't the Philips TV have dynamic tonemapping implementation as the newer LGs do?

Using the live algo for HDR measurements should be providing way better results than the (static) HDR10.
Not necessary, it depends :) It's not that simple, is it? :)

- you are/can be right if you use madvr dynamic tonemapping with your TV in SDR mode
-- do you? if so, in which nits setting?
- or you could use it as @SamuriHL does (https://forum.doom9.org/showpost.php?p=1878021&postcount=56703) / did (https://forum.doom9.org/showpost.php?p=1878081&postcount=56707)
- or you could "just" passthrough to the display and let it does its job (that's what I use (https://www.avsforum.com/forum/26-home-theater-computers/3040072-madvr-tool-madmeasurehdr-optimizer-measurements-dynamic-clipping-target-nits-34.html#post57986200), and here (https://www.avsforum.com/forum/26-home-theater-computers/3040072-madvr-tool-madmeasurehdr-optimizer-measurements-dynamic-clipping-target-nits-34.html#post57992014))

I don't understand why I could not use a calibration 3DLUT
You can't with passtrhough.
You can with madvr's dynamic tonempaiing + your TV in SDR.

I intend to make a 709 & a bt2020 (DCI-P3) one, using DisplayCAL
There's no need for 2 3dluts: just create a DCI-P3 for the widest gamut your TV can provide and madvr will handle the rest.

I think your last 'dashed' remark is incorrect. U CAN use bt709 as an external 3DLUT , WHEN your are tonemaping to SDR,
But I was talking about HDR passthrough!!! :)

U CAN use bt709 as an external 3DLUT , WHEN your are tonemaping to SDR, this will show HDR on ur TV , ur TV just won't tell you that is it is an HDR signa
No, it won't for multiple reasons:
- what nits settings do you get on your TV with your current settings? (I assume it's not HDR mode) 120 / 140 / 150 nits?
- if you try to go higher in your TV setting in SDR mode, you will get ABL that will ruin everything (there are at least 3 (!) different ABL algo on recent LG Oleds)
- you can't compete a ~700 nits HDR video with a 150 nits tonemapped SDR signal

That's why that beta thread on avsforum has the "projectors" in its title :)

[Warner306]

In latest stable madvr:
- it adds the possibility to do "static" hdr2sdr conversion which is waaay faster than the dynamic tonemapping implementation of the test versions.

You can also do plain HDR 3D LUTs with HDR output with DisplayCal with a BT.2390 tone curve.

[Alexkral]

@svengun

What's that "BT709 (old) 3DLUT, shared by Madshi"?


- which TV are we talking about? newer Philips or the older LG
- which option? hdr passthrough?

Then something is not right with your setup, it should be clearly way better with it than with madvr's dynamic tonemapping.
I think he means that passthrough usually looks pretty dark compared to uncalibrated SDR, which I agree with, but it shouldn't look that bad in a dim environment, which is the reference. Using low target nits solves that, and probably dynamic target nits too.

BTW, I didn't know that OLEDs had such a low peak 100% window.

[svengun]

@svengun

What's that "BT709 (old) 3DLUT, shared by Madshi"?

http://madshi.net/DisplayCal400Nits709.rar

I think he means that passthrough usually looks pretty dark compared to uncalibrated SDR, which I agree with, but it shouldn't look that bad in a dim environment, which is the reference. Using low target nits solves that, and probably dynamic target nits too.

BTW, I didn't know that OLEDs had such a low peak 100% window.

This TV has one of the highest nits luminance , 850 nits. Vincent Teoh gives it high praises

[svengun]

- which TV are we talking about? Philips (870 nits) - which option? hdr passthrough? Yes , via Samsung UHD player it looks fine , passthrough HDR in MadVR looks dark & dull
If I use tonemapping to SDR or report as HDR , both looks really good

Doesn't the Philips TV have dynamic tonemapping implementation as the newer LGs do? I don't know. The TV get's very high ratings , see: https://www.flatpanelshd.com/review.php?subaction=showfull&id=1539059646 and also Vincent Teoh's review on youtube . It also won the EISA award for 2018/19 best buy OLED TV. It uses an LG 2018 panel met 2nd rev, which has improvements and also reaches 100nits more luminance


Not necessary, it depends :) It's not that simple, is it? :)

- you are/can be right if you use madvr dynamic tonemapping with your TV in SDR mode
-- do you? if so, in which nits setting? I use value 202 and it looks stunning
- or you could use it as @SamuriHL does (https://forum.doom9.org/showpost.php?p=1878021&postcount=56703) / did (https://forum.doom9.org/showpost.php?p=1878081&postcount=56707)
- or you could "just" passthrough to the display and let it does its job (that's what I use (https://www.avsforum.com/forum/26-home-theater-computers/3040072-madvr-tool-madmeasurehdr-optimizer-measurements-dynamic-clipping-target-nits-34.html#post57986200), and here (https://www.avsforum.com/forum/26-home-theater-computers/3040072-madvr-tool-madmeasurehdr-optimizer-measurements-dynamic-clipping-target-nits-34.html#post57992014))


You can't with passtrhough.
You can with madvr's dynamic tonempaiing + your TV in SDR.


There's no need for 2 3dluts: just create a DCI-P3 for the widest gamut your TV can provide and madvr will handle the rest. Thanks for the tip !


But I was talking about HDR passthrough!!! :)

haha OK, my bad. I am super happy with the result now, no need to switch to passthrough , I also now have the possibility to tweak things to my liking, which I see as a benifit to passthrough

You know what? Tonight I'll make to some screenshots with MPC-BE , showing tonemapping versus passthrough, also showing CONTROL-J OSD

I have read that with this Philips TV, when using a PC , I should put the TV on 'Monitor mode' but that mode doesn't except Full RGB (which is annoying and stupid)

I know this all started to improve PJ's , not TV's, but I'm not the only one using it for an OLED. NEO-XP also uses it for his OLED



No, it won't for multiple reasons:
- what nits settings do you get on your TV with your current settings? (I assume it's not HDR mode) 120 / 140 / 150 nits? >> 202

850 nits translates to 202 , see https://www.avsforum.com/forum/attachment.php?attachmentid=2536936

- if you try to go higher in your TV setting in SDR mode, you will get ABL that will ruin everything (there are at least 3 (!) different ABL algo on recent LG Oleds)
- you can't compete a ~700 nits HDR video with a 150 nits tonemapped SDR signal

That's why that beta thread on avsforum has the "projectors" in its title :) (see my anwsers directly after your questions/remarks)

[chros]

... NEO-XP also uses it for his OLED ...
Neo_XP doesn't have a HDR capable OLED TV but an earlier model, just telling ... :)

[svengun]

Neo_XP doesn't have a HDR capable OLED TV but an earlier model, just telling ... :)

ah, I did not know that ;-)

I thought that the 1st gen OLED's started with UHD support. My LG is from late 2016 , also has HDR , but a max of 420 nits...

[el Filou]

In latest stable madvr:
- it adds the possibility to do "static" hdr2sdr conversion which is waaay faster than the dynamic tonemapping implementation of the test versions.Ah that's why. I'm using a test build and sometimes I forget what was missing in the latest official release (which is now getting a bit old and lacking a lot of stuff, tbh), sorry about that.
There is an option in the test build to use a HDR2HDR 3DLUT now (with settings for the output gamut and HDR nits) but I don't know how if it gives good results in practice.

[Warner306]

(see my anwsers directly after your questions/remarks)

No, it won't for multiple reasons:
- what nits settings do you get on your TV with your current settings? (I assume it's not HDR mode) 120 / 140 / 150 nits? >> 202

850 nits translates to 202 , see

You're misreading that chart. That tells you where the knee point where the tone mapping roll-off begins is placed relative to the measured frame peak brightness.

202 target peak nits translates to 202 nits of SDR brightness. If your display is actually calibrated to 202 nits in SDR mode, you are largely getting 1:1 representation of 0-100 nits for most scenes up to 1,000 nits frame peak brightness and the remaining 102 nits (202 nits - 100 nits) is allocated to rolling off the specular highlights in each scene.

If your display is calibrated to less than 202 nits in SDR mode, then you are rolling off some of the image towards black at the ratio of 202 nits to your actual calibrated SDR brightness (e.g., 202 target nits / 150 SDR nits = 1.35x darker representation of the source values).

If your display is calibrated above 202 nits, then 202 target peak nits in madVR would brighten the mastered PQ source values by some amount.

[SamuriHL]

- or you could use it as @SamuriHL does (https://forum.doom9.org/showpost.php?p=1878021&postcount=56703) / did (https://forum.doom9.org/showpost.php?p=1878081&postcount=56707)


That's how I'm still using it and it works very well for me. I use measurement files with the latest test builds and I'm outputting HDR in madvr with a target nits of ~700. I keep dynamic tone mapping enabled on the C8. It's really the same type of setup I have with my UB820, as well. In both cases, it works very well....FOR ME. :) YMMV.

[fourbigkids]

Can you right-click on the video and get any of the other MPC-BE options to show? Are you using fullscreen exclusive mode? If so, try disabling it.

Hi Warner306. When the fault is occurring, when I right click, nothing happens. No context menu appears at all. I wasn't using fullscreen exclusive mode and have enabled it to see if that helps.


You could also check madVR setting Rendering/Exclusive mode/Show seek bar.

Hi brazen. Yes, this is enabled. No luck in resolving the fault.

Thanks guys. I'll do some more testing in fullscreen exclusive mode.

Cheers,

Allan
..........................................................

edit:

Tried fullscreen exclusive mode but had to disable it as video would flash black a then maroon. Back to the drawing board.

[Knight77]

Hello everyone!

Guys need your support because I'm going crazy here.

My setup was:

- Sony LED XD93 (4K, HDR)
- AVR (4K, HDR)
- Nvidia 1070
- Madvr updated to last version
- MCP BE
- HDR option off in Windows

Everything was running good (24p, 4k, HDR movies) with RGB Full and 12 bit sett in nvidia settings and player, 10 bit or more in madvr setting and 3dlut file in madvr for the calibration (calibrated to DCI P3). Nothing else relevant that I feel to point out.

Yesterday I changed the TV with a new OLED GZ950 by Panasonic and when I tested MPC I noticed some problem: with HDR I noticed a lot of blocking and the whites were more pink than white. Obviously I deactivated the 3dlut proflies and switched to "this display is already calibrated" setting 2020 and 2.2 gamma. I use madvr only for 4K HDR Movies and my TV switch to HDR and BT2020 with 2.2 gamma. I checked online and I figured out that I was using the internal codes (which were fine before...) and someone suggested to reinstall and use LAV Filters. I did it and it made the situation much much better but I still can see some blocking and banding and the whites still have some noticeable pink.

I have to clarify that this problem apparently it's present only with the HTPC and Madvr since Netflix, the PS4 and other apps/devices do not have these issues at all (with or without HDR).

I tried everything: reinstalling the nvidia drivers, changing the bit depths in Madvr, changing the gamut in the TV Settings (DCI-P3 looks a bit better/less pink but I lose a lot in general color...) but nothing solved the problems: some blocks, noticeable banding and the pink.

Last note: if I turn on windows HDR and watch an HDR movie with VLC everything is fine but I do not want to lose madvr quality.

[ryrynz]

Are you using HDMI 1? Is your cable up to spec?

[Knight77]

Are you using HDMI 1? Is your cable up to spec?

I am using HDMI 2 which is the arc one. My cable was good enough before so I can't see why wouldn't be good now. My other TV was a Sony 4K HDR 2016mid/High range...

:(

Any PC or madvr setting I need to check? After further test I can confirm that mainly the problem is the pink tint (you can't see it on the whole mage but if you check you can see it on clouds r similar) and banding. The blocks issue is quite minor even if actually there but mainly you see it in certain scenes.

P.S. the source files are very very high quality 4K HDR

[Alexkral]

If you think the problem is madVR then try the EVR.

[austinminton]

Is SLI expected to help madvr? I have 2x2080 Ti in SLI/NVLink and I noticed that the 2nd GPU is under 20% load with madvr (dxva2 copyback). I was under the impression that SLI doesnt add much to madvr but seeing this I am wondering if I can get both GPUs to share the load more effectively? I have maxed out my usual settings in NGU etc and the rendering times are still about 20ms with 1st gpu at 50% load and 2nd at about 20%. Running at 4k 120hz.

[svengun]

To what I've read , MadVR doesn't support it

[Warner306]

Hello everyone!

Guys need your support because I'm going crazy here.

My setup was:

- Sony LED XD93 (4K, HDR)
- AVR (4K, HDR)
- Nvidia 1070
- Madvr updated to last version
- MCP BE
- HDR option off in Windows

Everything was running good (24p, 4k, HDR movies) with RGB Full and 12 bit sett in nvidia settings and player, 10 bit or more in madvr setting and 3dlut file in madvr for the calibration (calibrated to DCI P3). Nothing else relevant that I feel to point out.

Yesterday I changed the TV with a new OLED GZ950 by Panasonic and when I tested MPC I noticed some problem: with HDR I noticed a lot of blocking and the whites were more pink than white. Obviously I deactivated the 3dlut proflies and switched to "this display is already calibrated" setting 2020 and 2.2 gamma. I use madvr only for 4K HDR Movies and my TV switch to HDR and BT2020 with 2.2 gamma. I checked online and I figured out that I was using the internal codes (which were fine before...) and someone suggested to reinstall and use LAV Filters. I did it and it made the situation much much better but I still can see some blocking and banding and the whites still have some noticeable pink.

I have to clarify that this problem apparently it's present only with the HTPC and Madvr since Netflix, the PS4 and other apps/devices do not have these issues at all (with or without HDR).

I tried everything: reinstalling the nvidia drivers, changing the bit depths in Madvr, changing the gamut in the TV Settings (DCI-P3 looks a bit better/less pink but I lose a lot in general color...) but nothing solved the problems: some blocks, noticeable banding and the pink.

Last note: if I turn on windows HDR and watch an HDR movie with VLC everything is fine but I do not want to lose madvr quality.

It sounds like an issue with the 3D LUT. Do you get correct colors without the 3D LUT? Have you tried checking report BT.2020 to display under calibration?

With a Panasonic GZ950, you should get a better picture by sending the HDR source to the display with passthrough. Panasonic follows the SDR range 1:1 with the PQ curve and does its gamut mapping with correct colorimetry. It can also do dynamic tone mapping of the specular highlights in each scene. That, or compress the HDR source with pixel shaders in madVR and send it as HDR to the display.

[XMonarchY]

Any news on Photoshop plugins?

[foozoor]

It's dead... like madVR. :devil:

[Klaus1189]

:eek:

[ryrynz]

Oh here we go.

[Knight77]

It sounds like an issue with the 3D LUT. Do you get correct colors without the 3D LUT? Have you tried checking report BT.2020 to display under calibration?

With a Panasonic GZ950, you should get a better picture by sending the HDR source to the display with passthrough. Panasonic follows the SDR range 1:1 with the PQ curve and does its gamut mapping with correct colorimetry. It can also do dynamic tone mapping of the specular highlights in each scene. That, or compress the HDR source with pixel shaders in madVR and send it as HDR to the display.

Warner306 thank you for the reply (big fan of yours by a long time :o )!
I have deleted the previous 3D Luts, since they were created working on my previous TV, and selected "This TV is already calibrated" with BT2020 and gamma 2.2 . I haven't tried report BT.2020 but I'll do! Actually to me it's not really clear this function...

I start having doubts about another setting and the doubts comes from many post here:

- madvr is configured with 10 bits or more (the TV support 10 and 12 bits) and fullscreen windowed. When I play something it reports the bits correctly.

- I configured NV control panel to 4K, 60hz, RGB 8bit when I'm not watching anything and 4K, 23hz and 12bit during vision (again mainly 4K HDR content).

BUT I found more than one post like this:

I've been doing further testing and managed to capture better screenshots (download and present them at 1:1 resolution) to exemplify my findings:

NV HDR triggered by madVR (output 10 bit) BANDING
NV HDR triggered by madVR (output 8 bit) NO BANDING
OS HDR enabled at Windows 10 (output 10 bit) NO BANDING (no screenshot available, too bright)

I've also noticed that with OS HDR disabled, and sending the metadata at madVR (NV HDR), the OSD only shows D3D11 fullscreen windowed (10 bit) when MPC-HC's seek bar isn't showing, otherwise it shows (8 bit). Keeps alternating from (10 bit) to (8 bit) when the mouse cursor moves down to the seek bar, for example.

But when with the HDR toggle enabled at the Win 10 display settings and madVR no sending metadata to the display (OS HDR), the OSD always shows D3D11 fullscreen windowed (10 bit), even when you move the cursor to the seek bar, or exits fullscreen. It ALWAYS shows (10 bit) at the OSD.

And, at last, D3D11's fullscreen exclusive always shows D3D11 exclusive (10 bit) and has NO BANDING.

So, to conclude, D3D11 exclusive NV HDR = Win10 OS HDR (both banding free)

Hope this helps further understanding why Windows' HDR toggle results in perfect picture without banding, and madVR sending the metadata to the display (NV HDR) on windowed mode doesn't.

Or this

According to thos post https://forum.kodi.tv/showthread.php?tid=229692&pid=2616287#pid2616287 setting 12 bit in NVCP will cause banding, and 8 bit should be selected.
I did that and I still get banding.

So...is this something of the past or to avoid banding we should keep 8bit? I'm confused. I thought that since the TV support 10/12bit I should aim for that. Also about FSE, is it obligatory? :confused:

[njfoses]

For a 4K UHD display (Sony 940E) that switches into HDR mode automatically, what is the proper setting for the "calibration" tab? Should i select already calibrated to rec709 or bt2020? I have HDR being passed through to the display via madVR (Nvidia 1070.) I watch both 1080p bluray and 2160p HDR via madVR.

[Warner306]

Warner306 thank you for the reply (big fan of yours by a long time :o )!
I have deleted the previous 3D Luts, since they were created working on my previous TV, and selected "This TV is already calibrated" with BT2020 and gamma 2.2 . I haven't tried report BT.2020 but I'll do! Actually to me it's not really clear this function...

I start having doubts about another setting and the doubts comes from many post here:

- madvr is configured with 10 bits or more (the TV support 10 and 12 bits) and fullscreen windowed. When I play something it reports the bits correctly.

- I configured NV control panel to 4K, 60hz, RGB 8bit when I'm not watching anything and 4K, 23hz and 12bit during vision (again mainly 4K HDR content).

BUT I found more than one post like this:



Or this



So...is this something of the past or to avoid banding we should keep 8bit? I'm confused. I thought that since the TV support 10/12bit I should aim for that. Also about FSE, is it obligatory? :confused:

Windows 1903 is known to have issues with banding and the occasional video driver before that, but there shouldn't be any difference between 10/12-bits and 8-bits on most displays. Those with LG OLEDs get better results with 8-bits, but that doesn't mean all OLEDs will do better with 8-bits. Try both and determine if you can see a difference. The dithering added by madVR should make the two bit depths look nearly identical.

For your color gamut issue, almost all SDR content is mastered to BT.709 and the TV should ship set up to handle BT.709 sources, unless you deliberately changed the TV color profile to BT.2020 or DCI-P3. If it has an auto setting, I would select that and the display should automatically select the correct color profile.

[Warner306]

For a 4K UHD display (Sony 940E) that switches into HDR mode automatically, what is the proper setting for the "calibration" tab? Should i select already calibrated to rec709 or bt2020? I have HDR being passed through to the display via madVR (Nvidia 1070.) I watch both 1080p bluray and 2160p HDR via madVR.

BT.709
Gamma 2.20

Those are most common.

[Knight77]

BT.709
Gamma 2.20

Those are most common.

So wait...in madvr "already calibrated" setting should I select those too? Even if I'm using MPC-BE and madvr just to watch 2160p HDR and my TV switch to BT2020?

[Wull]

Hi.

Are there any screen shots to see how madVR's scaling algorithms compare?

Also i'm all new to this so please bare with me. If I wished to watch a 4K HDR movie without HDR, do you simply select 'passthrough HDR to display' and uncheck 'send HDR metadata to the display'?

As I've tried this expecting the 4K image to look similar to a 1080p pic and it doesn't. I used the same picture settings for each, yet the 4K looked a little washed out in comparison.

[Asmodian]

If I wished to watch a 4K HDR movie without HDR, do you simply select 'passthrough HDR to display' and uncheck 'send HDR metadata to the display'?

No. To watch HDR video as SDR you need to convert it to SDR. Do not select "passthrough HDR to display". If what you want is to watch the HDR video as your (SDR) display presents it your settings are correct but the video will appear washed out.

As I've tried this expecting the 4K image to look similar to a 1080p pic and it doesn't. I used the same picture settings for each, yet the 4K looked a little washed out in comparison.

Yes, you need to convert HDR to SDR for it to look correct on a SDR display. madVR does this pretty well but it will never look exactly like the SDR master. Mastering is a creative process that results in different video for SDR and HDR.

[Warner306]

So wait...in madvr "already calibrated" setting should I select those too? Even if I'm using MPC-BE and madvr just to watch 2160p HDR and my TV switch to BT2020?

The calibration settings only refer to the display's SDR mode. HDR content is passthrough unless you select pixel shaders with SDR output.

[Wull]

No. To watch HDR video as SDR you need to convert it to SDR. Do not select "passthrough HDR to display". If what you want is to watch the HDR video as your (SDR) display presents it your settings are correct but the video will appear washed out.



Yes, you need to convert HDR to SDR for it to look correct on a SDR display. madVR does this pretty well but it will never look exactly like the SDR master. Mastering is a creative process that results in different video for SDR and HDR.

Thank's for explaining that. Which setting within madVR do I select to convert HDR to SDR? Would it be this? (let madVR decide: Sends HDR data to displays capable of HDR, otherwise coverts to SDR using pixel shader math). My Display is capable of HDR. I was just hoping to watch a 4K image with no HDR.

[ryrynz]

My Display is capable of HDR. I was just hoping to watch a 4K image with no HDR.

Each time I try to respond to this statement I just stop short lol.

[el Filou]

Maybe Wull wants to compare HDR and SDR to show a comparison to other people?

[Asmodian]

Sends HDR data to displays capable of HDR, otherwise coverts to SDR using pixel shader math). My Display is capable of HDR. I was just hoping to watch a 4K image with no HDR.

Since your display supports HDR you would need to set madVR to convert to SDR using pixel shader math all the time.

[Warner306]

Each time I try to respond to this statement I just stop short lol.

That sounds like the definition of HDR on a projector.

[mrmojo666]

Windows 1903 is known to have issues with banding

also with the the proper hotfix ?

[tp4tissue]

I used the same picture settings for each, yet the 4K looked a little washed out in comparison.

HDR -> SDR shader , the image is still HDR fitted to a different signal output to the TV.

THE TV could be in SDR, but it's outputting what the HDR signal should look like (in HDR) as rendered by Madvr.

The HDR to SDR shader is advantageous because Madvr currently does a better job tonemapping than many, if not most tvs for HDR content.

You are not suppose to compare an HDR file to SDR file, they will never look the same, because they are color-graded differently to different specifications.

HDR to SDR does not chop off the HDR and leave you with an SDR image.

It's taking an HDR image, and sending it in an SDR signal that the TV can understand in its SDR mode, but the image is still HDR. :D

[Warner306]

also with the the proper hotfix ?

I'm sure it will be fixed, but it was/is an issue.

[mrmojo666]

I'm sure it will be fixed, but it was/is an issue.
sorry to insist, it should be fixed, the hotfix was released last week. As i posted days ago.

IMO keeping to state: "there is, was, willl bugs" creates just confusion on users. It looks like more a win10 blaming without reasons

another story if there is something tested with hotfix installed and the bug persists......

[huhn]

your first link talks about 10 bit banding with your own words.

bit deep has nothing to do with the issues it happens an all application all screen all bit deeps we only found one workaround and that's d3d9 overlay which ignores the WDDM.

we have two reports that 18941 doesn't have the issue but that's not enough to call it fixed in that version yet.

if you think or if they fixed it for you test it and report that and but don't claim they fixed it because you read a line about 10 bit banding so it has to be that issues.

not saying they haven't fixed it yet just saying none has confirmed it.

or do it like this does KB4505903 and/or KB4501375 fix the issue can someone confirm that?

but don't come in like i have no banding so there is no banding...
do you even know the requirements to trigger the system wide banding on 1903?

[Wull]

Since your display supports HDR you would need to set madVR to convert to SDR using pixel shader math all the time.

Thanks to all the above. I now understand the differences between HDR & SDR :)

Yep, I own a projector. The reason for this question was to see what my options are. Basically I’ve been using to great effect madVR’s zoom for movies that have IMAX presentation. So I was thinking of forgoing HDR in favor of zoom.

As my projector doesn’t have the blanking feature like the JVC’s, I see my only options now are either to watch Blu-ray IMAX presentations/zoom or use the projectors zoom to shrink the IMAX image to fit my screen. Or I could just overspill, which looks rubbish.

Anyone using JRiver/madVR - HDR pixel shader with a gtx1080?

[mrmojo666]

IMO you just like to blame something.

Are you using 1903 with proper hotfix ? are you still having banding ?

If you answer NO at the first question for sure you must stop talking about it.

I read a lot of blaming words from you but you never cleared if you have tried 1903 with hotfix or not.

If you are using 1903 with hotfix and you still having banding, as you like to say for the opposite, that is not proving at all is a windows problem, but we can talk about it to try to understand the point.

So keep saying it's not fixed because you didn't tried is unfair and childish.

I have 1903 with hotfix and no banding. i know that my experience (and there is another user with the same experience) not prove anything. But at least I've tried and i can talk about my experience.

What piss me off if this blaming that you and others keep to do all the time, in the past was on AMD cards, now it's on win10 ..tomorrow what it will be ?

If i was a new madvr user I would be scared to use it, reading your posts....

PS: this is my gut feeling, will all the respect for you guys

[huhn]

so you fixed a problem you never had? https://forum.doom9.org/showpost.php?p=1879488&postcount=56881
ironic isn't it.
So keep saying it's not fixed because you didn't tried is unfair and childish.
but i'm childish for testing this properly?
just a reminder i didn't say this update doesn't fix it we have no one confirming it yet. i have a post where "there is no issue" and "look they fixed it" and "just google it" from you so?

and now this: I have 1903 with hotfix and no banding. i know that my experience (and there is another user with the same experience) not prove anything. But at least I've tried and i can talk about my experience.

if you really want to help confirm the requirements first to trigger the bug. don't blindly claim "my system is fine without understanding the issue/ having it" and don't claim it is fixed if you never confirmed to have it!
If you answer NO at the first answer for sure you must stop talking about it.
sorry i'm on 18941 to test the issue i have to reinstall windows to go back to 1903. still communicating with other user about this problem BTW. https://forum.doom9.org/showthread.php?p=1879948#post1879948
feel free to join. but claiming i didn't test this is well just leave it at this...

[mrmojo666]

so you fixed a problem you never had? https://forum.doom9.org/showpost.php?p=1879488&postcount=56881
ironic isn't it.

but i'm childish for testing this properly?
just a reminder i didn't say this update doesn't fix it we have no one confirming it yet. i have a post where "there is no issue" and "look they fixed it" and "just google it" from you so?

and now this:

if you really want to help confirm the requirements first to trigger the bug. don't blindly claim "my system is fine without understanding the issue/ having it" and don't claim it is fixed if you never confirmed to have it!

sorry i'm on 18941 to test the issue i have to reinstall windows to go back to 1903. still communicating with other user about this problem BTW. https://forum.doom9.org/showthread.php?p=1879948#post1879948
feel free to join. but claiming i didn't test this is well just leave it at this...

you are talking about 1903 with hotfix without have tested with your hands ahahahahaha funny this does not look like a good testing, looks like more not testing at all :D

I have posted as other user did to share my experience, i posted link to a MS hotfix that should fix it (for the sake of trying to help), you said that hotfix is for other issues and actually you were wrong. sorry but what does make you think you are more credible than MS ?

And now you are telling lies , saying that i said there is no issue because i haven't had the issue ? that is not true.

You like to blame that's all. and in this way you are not providing a good service to madvr.

And if you want to close this pointless discussion, i think we make a favor to all the thread.

[huhn]

every one can read your posts just saying.

[el Filou]

The '1903 banding issue' is not fixed yet, Microsoft is listing the general issue (of which the visible banding is only one effect) in the Windows 1903 official list of known issues, and the current status is still only 'mitigated': https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903#601msgdesc
(this doesn't specifically mention banding, but the list of scenarios that "may have issues" corresponds to the problem reported)

Their only 'mitigation' btw is to reboot when it happens, but it doesn't work for all those scenarios/not for long.

[JonnyRedHed]

Hi guys.

Have you seen this (OC3D Article url) Nvidia tells users to update their drivers to patch security flaws (https://www.overclock3d.net/news/gpu_displays/nvidia_tells_users_to_update_their_drivers_to_patch_security_flaws/1)

Thing is I'm still on an old gpu (MSI 670 OC), and have been happy just using madvr and NV 385.28 WHQL.

Do I and others still using 385.28 now need to update to the latest NV (410.60 or newer).

[nevcairiel]

Thats not the first driver with security fixes. A whole list of them was fixed in between 385 and today. If you care about that is up to you entirely.

[clsid]

Hi everyone,

Development of a dark theme for MPC-HC is almost finished. Please test it and let me know if you see any visual bugs, or bugs when interacting with the player GUI.

test build (x64) (https://github.com/adipose/mpc-hc/raw/develop/testbuild64/mpc-hc64.7z)
test build (x86) (https://github.com/adipose/mpc-hc/raw/develop/testbuild/mpc-hc.7z)

Dark theme can be activated through: menu > view > dark theme

Please test both the dark theme and the normal theme.